[jira] Commented: (GERONIMO-2067) Configs migration to M2

2006-07-17 Thread Jason Dillon (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12421714
 ] 

Jason Dillon commented on GERONIMO-2067:


console patch applied (#422836) jetty j2ee now has a functional console :-)

 Configs migration to M2
 ---

 Key: GERONIMO-2067
 URL: http://issues.apache.org/jira/browse/GERONIMO-2067
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
  Components: buildsystem
Affects Versions: 1.2
 Environment: All
Reporter: Anita Kulshreshtha
 Assigned To: Anita Kulshreshtha
 Fix For: 1.2

 Attachments: applications.patch, applications.patch, configs.log, 
 configs.log, configs.log, configs.log, configs.patch, configs.patch, 
 configs.patch, configs.patch, configs.patch, configs.patch, configs.patch, 
 configs.patch, console-configs.patch, etc.patch, m2-plugins.patch, 
 m2-plugins.patch, modules.patch, modules.patch, modules.patch, 
 newconfigs.patch, pom.patch, pom.patch, pom.patch


 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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-2067) Configs migration to M2

2006-07-02 Thread Anita Kulshreshtha (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12418852
 ] 

Anita Kulshreshtha commented on GERONIMO-2067:
--

Please note - The openejb jars generated by M1 build can not be used. Openejb 
must use geronimo jars with 
o.a.g groupId. The geronimo-dependency.xml files included in openejb-core and 
openejb-builder jars refer to geronimo jars. The above  results were generated 
by using a local openejb build!

 Configs migration to M2
 ---

  Key: GERONIMO-2067
  URL: http://issues.apache.org/jira/browse/GERONIMO-2067
  Project: Geronimo
 Type: Sub-task
 Security: public(Regular issues) 
   Components: buildsystem
 Versions: 1.2
  Environment: All
 Reporter: Anita Kulshreshtha
 Assignee: Anita Kulshreshtha
  Fix For: 1.2
  Attachments: applications.patch, applications.patch, configs.log, 
 configs.log, configs.log, configs.log, configs.patch, configs.patch, 
 configs.patch, configs.patch, configs.patch, configs.patch, configs.patch, 
 etc.patch, m2-plugins.patch, modules.patch, modules.patch, modules.patch, 
 newconfigs.patch, pom.patch, pom.patch, pom.patch

 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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-2067) Configs migration to M2

2006-06-11 Thread David Jencks (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12415761
 ] 

David Jencks commented on GERONIMO-2067:


Latest patches applied with minor tweaks in rev 413472.

By my count the remaining configs work is:
missing pom.xml are daytrader[jetty,tomcat], remote-deploy[jetty,tomcat] and 
uddi [jetty,tomcat]

In addition, activemq, activemq-broker, console[jetty,tomcat] are not built

 Configs migration to M2
 ---

  Key: GERONIMO-2067
  URL: http://issues.apache.org/jira/browse/GERONIMO-2067
  Project: Geronimo
 Type: Sub-task
 Security: public(Regular issues) 
   Components: buildsystem
 Versions: 1.2
  Environment: All
 Reporter: Anita Kulshreshtha
 Assignee: Anita Kulshreshtha
  Fix For: 1.2
  Attachments: configs.log, configs.patch, configs.patch, configs.patch, 
 modules.patch, modules.patch, newconfigs.patch, pom.patch, pom.patch, 
 pom.patch

 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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-2067) Configs migration to M2

2006-06-11 Thread Anita Kulshreshtha (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12415802
 ] 

Anita Kulshreshtha commented on GERONIMO-2067:
--

The jars needed for activemq, activemq-broker were not getting downloaded. I 
had to hand install them from 
.maven repo to .m2 repo. Will enable these as soon as the jars can be 
downloaded. 
Need to discuss with Prasad. I had to use o.a.g.applications groupId 
instead of o.a.g.applications.console. 
With the later groupId the 'target' directory could not be deleted. We are 
exceeding windows file name length limit.
-- A patch is needed in applications\console\console-ear  to add 
bundleFileName to maven-ear-plugin.


 Configs migration to M2
 ---

  Key: GERONIMO-2067
  URL: http://issues.apache.org/jira/browse/GERONIMO-2067
  Project: Geronimo
 Type: Sub-task
 Security: public(Regular issues) 
   Components: buildsystem
 Versions: 1.2
  Environment: All
 Reporter: Anita Kulshreshtha
 Assignee: Anita Kulshreshtha
  Fix For: 1.2
  Attachments: configs.log, configs.patch, configs.patch, configs.patch, 
 modules.patch, modules.patch, newconfigs.patch, pom.patch, pom.patch, 
 pom.patch

 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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-2067) Configs migration to M2

2006-06-06 Thread Anita Kulshreshtha (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12414961
 ] 

Anita Kulshreshtha commented on GERONIMO-2067:
--

j2ee-corba and client-corba configuration - 
   The plan.xml in both of these configurations are adding GBeans from 
openejb-core. The corba specs are being referenced via 
system properties. Hence added corba specs as a dependency via g-dependency.xml 
in openejb-core . This only contains corba spec 
whereas the M1 build includes g-timer, g-axis, g-util, tranql, and antlr. We 
could either add all the dependencies right now, or add as needed.

 Configs migration to M2
 ---

  Key: GERONIMO-2067
  URL: http://issues.apache.org/jira/browse/GERONIMO-2067
  Project: Geronimo
 Type: Sub-task
 Security: public(Regular issues) 
   Components: buildsystem
 Versions: 1.2
  Environment: All
 Reporter: Anita Kulshreshtha
 Assignee: Anita Kulshreshtha
  Fix For: 1.2
  Attachments: newconfigs.patch

 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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-2067) Configs migration to M2

2006-06-06 Thread David Jencks (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12415067
 ] 

David Jencks commented on GERONIMO-2067:


There's something wrong with your patch generation process.  All of these poms 
are already committed to svn, and your patch appends another copy to the 
existing file.  Please fix this problem before submitting any more patches.  I 
cannot apply patches that are against non-current svn.

 Configs migration to M2
 ---

  Key: GERONIMO-2067
  URL: http://issues.apache.org/jira/browse/GERONIMO-2067
  Project: Geronimo
 Type: Sub-task
 Security: public(Regular issues) 
   Components: buildsystem
 Versions: 1.2
  Environment: All
 Reporter: Anita Kulshreshtha
 Assignee: Anita Kulshreshtha
  Fix For: 1.2
  Attachments: newconfigs.patch

 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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-2067) Configs migration to M2

2006-06-06 Thread Anita Kulshreshtha (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2067?page=comments#action_12415070
 ] 

Anita Kulshreshtha commented on GERONIMO-2067:
--

This patch is dt 29th May. I had attached the patches to G-2071 for your 
convenience. But wanted to note down the important 
issues here. Today's patches are attached and described here :
http://issues.apache.org/jira/browse/GERONIMO-2071#action_12414974


 Configs migration to M2
 ---

  Key: GERONIMO-2067
  URL: http://issues.apache.org/jira/browse/GERONIMO-2067
  Project: Geronimo
 Type: Sub-task
 Security: public(Regular issues) 
   Components: buildsystem
 Versions: 1.2
  Environment: All
 Reporter: Anita Kulshreshtha
 Assignee: Anita Kulshreshtha
  Fix For: 1.2
  Attachments: newconfigs.patch

 To build these configurations use packaging plugin GERONIMO-1740. This patch 
 builds non openejb and non jetty configurations. 
 This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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