Re: [DISCUSS] Geronimo Eclipse Plugin (GEP) questions

[Sachin Patel]

(1) I think N-2 is a good rule to go by.

On 10/23/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
>
> Hi everyone, I have a couple questions I'd like to discuss about the
> Geronimo
> Eclipse plugin:
>
> 1. How many versions of the Geronimo server should we continue to
> simultaneously
> support in the Geronimo Eclipse plugin ??
> 2. What level of support should we provide in the Eclipse plugin for the
> Geronimo 1.2 Beta ??
>
> My thoughts and/or opinions are as follows (simply to start the
> discussions):
>
> 1. The plugin now has support for four Geronimo releases (i.e., 1, 1.1.1,
> 1.2,
> and 2.0). I would like to support only three versions at a time. This
> would
> still allow an upward migration path for people who want to migrate their
> projects from older to new versions (which is apparently one of the major
> reasons for providing support for multiple versions to begin with). I feel
> though that support for only three versions at a time would facilitate a
> more
> stable (and smaller) code base, it would mitigate some of the test
> scenario
> permutations inherit with multiple version support, and ease the
> implementation
> transitions from one release of the GEP to another. We've had and continue
> to
> have difficulties supporting the Geronimo 2.0.2 deployment plans in the
> GEP,
> which I'm confident will finally be rectified in the next maintenance
> release of
> the GEP, but it's only exacerbated by supporting so many versions.
>
> 2. I would like to start to untangle some of the interdependencies we now
> have
> with the various features in the plugin in the upcoming GEP  maintenance
> release. I know very little about the Geronimo 1.2 Beta, but I get the
> sense
> that it is more of a "one-off" rather than a nature progression from 1.1.1to
> 2.0.x, and I just wonder though how much the 1.2 support in the plugin is
> really
> being used. If it's not being used, I would actually like to remove the
> 1.2 Beta
> code from the plugin in the upcoming maintenance release for the reasons
> I've
> mentioned above.
>
> Thoughts ??
>
> --
> Thanks,
> Tim McConnell
>
>

[jira] Commented: (GERONIMODEVTOOLS-226) Production eclipse udate site does not have 2.0.0 on it!

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531102
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-226:
---

No! never delete old releases from the update site.. always append to the 
update site, don't create new update site either, otherwise you break everyone 
with this current site configured, AS well as WTP who uses the update site for 
the downloadable server adapter support.

> Production eclipse udate site does not have 2.0.0 on it!
> 
>
> Key: GERONIMODEVTOOLS-226
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-226
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Ted Kirby
>Priority: Blocker
>
> The staging site
> http://people.apache.org/~mcconne/releases/RC3/staging_site
> looks good, 
> but the production site
> http://www.apache.org/dist/geronimo/eclipse/updates/plugins/
> does not have the new stuff on it.
> Do we want to keep the old stuff there also, or just nuke it and put the v20 
> stuff there?
> Or, create a new udpate site for v2?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

project involvement

[Sachin Patel]

Hello community members...

I'd thought I'd shoot of a note to explain my limited involvement in  
the project as of recent.  As some have you may have known, I've  
taken a new job thats taken has taken away from the Java enterprise  
space.  As we all know what starting a new job is like, I've had very  
limited time with following the progress of Geronimo 2.0 and keeping  
up with the Geronimo Eclipse Plugin.  I ask that the community see to  
it that they continue their involvement in providing Geronimo best  
Java EE tooling and once things aren't so hectic with my life (a new  
job & getting married in 3 weeks!) I'll continue to be involved as I  
can.


- sachin

[jira] Updated: (GERONIMODEVTOOLS-181) Plugin build process should use maven-ant-plugin to download required Eclipse artifacts

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel updated GERONIMODEVTOOLS-181:
--


The problem with the eclipse web sites is that the URL have changed in the 
past.  Having them under our control aleast guarnetees reproducable builds.  

> Plugin build process should use maven-ant-plugin to download required Eclipse 
> artifacts 
> 
>
> Key: GERONIMODEVTOOLS-181
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-181
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.0
>
>
> The Eclipse plugin build process should use maven-ant-plugin to download the 
> required Eclipse artifacts from the Eclipse website rather than copying the 
> artifacts into a local maven repository on people.apache.org

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-181) Plugin build process should use maven-ant-plugin to download required Eclipse artifacts

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520384
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-181:
---

I disagree with this approach, this is what used to happen, and I would hate to 
revert back to this approach.  Having the eclipse artifcats deployed as maven 
dependencies worked out to be a huge improvement.  If the issue is the location 
of the maven repo, then its just a matter of publishing the jars to a more 
central location.

> Plugin build process should use maven-ant-plugin to download required Eclipse 
> artifacts 
> 
>
> Key: GERONIMODEVTOOLS-181
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-181
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.0
>
>
> The Eclipse plugin build process should use maven-ant-plugin to download the 
> required Eclipse artifacts from the Eclipse website rather than copying the 
> artifacts into a local maven repository on people.apache.org

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-177) Start of Remote Geronimo Server from within Eclipse fails

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515292
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-177:
---

There is no real way to start a remote server.  Until Geronimo has some sort of 
agent capable of managing multiple servers that we can use, there really isn't 
a mechanism available in geronimo to allow this capability.

> Start of Remote Geronimo Server from within Eclipse fails
> -
>
> Key: GERONIMODEVTOOLS-177
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-177
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
> Environment: Geronimo Eclipse Plug-in v1.2.1 and v2.0
>Reporter: Shiva Kumar H R
>Assignee: Tim McConnell
>
> Scenario: Using Eclipse to deploy apps to a remote instance of Geronimo.
> Add a remote instance of Geronimo server (say v2.0) inside Eclipse as per the 
> instructions in 
> http://www.ibm.com/developerworks/java/library/os-ag-remotedeploy/index.html
> Upon trying to Start that remote Geronimo server from within Eclipse, it 
> immediately fails with an error "Server Apache Geronimo v2.0 Server at 
>  failed to start."
> However if the remote server is manually started (outside of Eclipse), after 
> a while its state changes to "Started" inside Eclipse. And we can 
> deploy/redeploy/undeploy & stop the remote server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-174) "Distribution of configuration failed" when attempting to deploy using Geronimo 2.0 adapter

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511739
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-174:
---

To deterimine weither its a WTP J2EE export operation bug, can you crack open 
the zip file and (1) verify its contents and strcuture to see if its missing 
anything, then (2) deploy that archive using the command line deployment tools.

> "Distribution of configuration failed" when attempting to deploy using 
> Geronimo 2.0 adapter
> ---
>
> Key: GERONIMODEVTOOLS-174
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Tom Mutdosch
>
> Using the following Geronimo 2.0 runtime server and adapter:
> (*) Server: 
> http://people.apache.org/dist/geronimo/eclipse/unstable/servers/geronimo-tomcat6-jee5-2.0-SNAPSHOT-bin.zip
>  
> (*)Server plugins: 
> http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070621.1204-deployable.zip
>  
> Using eclipse WTP, I create a simple Dynamic Web Project targeting Geronimo 
> with a single HTML file.  When I do a Run on Server I get the following error 
> in an error dialog and my page does not run.
> Error:
> Distribution of configuration failed. See log for details.
> Cannot deploy the requested application module because no deployer is able to 
> handle it. This can happen if you have omitted the J2EE deployment 
> descriptor, disabled a deployer module, or if, for example, you are trying to 
> deploy an EJB module on a minimal Geronimo server that does not have EJB 
> support installed. 
> (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip)
> org.apache.geronimo.common.DeploymentException: Cannot deploy the requested 
> application module because no deployer is able to handle it. This can happen 
> if you have omitted the J2EE deployment descriptor, disabled a deployer 
> module, or if, for example, you are trying to deploy an EJB module on a 
> minimal Geronimo server that does not have EJB support installed. 
> (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:239)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124)
> at 
> org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke()
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863)
> at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
> at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
> at 
> org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke()
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863)
> at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
> at 
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
> at 
> com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
> at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
> at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423)
> at 
> javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96)
> at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260)
> at java.security.AccessController.doPrivileged(AccessController.java:275)
> at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363)
> at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797)
> at sun.reflect.GeneratedMethodAcce

[jira] Commented: (GERONIMODEVTOOLS-141) Installation/Activation of other Plugins fail after installing Devtools plugin

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510145
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-141:
---

No changes should be made here.  Once the 2.0 release of the plugin is 
released, this will resolve the issue.

> Installation/Activation of other Plugins fail after installing Devtools plugin
> --
>
> Key: GERONIMODEVTOOLS-141
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-141
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 1.2.0
> Environment: Windows XP SP2, Java 1.6.0_01, Eclipse 3.3 M6, WST 2.0 M6
>Reporter: Stefan
>Assignee: Sachin Patel
>Priority: Blocker
>
> Via Eclipse function to download additional server adapters you can choose 
> and install the plugin.
> But after restart Eclipse the plugin is disabled. If you try to enable it, 
> you get:
> Requested operation cannot be performed because it would invalidate the 
> current configuration. See details for more information. 
> org.apache.geronimo.feature (1.2.0) requires plug-in 
> "com.ibm.etools.emf.event".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-141) Installation/Activation of Plugin fails

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-141.
-

Resolution: Won't Fix
  Assignee: Sachin Patel

> Installation/Activation of Plugin fails
> ---
>
> Key: GERONIMODEVTOOLS-141
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-141
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 1.2.0
> Environment: Windows XP SP2, Java 1.6.0_01, Eclipse 3.3 M6, WST 2.0 M6
>    Reporter: Stefan
>Assignee: Sachin Patel
>Priority: Blocker
>
> Via Eclipse function to download additional server adapters you can choose 
> and install the plugin.
> But after restart Eclipse the plugin is disabled. If you try to enable it, 
> you get:
> Requested operation cannot be performed because it would invalidate the 
> current configuration. See details for more information. 
> org.apache.geronimo.feature (1.2.0) requires plug-in 
> "com.ibm.etools.emf.event".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-141) Installation/Activation of Plugin fails

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509838
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-141:
---

The eclipse plugin that is currently on the update site is for WTP 1.5.4 only.  
There are issues with it installing it on Eclipse 3.3/WTP2.0.  Since these are 
released binaries they cannot be cracked open and modified to prevent 
installation on Eclipse 3.3.

As far as the unstable driver that is supported on WTP2.0.  It will be 
published on the update site, once Geronimo 2.0 is released (in order to break 
snapshot depenencies) and secondly, once the plugin has gone through the voting 
process.  You can expect RC drivers to roll out once Geronimo 2.0 is released.  
In the meantime please continue to use the daily drivers and go through the 
manual (non update mgr) installation process.

> Installation/Activation of Plugin fails
> ---
>
> Key: GERONIMODEVTOOLS-141
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-141
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 1.2.0
> Environment: Windows XP SP2, Java 1.6.0_01, Eclipse 3.3 M6, WST 2.0 M6
>Reporter: Stefan
>Priority: Blocker
>
> Via Eclipse function to download additional server adapters you can choose 
> and install the plugin.
> But after restart Eclipse the plugin is disabled. If you try to enable it, 
> you get:
> Requested operation cannot be performed because it would invalidate the 
> current configuration. See details for more information. 
> org.apache.geronimo.feature (1.2.0) requires plug-in 
> "com.ibm.etools.emf.event".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-100) publishing hundreds of web projects / dependencies - GUI usability

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-100.
-

Resolution: Won't Fix
  Assignee: Sachin Patel

Closing per comments.

> publishing hundreds of web projects / dependencies - GUI usability
> --
>
> Key: GERONIMODEVTOOLS-100
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-100
> Project: Geronimo-Devtools
>  Issue Type: Wish
>  Components: eclipse-plugin
>Affects Versions: 1.1.0
>Reporter: Oleg Gusakov
>Assignee: Sachin Patel
>Priority: Trivial
>
> When there are several hundred projects, publishing/removing them from 
> Geronimo becomes a tedious task.
> We need a clearer GUI to address that, probably some kind of hierarchical 
> markup in the project metadata. Or combine that with Maven POM metadata ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-91) WTP server adapters for geronimo needs to provide extensibility, like an OEM vendor.

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-91.


   Resolution: Fixed
Fix Version/s: (was: 1.2.1)
   2.0

I think this issue has been resolved and extensibility issues have been worked 
around by redefining extension points and using parameters in property files.

> WTP server adapters for geronimo needs to provide extensibility, like an OEM 
> vendor.
> 
>
> Key: GERONIMODEVTOOLS-91
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-91
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 1.1.0
> Environment: all environments
>Reporter: Lin Sun
> Fix For: 2.0
>
>
> The WTP server adapter for geronimo, also known as devtools project, needs to 
> provide extensibility, like an OEM vendor so that other companies can build 
> their additional plugins to brand Apache Geronimo to their companies' logo or 
> name, with AG's eclipse plugins untouched.One example is that Eclipse 
> allow other vendors to brand Eclipse, for example, you could configure a 
> different splash screen.
> There are two things I see here, and there can be others that I am missing:
> 1) There is a geronimo-1.1 appended to the installation path after user 
> clicks on the Download and Install button to download either the jetty or 
> tomcat distribution.   This is undesired.   
> 2) There are two buttons (Jetty or Tomcat).  It should be configurable as 
> other companies may want to distribute jetty only, tomcat only or both.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-140) Eclipse plugin redeploys multiple times after a re-publish

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-140.
-

   Resolution: Fixed
Fix Version/s: 2.0

This issue has been fixed in 2.0.0 drivers.

> Eclipse plugin redeploys multiple times after a re-publish
> --
>
> Key: GERONIMODEVTOOLS-140
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-140
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 1.2.0
> Environment: Eclipse 3.2.2 / WTP 1.5.3 on Windows XP against Geronimo 
> 1.1.1
>Reporter: Andres Martinez
> Fix For: 2.0
>
> Attachments: projects.zip, trace.txt
>
>
> My workspace consists of a WAR project dependent on 3 utility JAR projects.  
> If I rebuild all my projects and republish, the console shows 3 redeploys:
> 01:06:16,687 INFO  [DirectoryMonitor] Hot deployer notified that an artifact 
> was removed: default/default/1.0/car
> 01:06:17,609 INFO  [DirectoryMonitor] Hot deployer notified that an artifact 
> was removed: default/default/1.0/car
> 01:06:18,437 INFO  [DirectoryMonitor] Hot deployer notified that an artifact 
> was removed: default/default/1.0/car

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-142) g-eclipse-plugin 1.2.1 requires the feature "org.eclipse.jst 1.5.3".

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-142.
-

Resolution: Won't Fix

It does require 1.5.3.  There were some fixes that went into WTP 1.5.3 that are 
needed.  (Its been a long time and I can't remember exactly what those fixes 
where but had to do with the installable runtime/server support.) You may get 
the deployable.zip for the 1.2.1 plugin, and it will install but you may run 
into minor issues.  Thus the update manager distribution was restricted to 
require 1.5.3.

> g-eclipse-plugin 1.2.1 requires the feature "org.eclipse.jst 1.5.3".
> 
>
> Key: GERONIMODEVTOOLS-142
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-142
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 1.2.1
>Reporter: Kan Ogawa
>Priority: Critical
> Attachments: screenshot-1.jpg
>
>
> Now, using the following Eclipse environment, I am developing the J2EE 
> application with Apache Geronimo server.
>  (a) Eclipse 3.2.1 with Language Pack.
>  (b) Eclipse WTP 1.5.1 with Language Pack.
>  (c) Apache Geronimo Server 1.2.0 beta (in the future, I will upgrade to its 
> stable release.)
>  (d) Geronimo WTP Server Adapter plug-in 1.2.1 (2007/04/03 Build, I built it 
> by maven after downloading the source codes from the apache svn repository.)
> In this environment, Eclipse always displays the error message, which it 
> cannot install any and every plugins from any and every update sites(in other 
> words, any other plugin except g-eclipse-plugin).
> (See the attached screen shot.)
> In order to compile and run g-eclipse-plugin 1.2.1, is the feature 
> "org.eclipse.jst 1.5.3" required absolutely?
> That is, does g-eclipse-plugin 1.2.1 not run on the older version (from JST 
> 1.5.0 to 1.5.2 version) than JST 1.5.3?
> I doesn't have verified all features in g-eclipse-plugin 1.2.1 yet, but I got 
> the impression that it is running in the above eclipse environment (a) and 
> (b).
> Now, on the eclipse error log view, the error level messages display none.
> If it can run on the older version than Eclipse JST 1.5.3, can you modify the 
> "requires" element definition in feature.xml?
> [Before]
>
>   
>
> [After]
>
>   
>
> If it cannot certainly run the older version its 1.5.3, would you give a 
> detail of the reason?
> Best Regards,
> Kan Ogawa

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-171) Remove hard-coded Geronimo name from launch console message and tool-tip

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509624
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-171:
---

We'll probably need a trivial extension point for this to check for supported 
servers to add this context menu action.

> Remove hard-coded Geronimo name from launch console message and tool-tip
> 
>
> Key: GERONIMODEVTOOLS-171
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-171
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
> Attachments: GD-171.patch
>
>
> Replace:
> console=Geronimo Console
> consoleTooltip=Apache Geronimo Console
> with:
> console={0} Console
> consoleTooltip={0} Console
> in 
> eclipse-plugin\plugins\org.apache.geronimo.st.ui\src\org\apache\geronimo\st\ui\internal\Messages.properties,
>  and allow the server name to be determined by server.getName().
> This allows for an extensible approach, for servers based on Geronimo.  No 
> change is required to support other servers.
> In this particular case, 
> plugins\org.apache.geronimo.st.ui\src\org\apache\geronimo\st\ui\actions\LaunchGeronimoConsoleAction.G_SERVER_PREFIX
>   is hard-coded to "org.apache.geronimo".  It would be nice if this could be 
> paramterized in some fashion to avoid having to replace the class in its 
> entirety, just to change this value to determine if the "Launch {ServerName} 
> Console" menu item should be activated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-145) Provide WTP2.0m6 compatibility

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-145.
-

Resolution: Fixed
  Assignee: Sachin Patel

Should be fixed.

> Provide WTP2.0m6 compatibility
> --
>
> Key: GERONIMODEVTOOLS-145
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-145
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.0
> Environment: Eclipse3.3m7, WTP2.0.0 m6
>Reporter: Vadim Dmitriev
>Assignee: Sachin Patel
>Priority: Minor
>
> WTP2.0 prior to m6 release had most of included plugins with version 1.6.0. 
> Since m6 these plugins version was changed to 2.0.
> In this case dependency on JDT 1.6.0 can't be satisfied on WTP2.0m6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-172) Enable customization of New/Edit Server Runtime Wizard screen

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-172.
-

   Resolution: Fixed
Fix Version/s: 2.0
 Assignee: Sachin Patel

> Enable customization of New/Edit Server Runtime Wizard screen
> -
>
> Key: GERONIMODEVTOOLS-172
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-172
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
>Assignee: Sachin Patel
> Fix For: 2.0
>
> Attachments: GD-172.patch
>
>
> The installDir label and text box have hard-coded Geronimo values:
> tooltipLoc=A location of an existing Geronimo installation or a path to 
> install to.
> tooltipInstall=Downloads the selected Geronimo distribution and installs it 
> to the specified location.
> replace Geronimo above with {0}.
> Code must be updated to pass in the value as getRuntimeName()
> Also, the visibility of some methods should be changed from private to at 
> least protected to allow flexibility in overriding this screen for 
> extension/customization.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: J2G Conversion tool got a makeover. Now what?

[Sachin Patel]

Having a j2g migration target runtime wouldn't really be the right  
thing to do.  A target runtime is basically a Eclipse ClassPath  
Container that gets added to your project that defines your project's  
JRE as well as the set of runtime jars that are needed to compile  
your application for a particular j2ee server.  The idea was when  
this is swapped, for you to use a wtp data model operation to add pre  
and/or post operations to extend the operation that applies or  
changes a target runtime for a project.  I'm not sure why they  
introduced allowing multiple target runtimes it very well could be a  
bug.


Since this takes a little more digging and understanding into WTP  
api's and extension points Id start with the basics.


Create a context menu action that operates on an IProject (you can  
later filter it based on if its a J2EE project and what its current  
target runtime is) but for now, just enable if for all IProjects.   
Then as I suggested earlier, run through the project resources to  
invoke the necessary operations on each resource.   You should be  
able to do this with the base eclipse platfrom API's, and I think J2G  
is using stuff from JDT.


In the long run this really needs to be done completely through WTP  
API's, otherwise its behavior of it will be really ugly :), and it  
won't have the seamless integration into the product we are looking for.


-sachin



-sachin


On Jun 27, 2007, at 12:22 PM, Erik B. Craig wrote:


Sachin,
I've been digging into documentation on WTP and Eclipse plug-ins in  
general over the last few days, and I am wondering what  
specifically you have in mind with this approach. Based on what you  
have said, the best solution I've been able to think of is perhaps  
adding an additional 'target runtime' to be selected from the list  
that would be called something like 'j2g migration', at which point  
the user would be prompted for a path to an existing geronimo  
server, and after clicking 'next', it would (correct me if it can  
even DO this) execute the 1st piece of j2g in a terminal (or maybe  
behind the scenes?), displaying the output, a next again would do  
the same for the second piece, a third next would do the same for  
the final piece.



Other than this, which I'm not entirely sure of the feasibility of  
it at this point, I don't know that trying to have it auto detect a  
changeover or something would necessarily work, because of the fact  
that you can have multiple target runtimes selected.


The other (perhaps simpler) idea for a UI integration I came up  
with doesn't necessarily involve any WTP pieces, as it would be to  
simply have a window or menu available that would have buttons/ 
options to run the three components and show the output from them.


What are your thoughts?

Thanks

-Erik

On 6/15/07, Sachin Patel <[EMAIL PROTECTED]> wrote: At this time  
as its currently implemented, I don't think it would

make a good inside the UI.  The context you're working in the IDE is
a "project" under development and J2G currently doesn't operate under
this context.  There would be no real advantage to allow it to be
invoked in the UI since it can't be operated on projects in the
workspace.

If any integration into the UI then the proper approach and it would
be fairly trivial is to go ahead with WTP integration...

All J2EE projects in WTP have a notion of a target runtime.  Every
application is required to have its target runtime set (JBoss,
WebSphere, Geronimo, etc..).  At any point in time you can retarget
an applications runtime to a different one.  So if an application's
runtime is set to JBoss, you can currently swap it over to Geronimo.
This operation can be extended to perform any other tasks.  In our
case, we would simply process the projects and traverse through the
content running any migrations necessary.

I don't think this would be too hard to do.  Its just picking out the
core peices currently inside J2G that actually do the migration on
particular resources and wrapping those in 1 or more WTP operations.
If this approach was taken I would be +1 to integrating this within
the Eclipse Plugin.

hope that helps.

-sachin


On Jun 14, 2007, at 5:54 PM, Jason Warner wrote:

> Paul,
>
> Thanks for the feedback!
>
> In regards to integration with the eclipse plugin, I don't believe
> that would be an easy task to accomplish.  From my understanding,
> the eclipse-plugin runs on top of WTP whereas the J2G tool is a
> headless plugin.  I believe the J2G tool would need to be rewritten
> using WTP to allow for integration.
>
> As for a button or other GUI way of launching the tool, I think
> that's a great idea.  I'm still rather new to working with eclipse
> plugins, though, so I'm not quite sure how that could be done.  The
> tool 

[jira] Closed: (GERONIMODEVTOOLS-149) EAR deployment fails with Eclipse 3.3M7

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-149.
-

   Resolution: Fixed
Fix Version/s: 2.0

This should be fixed now in recent RC drivers.

> EAR deployment fails with Eclipse 3.3M7
> ---
>
> Key: GERONIMODEVTOOLS-149
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-149
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Jacek Laskowski
> Fix For: 2.0
>
>
> I'm working with
> [1] Eclipse 3.3M7
> [2] Apache Geronimo 2.0 - http://people.apache.org/~prasad/binaries/20070522/
> [3] 
> http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070523.0744-deployable.zip
> Deploying WAR file is fine, but EAR finishes with the following exception:
> Distribution of configuration failed.  See log for details.
>   java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip
>  (The system cannot find the file specified)
>   org.apache.geronimo.common.DeploymentException: 
> java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip
>  (The system cannot find the file specified)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:119)
>   at 
> org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke()
>   at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>   at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
>   at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
>   at 
> org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke()
>   at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>   at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
>   at 
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
>   at 
> com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
>   at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
>   at sun.reflect.GeneratedMethodAccessor200.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:585)
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>   at sun.rmi.transport.Transport$1.run(Transport.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>   at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>   at java.lang.Thread.run(Thread.java:595)
>   Caused by: java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacj

[jira] Closed: (GERONIMODEVTOOLS-150) errant dependency in plugins/org.apache.geronimo.st.v20.core/pom.xml

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-150.
-

   Resolution: Fixed
Fix Version/s: 2.0

> errant dependency in plugins/org.apache.geronimo.st.v20.core/pom.xml
> 
>
> Key: GERONIMODEVTOOLS-150
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-150
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
>Priority: Minor
> Fix For: 2.0
>
> Attachments: GD-150.patch
>
>
> I don't think st.v20.core should depend on st.v12.core.
> I think this dependency can be removed from 
> plugins/org.apache.geronimo.st.v20.core/pom.xml:
> 
> org.apache.geronimo.devtools
> org.apache.geronimo.st.v12.core
> ${version}
> 
> I believe that the features should be segregated for configurability.
> I tested a build with this fix, and it seems to run fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3261) Modify pom.xml so that J2G automatically builds a deployable when the mvn install command is issued

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507965
 ] 

Sachin Patel commented on GERONIMO-3261:


The current packaging mechanism isn't technically incorrect.  Geronimo itself 
has a much more complex packaging mechanism, and thus some of the default maven 
assembly mechnism wouldn't work for it.  The current mechanism takes advantage 
of moduleSet's in the assembly descriptor and thus it keeps the maintaince of 
that file to a minium.  Everything in the plugins directory will be 
automatically be package for inclusion in the plugins directory and same goes 
for the feature.  If you moved the assembly as its own module, then you cannot 
use moduleSet's and would have to use dependency sets which you'll have to 
specifiy every single plugin and feature in the assembly's pom as a dependency 
as well redefining which subset of those you want in the assembly descriptor.

> Modify pom.xml so that J2G automatically builds a deployable when the mvn 
> install command is issued
> ---
>
> Key: GERONIMO-3261
> URL: https://issues.apache.org/jira/browse/GERONIMO-3261
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: J2G
>Reporter: Jason Warner
>Assignee: Jason Warner
>Priority: Minor
>
> J2G currently requires the use of the assembly:assembly command line argument 
> to build the deployable.  This should be changed to work similar to other 
> parts of geronimo.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [ANNOUNCE] Welcome Lin Sun as our newest committer

[Sachin Patel]

Congrats!!

-sachin


On Jun 21, 2007, at 2:32 PM, Davanum Srinivas wrote:


Folks,

We're pleased to let you know that we have a new committer in
our midst. Lin Sun has been active on the Web Services integration
for Geronimo for quite some time and has accepted our
invitation to join the Geronimo project as a committer.

Many Many apologies to Lin for the delay in announcing her as a  
committer!!


thanks,
dims

--
Davanum Srinivas :: http://davanum.wordpress.com

Re: [ANNOUNCE] Welcome Tim McConnell as our newest committer

[Sachin Patel]

Congrats!


-sachin


On Jun 21, 2007, at 6:36 PM, David Blevins wrote:


All,

The Geronimo PMC is pleased to announce that Tim McConnell has  
recently accepted our invitation to become an Apache Geronimo  
committer.  Tim has done some great work in 2.0 with regards to  
annotation processing and was a definite asset in completing the  
JavaEE 5 functionality.


We're thrilled to hand him a committer hat and look forward to his  
continued contributions to the project and to other contributors  
who wish to walk the same road he did.


Welcome aboard, Tim!

-David

[jira] Closed: (GERONIMODEVTOOLS-170) Can't start server with eclipse plugin with spaces in runtime location or vm directory

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-170.
-

Resolution: Fixed

patch applied

> Can't start server with eclipse plugin with spaces in runtime location or vm 
> directory
> --
>
> Key: GERONIMODEVTOOLS-170
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-170
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
> Environment: windows
>    Reporter: Ted Kirby
>Assignee: Sachin Patel
> Attachments: GD170.patch
>
>
> putting " around the -javaagent and -Djava.*.dirs parameters solves the 
> problem on windows.  I hope this also works on other platforms, as I'd hate 
> to have to add code to determine the platform...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: J2G Conversion tool got a makeover. Now what?

[Sachin Patel]

At this time as its currently implemented, I don't think it would  
make a good inside the UI.  The context you're working in the IDE is  
a "project" under development and J2G currently doesn't operate under  
this context.  There would be no real advantage to allow it to be  
invoked in the UI since it can't be operated on projects in the  
workspace.


If any integration into the UI then the proper approach and it would  
be fairly trivial is to go ahead with WTP integration...


All J2EE projects in WTP have a notion of a target runtime.  Every  
application is required to have its target runtime set (JBoss,  
WebSphere, Geronimo, etc..).  At any point in time you can retarget  
an applications runtime to a different one.  So if an application's  
runtime is set to JBoss, you can currently swap it over to Geronimo.   
This operation can be extended to perform any other tasks.  In our  
case, we would simply process the projects and traverse through the  
content running any migrations necessary.


I don't think this would be too hard to do.  Its just picking out the  
core peices currently inside J2G that actually do the migration on  
particular resources and wrapping those in 1 or more WTP operations.   
If this approach was taken I would be +1 to integrating this within  
the Eclipse Plugin.


hope that helps.

-sachin


On Jun 14, 2007, at 5:54 PM, Jason Warner wrote:


Paul,

Thanks for the feedback!

In regards to integration with the eclipse plugin, I don't believe  
that would be an easy task to accomplish.  From my understanding,   
the eclipse-plugin runs on top of WTP whereas the J2G tool is a  
headless plugin.  I believe the J2G tool would need to be rewritten  
using WTP to allow for integration.


As for a button or other GUI way of launching the tool, I think  
that's a great idea.  I'm still rather new to working with eclipse  
plugins, though, so I'm not quite sure how that could be done.  The  
tool is launched using a series of scripts, so perhaps a button  
that can launch these scripts would be feasible.  Anyone know of a  
better way?


Jason Warner


On 6/14/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Fantastic  
work, thanks for your contributions!


After all this testing and improvement we could consider moving J2G
from sandbox to a more stable location where it can be properly
released and maintained.  If our dev community expresses interest in
doing that then maybe the devtools subproject is a good place for
it.   Asking for feedback on the users list would help us know how to
proceed as well.

Thinking from the user's perspective, I wonder if J2G can be
integrated with our eclipse plugin somehow?  For example could our
eclipse plugin wrapper the J2G functionality in a wizard, button, or
context menu item?  Perhaps something simple for starters, just some
way launch the tool from inside the IDE.  Since J2G is itself
implemented as an eclipse plugin it would seem strange to provide no
UI controls for it or integration point with our current eclipse  
plugin.



Best wishes,
Paul

On Jun 14, 2007, at 2:26 PM, Jason Warner wrote:

> Some of you may have noticed the recent activity on the devlist in
> regards to the J2G conversion tool.  Erik Craig and I have been
> making significant improvements in the functionality and usability
> of this tool.  Some of these changes include adding new
> documentation on the wiki, fixing scripts to provide more
> functionality, ensuring unix functionality, and general debugging
> for both the code and the unit tests.  Now that these changes have
> been made, it might be appropriate to have another look at the tool
> and see if it is ready to be moved out of sandbox and into
> devtools.  Any and all comments are welcome.
>
> For those interested, here's a link to the documentation http://
> cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html

Re: Build failure "Error parsing web.xml for ."

[Sachin Patel]

Thats strange because I build fine on windows, but its happening on  
my mac..  i did clean my repo, but now that i think about it, i may  
have not scrubbed my tree clean.


I'll kick off a build and try again.

-sachin


On Jun 8, 2007, at 1:49 PM, Jeff Genender wrote:


Is this only happening in Windows?  I must admit I wrote this on a
Mac...if you can confirm, let me know and I (or Jason) shoul dbe  
able to

find the problem and squash this.

Jeff

Donald Woods wrote:

Did you mvn clean before rebuilding?

I'm still seeing weird behavior from the latest jspc-maven-plugin on
Windows and SLED10 if I build individual modules by hand w/o  
running mvn
clean first, like its adding duplicate  sections to the  
web.xml


-Donald

Sachin Patel wrote:
I keep hitting the following build error on LDAP Demo for Jetty,  
even

on a clean repo on mac os x.

Error prasing web.xml for .

Unexpected element: XML_DOC_OR_TEXT_DECL

-sachin

Build failure "Error parsing web.xml for ."

[Sachin Patel]

I keep hitting the following build error on LDAP Demo for Jetty, even  
on a clean repo on mac os x.


Error prasing web.xml for .

Unexpected element: XML_DOC_OR_TEXT_DECL

-sachin

[jira] Closed: (GERONIMODEVTOOLS-151) Need to build eclipse plugin so it can be installed via the eclipse update manager

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-151.
-

Resolution: Invalid

This is not really a bug.  This is the part of the normal release process.  
Once Geronimo is released, RC candidate drivers for the eclipse plugin will be 
made available for voting.  Once binaries are approved as part of the 
publishing process, a deployable.zip will be published as well as the 
features/plugins to the update site.

> Need to build eclipse plugin so it can be installed via the eclipse update 
> manager
> --
>
> Key: GERONIMODEVTOOLS-151
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-151
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
> Environment: all
>Reporter: Ted Kirby
>Priority: Blocker
>
> The package needs to be installed on the update site.  This support is 
> required for official 2.0 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-149) EAR deployment fails with Eclipse 3.3M7

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498325
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-149:
---

Its been broken in previous milestones as well.  We'll just have to wait for an 
integration build for a fix.

> EAR deployment fails with Eclipse 3.3M7
> ---
>
> Key: GERONIMODEVTOOLS-149
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-149
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Jacek Laskowski
>
> I'm working with
> [1] Eclipse 3.3M7
> [2] Apache Geronimo 2.0 - http://people.apache.org/~prasad/binaries/20070522/
> [3] 
> http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070523.0744-deployable.zip
> Deploying WAR file is fine, but EAR finishes with the following exception:
> Distribution of configuration failed.  See log for details.
>   java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip
>  (The system cannot find the file specified)
>   org.apache.geronimo.common.DeploymentException: 
> java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip
>  (The system cannot find the file specified)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:119)
>   at 
> org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke()
>   at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>   at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
>   at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
>   at 
> org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke()
>   at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>   at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
>   at 
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
>   at 
> com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
>   at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
>   at sun.reflect.GeneratedMethodAccessor200.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:585)
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>   at sun.rmi.transport.Transport$1.run(Transport.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>   at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>   at java.lang.Thread.run(Thread.java:595)
>   Caused by: java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05

[jira] Commented: (GERONIMODEVTOOLS-149) EAR deployment fails with Eclipse 3.3M7

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498318
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-149:
---

This is due to a bug in WTP.. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=188710

> EAR deployment fails with Eclipse 3.3M7
> ---
>
> Key: GERONIMODEVTOOLS-149
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-149
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Jacek Laskowski
>
> I'm working with
> [1] Eclipse 3.3M7
> [2] Apache Geronimo 2.0 - http://people.apache.org/~prasad/binaries/20070522/
> [3] 
> http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070523.0744-deployable.zip
> Deploying WAR file is fine, but EAR finishes with the following exception:
> Distribution of configuration failed.  See log for details.
>   java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip
>  (The system cannot find the file specified)
>   org.apache.geronimo.common.DeploymentException: 
> java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip
>  (The system cannot find the file specified)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:119)
>   at 
> org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke()
>   at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>   at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
>   at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
>   at 
> org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke()
>   at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>   at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
>   at 
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
>   at 
> com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
>   at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
>   at sun.reflect.GeneratedMethodAccessor200.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:585)
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>   at sun.rmi.transport.Transport$1.run(Transport.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>   at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>   at java.lang.Thread.run(Thread.java:595)
>   Caused by: java.io.FileNotFoundException: 
> C:\.eclipse\sandbox\.metadata\.plugins\org.apache.geronimo.st.core\server_23.05.07_00_570\aplikacjaEAR.zip

Re: Should DisconnectedDeploymentManager allow offline deployment?

[Sachin Patel]

no, I didn't read the spec..  I just assumed it was optional or  
something, rather then a spec violation. No I don't think it is  
currently using it.


thx

-sachin


On May 23, 2007, at 11:33 AM, David Jencks wrote:

Have you checked the specs on the disconnected deployment manager?   
IIRC by spec it can't deploy, distribute, undeploy, redeploy.  
or do anything except give you access to the DConfigBeans.


In particular the offline deployer should not be trying to use a  
disconnected deployment manager.  Is it currently?


thanks
david jencks

On May 23, 2007, at 6:33 AM, Sachin Patel wrote:

The distribute method of the DisconnectedDeploymentManager returns  
an IllegalStateException.  Should this still remain a restriction  
with the new offline deployment support? Or is there much more  
additional work required to support offline deployment through JSR88?


thx

-sachin

Should DisconnectedDeploymentManager allow offline deployment?

[Sachin Patel]

The distribute method of the DisconnectedDeploymentManager returns an  
IllegalStateException.  Should this still remain a restriction with  
the new offline deployment support? Or is there much more additional  
work required to support offline deployment through JSR88?


thx

-sachin

[jira] Closed: (GERONIMODEVTOOLS-146) Server won't start nicely due to missing setting of java.endorsed.dirs for Yoko

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-146.
-

   Resolution: Fixed
Fix Version/s: 2.0
 Assignee: Sachin Patel

Patch applied with formatting adjustments, thanks!!

> Server won't start nicely due to missing setting of java.endorsed.dirs for 
> Yoko
> ---
>
> Key: GERONIMODEVTOOLS-146
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-146
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
> Assigned To: Sachin Patel
>Priority: Critical
> Fix For: 2.0
>
> Attachments: GD146-2.patch, GD146-3.patch, GD146.patch
>
>
> Here are console messages:
> Booting Geronimo Kernel (in Java 1.5.0)...
> 17:03:26,609 ERROR [NameService] Incorrect level of org.omg.CORBA classes 
> found.
> Likely cause is an incorrect java.endorsed.dirs configuration
> 17:03:26,609 ERROR [GBeanInstanceState] Error while starting; GBean is now in 
> the FAILED state: 
> abstractName="org.apache.geronimo.configs/j2ee-corba-yoko/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-corba-yoko/2.0-SNAPSHOT/car,j2eeType=CORBANameService,name=NameServer"
> org.apache.geronimo.gbean.InvalidConfigurationException: CORBA usage requires 
> Yoko CORBA spec classes in java.endorsed.dirs classpath
>   at org.apache.geronimo.corba.NameService.doStart(NameService.java:168)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:986)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
> Need to set 
> -Djava.endorsed.dirs="%GERONIMO_BASE%\lib\endorsed;%JRE_HOME%\lib\endorsed", 
> like in geronimo.{sh,bat}
> If I set this manually as a server VM argument for the server instance, the 
> server starts fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: geronimo plan help

[Sachin Patel]

I don't know too much about the DConfigBean support but from a quick  
glance at the description one of the intents for DConfigBeans is to  
exploit its use through vendor tooling.  So regardless of what the  
underlying technology is being used to read/write the descriptor  
XMLBeans, EMF, or DConfigBeans, you should be able to create an  
Eclipse UI around any of the those.  There are certainly advantages  
and disadvantages to each and it could be that using DConigBeans is  
the best approach in the long run for both Geronimo and the Eclipse  
Plugin.  I wish I knew more about DConfigBeans and wether it can  
support things like in-memory writing of a plan and reverting  
changes, etc...


-sachin


On May 21, 2007, at 12:25 PM, David Jencks wrote:

Can the eclipse plan editors be based on jsr-88 DConfigBeans?  We  
certainly don't have complete DConfigBean support for our plans,  
but having an actual editor using them might provide some incentive  
to keep the jsr-88 support up to date and complete.  The more up to  
date parts of the deployment wizards in the admin console use  
DConfigBeans.


I think there's supposed to be some kind of generic dconfigbean  
based plan editor in NetBeans, but I've never tried it.


thanks
david jencks

On May 21, 2007, at 6:04 AM, Sachin Patel wrote:

The primary issue is based on past experiences I chose EMF as the  
modeling framework around the plans, but after several releases  
came to the quick realization that it was too heavyweight for our  
purpose.  This and the fact that are schemas each release have not  
been cumulative additions and this makes it painful to provide UI  
support for every version of the schema.  Thus I've unfortunately  
considered this a dying effort.  What I would like to eventually  
do is simplify at least the use of EMF and just use the XMLBeans  
generated code and generate the editors out of it.  There is a  
good bit of migration work to do this, but in the long wrong it  
would simplify this greatly as well as reduce some footprint.


The other option and one I like much better, is something we can  
do in addition but prior to rebuilding the editors is  to extend  
the XML structured text editor in WTP to build a custom deployment  
plan editor for eclipse that provides full dynamic content assist  
into our plans.  So though this won't provide a UI, it will  
provide a reliable XML editor that will correctly display element  
choices as you write your plans.  I think this would be much more  
valuable since it would provide 100% coverage and thus more used  
than the above and the maintainability would be a whole lot easier  
than maintaining a full set of form editors.


-sachin


On May 21, 2007, at 7:47 AM, Shiva Kumar H R wrote:

Please read Aaron's book on Geronimo http:// 
www.chariotsolutions.com/geronimo/geronimo-1.1/geronimo-html-one- 
page.html . I find it to be a great documentation for almost  
anything related to Geronimo Deployment Plans.


I can understand your frustrations. It's no different for me when  
it comes to manually creating Geronimo Deployment Plans.


I have always wished that Geronimo Development Tools (like  
Geronimo Eclipse Plug-in) provide some facility for auto-creating/ 
updating those deployment plans. I have created a wiki page  
summarizing my proposal:  http://cwiki.apache.org/GMOxPMGT/ 
geronimo-deployment-plans-how-to-simplify-creation-or-updation.html


Would be useful if you and other users/developers can provide  
feedback on it as well post new proposals if any on that page. I  
think it would be useful if I float a separate mail on User list  
for this.


- Shiva

On 5/19/07, Doug Lochart < [EMAIL PROTECTED]> wrote: Lin,

Thanks for trying to help.  I do appreciate it.  I may not have  
made my

questions/gripes clear.  So I will reiterate after your replies.

Lin Sun wrote:
> Hi, I am not a plan expert at all but I'll try answer your  
questions...

>
> What I find most useful besides reading the existing samples and
> documentations, is to use the schema files (generally located  
at the

> server_home\schema directory.)  For example, I am looking at my
> geronimo 2.0 server now, and the geronimo-module-{version}.xsd  
is the

> schema for namespace
> " http://geronimo.apache.org/xml/ns/deployment-{version} ".   
You 'll

> want to look at the geronimo-application-{version}.xsd for
> geronimo-application.xml file.
>
I have looked at the examples and what I have now is from them as  
well

as help from the forum.  What I am griping about is that even the
documents are syntactically described in the xsd they are not  
described
verbally as to what they mean or how they are used.  I can read  
and use

a schema but it doesn't help if I don;t know how or why I am
constructing the xml document.

The other issue I had was that I have an EAR with a WAR and EJB-JAR
inside.  Nowh

[jira] Commented: (GERONIMODEVTOOLS-146) Server won't start nicely due to missing setting of java.endorsed.dirs for Yoko

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497477
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-146:
---

Actually we already have getVMArgs on GeronimoServerDelegate so you can just 
override this in GeronimoServer.class in the 2.0 plugin, but be sure to prepend 
it to super.

> Server won't start nicely due to missing setting of java.endorsed.dirs for 
> Yoko
> ---
>
> Key: GERONIMODEVTOOLS-146
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-146
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
>Priority: Critical
> Attachments: GD146-2.patch, GD146.patch
>
>
> Here are console messages:
> Booting Geronimo Kernel (in Java 1.5.0)...
> 17:03:26,609 ERROR [NameService] Incorrect level of org.omg.CORBA classes 
> found.
> Likely cause is an incorrect java.endorsed.dirs configuration
> 17:03:26,609 ERROR [GBeanInstanceState] Error while starting; GBean is now in 
> the FAILED state: 
> abstractName="org.apache.geronimo.configs/j2ee-corba-yoko/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-corba-yoko/2.0-SNAPSHOT/car,j2eeType=CORBANameService,name=NameServer"
> org.apache.geronimo.gbean.InvalidConfigurationException: CORBA usage requires 
> Yoko CORBA spec classes in java.endorsed.dirs classpath
>   at org.apache.geronimo.corba.NameService.doStart(NameService.java:168)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:986)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
> Need to set 
> -Djava.endorsed.dirs="%GERONIMO_BASE%\lib\endorsed;%JRE_HOME%\lib\endorsed", 
> like in geronimo.{sh,bat}
> If I set this manually as a server VM argument for the server instance, the 
> server starts fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-146) Server won't start nicely due to missing setting of java.endorsed.dirs for Yoko

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497467
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-146:
---

Thanks for finding this bug, but I think we need to add getVMArgs method to 
IGeronimoServer interface and add these arguments there since this is release 
specific.

> Server won't start nicely due to missing setting of java.endorsed.dirs for 
> Yoko
> ---
>
> Key: GERONIMODEVTOOLS-146
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-146
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
>Priority: Critical
> Attachments: GD146-2.patch, GD146.patch
>
>
> Here are console messages:
> Booting Geronimo Kernel (in Java 1.5.0)...
> 17:03:26,609 ERROR [NameService] Incorrect level of org.omg.CORBA classes 
> found.
> Likely cause is an incorrect java.endorsed.dirs configuration
> 17:03:26,609 ERROR [GBeanInstanceState] Error while starting; GBean is now in 
> the FAILED state: 
> abstractName="org.apache.geronimo.configs/j2ee-corba-yoko/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-corba-yoko/2.0-SNAPSHOT/car,j2eeType=CORBANameService,name=NameServer"
> org.apache.geronimo.gbean.InvalidConfigurationException: CORBA usage requires 
> Yoko CORBA spec classes in java.endorsed.dirs classpath
>   at org.apache.geronimo.corba.NameService.doStart(NameService.java:168)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:986)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
> Need to set 
> -Djava.endorsed.dirs="%GERONIMO_BASE%\lib\endorsed;%JRE_HOME%\lib\endorsed", 
> like in geronimo.{sh,bat}
> If I set this manually as a server VM argument for the server instance, the 
> server starts fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Is there a Geronimo 2.0 version of the Eclipse plugin to run in Eclipse 3.3m7?

[Sachin Patel]

Yeah those warnings you can ignore.  It should build fine right after  
checking out with "mvn install".


-sachin


On May 21, 2007, at 9:24 AM, Jason Warner wrote:


Sachin,

I was trying to build this late friday and was unsuccesful.  I  
think it might be my own fault, though, so I'm going to tinker with  
it a little bit before complaining too much ; )


One thing I did notice is the following message popping up multiple  
times:


[WARNING] POM for 'org.apache.geronimo.modules:geronimo-web- 
builder:pom:2.0-SNAPSHOT:compile' is invalid. It will be ignored  
for artifact resolution.Reason: Failed to validate POM.


Thanks,

Jason Warner



On 5/21/07, Sachin Patel <[EMAIL PROTECTED]> wrote: Yeah try the  
one daily driver I updated last Friday.  All I did was

upgrade the packages and did not have a chance to do any testing.  If
it fails, let me know and fix up any issues.

thx

-sachin


On May 20, 2007, at 10:00 PM, Ted Kirby wrote:

> Jacek,
>
> I have just gotten the eclipse plugin to start Geronimo 2.0 with
> eclipse 3.3M6.
> The plugin was last changed on April 30, and several changes in AG
> have occurred since then.  I can start the server, but with two
> patches applied:  G3174, and GERONIMODEVTOOLS-146.  G3174 really
> applies to the plugin.
>
> G3174 changes to class to start AG, and GD-146 adds the
> java.endorsed.dirs property.  It looks like javaagent and
> java.ext.dirs should also be added to the start command from the
> plugin.
>
> On May 18, Sachin upgraded to 3.3M7.  I have not made that upgrade,
> and cannot speak to that level.  I presume the above two patches and
> other work I mentioned will be needed for 3.3M7.
>
> Ted Kirby
>
> On 5/20/07, Jacek Laskowski < [EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> Can I use the Eclipse plugin with Geronimo 2.0? What Eclipse  
version
>> do I need? I can't seem to run Eclipse 3.3M7 and Eclipse Plugin  
2.0.0

>> (g-eclipse-plugin-2.0.0-v20070517.1449-deployable) with the daily
>> build of Geronimo 2.0
>> (http://people.apache.org/~prasad/binaries/20070520/ ).
>>
>> Jacek
>>
>> --
>> Jacek Laskowski
>> http://www.JacekLaskowski.pl
>>

Re: Is there a Geronimo 2.0 version of the Eclipse plugin to run in Eclipse 3.3m7?

[Sachin Patel]

Nevermind, don't try that driver its broken. Publishing a new one  
that should fix the issue.


-sachin


On May 21, 2007, at 8:47 AM, Sachin Patel wrote:

Yeah try the one daily driver I updated last Friday.  All I did was  
upgrade the packages and did not have a chance to do any testing.   
If it fails, let me know and fix up any issues.


thx

-sachin


On May 20, 2007, at 10:00 PM, Ted Kirby wrote:


Jacek,

I have just gotten the eclipse plugin to start Geronimo 2.0 with  
eclipse 3.3M6.

The plugin was last changed on April 30, and several changes in AG
have occurred since then.  I can start the server, but with two
patches applied:  G3174, and GERONIMODEVTOOLS-146.  G3174 really
applies to the plugin.

G3174 changes to class to start AG, and GD-146 adds the
java.endorsed.dirs property.  It looks like javaagent and
java.ext.dirs should also be added to the start command from the
plugin.

On May 18, Sachin upgraded to 3.3M7.  I have not made that upgrade,
and cannot speak to that level.  I presume the above two patches and
other work I mentioned will be needed for 3.3M7.

Ted Kirby

On 5/20/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote:

Hi,

Can I use the Eclipse plugin with Geronimo 2.0? What Eclipse version
do I need? I can't seem to run Eclipse 3.3M7 and Eclipse Plugin  
2.0.0

(g-eclipse-plugin-2.0.0-v20070517.1449-deployable) with the daily
build of Geronimo 2.0
(http://people.apache.org/~prasad/binaries/20070520/).

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Closed: (GERONIMODEVTOOLS-147) Geronimo box picture of New Server wizard shows Version 1.1, but is for Apache Geronimo v2.0

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-147.
-

Resolution: Fixed

I was playing around with using the box images, and accidenly published a 
driver with the new image. This has been reverted.  

> Geronimo box picture of New Server wizard shows Version 1.1, but is for 
> Apache Geronimo v2.0
> 
>
> Key: GERONIMODEVTOOLS-147
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-147
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 2.0
> Environment: g-eclipse-plugin-2.0.0-v20070517.1449-deployable.zip
>Reporter: Jacek Laskowski
>
> The Geronimo box picture on the second page of the New Server wizard shows 
> Version 1.1 whereas the plugin is for Apache Geronimo v2.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMODEVTOOLS-148) Can't start server with eclipse plugin

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-148.
-

   Resolution: Fixed
Fix Version/s: 2.0

Patch applied, thanks!

> Can't start server with eclipse plugin
> --
>
> Key: GERONIMODEVTOOLS-148
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-148
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
> Assigned To: Sachin Patel
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: GD148.patch
>
>
> Exception in thread "main" java.lang.IllegalArgumentException: Argument type 
> is [class [Ljava.lang.String;]; expected [class 
> org.apache.geronimo.cli.daemon.DaemonCLParser]
> at 
> org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:56)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:33)
> See G3174 https://issues.apache.org/jira/browse/GERONIMO-3174.
> At first, I did not know if it was an AG or devtools problem.  Now, I think 
> it is a devtools problem.  Per Donald Woods in G3174, I am opening up this 
> devtools JIRA.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMODEVTOOLS-148) Can't start server with eclipse plugin

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel reassigned GERONIMODEVTOOLS-148:
-

Assignee: Sachin Patel

> Can't start server with eclipse plugin
> --
>
> Key: GERONIMODEVTOOLS-148
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-148
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.0
>Reporter: Ted Kirby
> Assigned To: Sachin Patel
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: GD148.patch
>
>
> Exception in thread "main" java.lang.IllegalArgumentException: Argument type 
> is [class [Ljava.lang.String;]; expected [class 
> org.apache.geronimo.cli.daemon.DaemonCLParser]
> at 
> org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:56)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
> at 
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:33)
> See G3174 https://issues.apache.org/jira/browse/GERONIMO-3174.
> At first, I did not know if it was an AG or devtools problem.  Now, I think 
> it is a devtools problem.  Per Donald Woods in G3174, I am opening up this 
> devtools JIRA.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: geronimo plan help

[Sachin Patel]

The primary issue is based on past experiences I chose EMF as the  
modeling framework around the plans, but after several releases came  
to the quick realization that it was too heavyweight for our  
purpose.  This and the fact that are schemas each release have not  
been cumulative additions and this makes it painful to provide UI  
support for every version of the schema.  Thus I've unfortunately  
considered this a dying effort.  What I would like to eventually do  
is simplify at least the use of EMF and just use the XMLBeans  
generated code and generate the editors out of it.  There is a good  
bit of migration work to do this, but in the long wrong it would  
simplify this greatly as well as reduce some footprint.


The other option and one I like much better, is something we can do  
in addition but prior to rebuilding the editors is  to extend the XML  
structured text editor in WTP to build a custom deployment plan  
editor for eclipse that provides full dynamic content assist into our  
plans.  So though this won't provide a UI, it will provide a reliable  
XML editor that will correctly display element choices as you write  
your plans.  I think this would be much more valuable since it would  
provide 100% coverage and thus more used than the above and the  
maintainability would be a whole lot easier than maintaining a full  
set of form editors.


-sachin


On May 21, 2007, at 7:47 AM, Shiva Kumar H R wrote:

Please read Aaron's book on Geronimo http:// 
www.chariotsolutions.com/geronimo/geronimo-1.1/geronimo-html-one- 
page.html . I find it to be a great documentation for almost  
anything related to Geronimo Deployment Plans.


I can understand your frustrations. It's no different for me when  
it comes to manually creating Geronimo Deployment Plans.


I have always wished that Geronimo Development Tools (like Geronimo  
Eclipse Plug-in) provide some facility for auto-creating/updating  
those deployment plans. I have created a wiki page summarizing my  
proposal:  http://cwiki.apache.org/GMOxPMGT/geronimo-deployment- 
plans-how-to-simplify-creation-or-updation.html


Would be useful if you and other users/developers can provide  
feedback on it as well post new proposals if any on that page. I  
think it would be useful if I float a separate mail on User list  
for this.


- Shiva

On 5/19/07, Doug Lochart < [EMAIL PROTECTED]> wrote: Lin,

Thanks for trying to help.  I do appreciate it.  I may not have  
made my

questions/gripes clear.  So I will reiterate after your replies.

Lin Sun wrote:
> Hi, I am not a plan expert at all but I'll try answer your  
questions...

>
> What I find most useful besides reading the existing samples and
> documentations, is to use the schema files (generally located at the
> server_home\schema directory.)  For example, I am looking at my
> geronimo 2.0 server now, and the geronimo-module-{version}.xsd is  
the

> schema for namespace
> " http://geronimo.apache.org/xml/ns/deployment-{version} ".  You 'll
> want to look at the geronimo-application-{version}.xsd for
> geronimo-application.xml file.
>
I have looked at the examples and what I have now is from them as well
as help from the forum.  What I am griping about is that even the
documents are syntactically described in the xsd they are not  
described
verbally as to what they mean or how they are used.  I can read and  
use

a schema but it doesn't help if I don;t know how or why I am
constructing the xml document.

The other issue I had was that I have an EAR with a WAR and EJB-JAR
inside.  Nowhere in the documentation did it cover the rules of what
plans are required.  Almost all examples attacke either a WAR or EJB
alone.  The one example that starts doing an EAR is never completed.

So when I was creating mine I had a geronimo-application.xml (which I
kept outside the ear), a geronimo-web.xml in the WAR, and an
openejb-jar.xml in the ejb.jar.  One forum member asked me to  
remove the

geronimo-web.  It seemed to not break anything and I think it may have
made things go farther but again I still have no clue what  
combinations

(or why) of geronimo specific plans are required in an ear.

> Doug Lochart wrote:
>
>>
>> openejb-jar xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1 ">
>>  > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1";>
>>
>>  qdfrancepolicy.
>>  FrancePolicyServverEjb
>>  1.0
>>  car
>>
>>
>>  
>>geronimo
>>tomcat
>>car
>>  
>>
>>
>>
>>  
>>  
>>
>>  FrancePolicyServer
>>  qdfrancepolicy.FrancePolicyHome 
>>
>>  
>> 
>>
>> Is the dep:groupId supposed to match the sys:groupID on the  
app?  If
>> not how is it used?  What does artifactid do?  Does it matter  
what I
>> name it?  Does the name have to correspond to another field  
somewhere?

>
> No, it needs to be dep:groupId here as you had " > xmlns:dep=" http://geronimo.apache.org/xml/ns/deployment-1.1";>"
> defined earlier.

Re: Is there a Geronimo 2.0 version of the Eclipse plugin to run in Eclipse 3.3m7?

[Sachin Patel]

Yeah try the one daily driver I updated last Friday.  All I did was  
upgrade the packages and did not have a chance to do any testing.  If  
it fails, let me know and fix up any issues.


thx

-sachin


On May 20, 2007, at 10:00 PM, Ted Kirby wrote:


Jacek,

I have just gotten the eclipse plugin to start Geronimo 2.0 with  
eclipse 3.3M6.

The plugin was last changed on April 30, and several changes in AG
have occurred since then.  I can start the server, but with two
patches applied:  G3174, and GERONIMODEVTOOLS-146.  G3174 really
applies to the plugin.

G3174 changes to class to start AG, and GD-146 adds the
java.endorsed.dirs property.  It looks like javaagent and
java.ext.dirs should also be added to the start command from the
plugin.

On May 18, Sachin upgraded to 3.3M7.  I have not made that upgrade,
and cannot speak to that level.  I presume the above two patches and
other work I mentioned will be needed for 3.3M7.

Ted Kirby

On 5/20/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote:

Hi,

Can I use the Eclipse plugin with Geronimo 2.0? What Eclipse version
do I need? I can't seem to run Eclipse 3.3M7 and Eclipse Plugin 2.0.0
(g-eclipse-plugin-2.0.0-v20070517.1449-deployable) with the daily
build of Geronimo 2.0
(http://people.apache.org/~prasad/binaries/20070520/).

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: www.ibm.com namespace in j2g migration tool

[Sachin Patel]

Yes, all IBM references should be removed.

-sachin


On May 17, 2007, at 1:13 PM, Jason Warner wrote:

I was looking through the code for the j2g migration tool that  
currently resides in the sandbox.  I noticed that for the XML  
conversion it seems that it uses a namespace of "http://www.ibm.com/ 
j2g ".  Am I correct in thinking that this is something that should  
definitely be changed?



Thanks,

Jason Warner

Re: MEJBGBean startup error

[Sachin Patel]

Its harmless, but openejb needs to squash it.

-sachin


On May 15, 2007, at 10:52 AM, Tim McConnell wrote:

Hi, is anyone else getting this error when starting the server ??  
It doesn't seem to harm anything (as best I can tell) but it is a  
little disconcerting.



java.net.MalformedURLException: no protocol: MEJBGBean
at java.net.URL.(URL.java:567)
at java.net.URL.(URL.java:464)
at java.net.URL.(URL.java:413)
at org.apache.openejb.config.AnnotationDeployer 
$DiscoverBeansInClassLoader.deploy(AnnotationDeployer.java:190)
at org.apache.openejb.config.AnnotationDeployer 
$DiscoverBeansInClassLoader.deploy(AnnotationDeployer.java:167)
at org.apache.openejb.config.AnnotationDeployer.deploy 
(AnnotationDeployer.java:158)
at org.apache.openejb.config.ConfigurationFactory 
$Chain.deploy(ConfigurationFactory.java:110)
at  
org.apache.openejb.config.ConfigurationFactory.configureApplication 
(ConfigurationFactory.java:311)
at  
org.apache.openejb.config.ConfigurationFactory.configureApplication 
(ConfigurationFactory.java:298)


--
Thanks,
Tim McConnell

Re: A session I presented at ApacheCon on J2EE App development using Eclipse

[Sachin Patel]

The update manager needs to remain the official means of  
installation.  The zip distributions are available and we'll continue  
to make them available, but this should not be and will not be as a  
documented installation method.  The don't see your server link  
automatically chooses a default mirror location, so the cause of your  
slow downloads is most likely due to the mirror not being the ideal  
server for your location.  Thus you can always use the update manager  
directly as the website suggests so that you can select a mirror of  
your choosing.  A zip distribution provides, no validation, no  
dependency checking, no install location preference, and does not  
automatically refresh the plugin cache when extracted, so a restart  
will not load the plugins if previous versions of the plugin  
existed.  Thus it should remain only a alternate install mechanism  
that only individuals familiar with eclipse should use.


-sachin


On May 11, 2007, at 4:09 PM, Shiva Kumar H R wrote:


I suspect your network connectivity is too good :-)

Here is an experiment I tried:
Connected from Home with a Mobile Internet Connectivity of 230Kbps  
( :-( that's the best Home connectivity I can get in my place) and  
tried downloading Geronimo Eclipse Plug-in by clicking on "Don't  
see your server listed" link. After about 25mins and 7.1MB of  
download volume Plug-in installation failed with a Network  
Connection Error. When I tried again (thank God, download restarted  
from where it last failed) it took another 25mins for an additional  
download volume of 7.8 MB with 3 restarts!


After this I tried downloading a zip of eclipse plug-in (http:// 
people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse- 
plugin-2.0.0-v20070430.1413-deployable.zip ) using a download  
accelerator. This time it took 50mins for 17MB of download volume  
to complete and there were no download errors.


In addition being able to download a zip allows me to backup a copy  
of the setup for later use, which wouldn't be trivial if I use  
automatic download by IDE.


We probably can recommend users to install via Eclipse update site,  
yet make available a zip of eclipse plug-in for direct download.  
What do you say?


We probably can also work to reduce the size of Geronimo Eclipse  
Plug-in.


- Shiva

On 5/10/07, Lin Sun <[EMAIL PROTECTED]> wrote:
Just one comment here...  When I last tried to download the geronimo
eclipse plugin, it was not slow at all.  I don't really see much
difference of using the eclipse update manager vs. go to the site to
download the zip file.   I think the preferred way is to use the  
eclipse

update site as it can install/update the feature and its dependencies
automatically on the fly.

Lin

Shiva Kumar H R wrote:

> A few observations I made as a User of Geronimo Eclipse Plug-in:
> 1) Downloading Geronimo Eclipse Plugin from within the IDE (by  
clicking
> on the "Don't see your server listed?" or by creating a new  
remote site

> in the update manager) is too slow.
>
> It would save a lot of time if I can simply download a zip of  
Geronimo

> Eclipse Plug-in say from
> http://geronimo.apache.org/development-tools.html (similar to the  
way I

> can download zips of most Eclipse Plug-ins from eclipse.org
> ).
>

Help with MEJB

[Sachin Patel]

I need some help finishing up the MEJB support.  I have the EJB  
implementation in openejb, and a GBean wrapper in configs/openejb  
that creates and EJBJar with this stateless session bean and deploys  
it like below...


EjbJar ejbJar = new EjbJar();
StatelessBean bean = ejbJar.addEnterpriseBean(new StatelessBean 
("MEJB",MEJBBean.class.getName()));

bean.setHomeAndRemote(MEJBHome.class, Management.class);

ClassLoader cl = MEJBBean.class.getClassLoader();
OpenEjbSystem openEjbSystem = ejbContainer.getOpenEjbSystem();
EjbJarInfo ejbJarInfo = openEjbSystem.configureApplication(new  
EjbModule(cl, getClass().getSimpleName(), null, ejbJar, null));

openEjbSystem.createEjbJar(ejbJarInfo, cl);

After this, the applications with an ejb/MEJB ejbref fail to deploy  
and I assume we need to take one additional step and properly bind  
the ejb.  I haven't been able to figure out on how to look up this  
bean as is and what the defaults, if any, are.


Could someone provide some guidance and how to programatically  
enhance this so that applications with an ejbref to it don't require  
a vendor plan and lookup to java:/comp/env/ejb/MEJB resolves?


Thanks.

-sachin

Re: server startup problems with yoko

[Sachin Patel]

Ok, thanks. I guess I'll have to start using the scripts.

-sachin


On May 7, 2007, at 12:41 PM, Jay D. McHugh wrote:


Sachin,

I was having that problem, but only when I tried to start the  
server 'directly'.


When I used the scripts, it started fine.

I have needed to to this for builds done within the past 7-10 days  
or so.



Jay

Sachin Patel wrote:

I'm running into the following starting the server...

[*>  ] 79%  68s Starting  
org.apache.ger...11:43:40,654 ERROR [NameService] Incorrect level  
of org.omg.CORBA classes found.

Likely cause is an incorrect java.endorsed.dirs configuration
11:43:40,657 ERROR [GBeanInstanceState] Error while starting;  
GBean is now in the FAILED state:  
abstractName="org.apache.geronimo.configs/j2ee-corba-yoko/2.0- 
SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-corba- 
yoko/2.0-SNAPSHOT/car,j2eeType=CORBANameService,name=NameServer"
org.apache.geronimo.gbean.InvalidConfigurationException: CORBA  
usage requires Yoko CORBA spec classes in java.endorsed.dirs  
classpath
at org.apache.geronimo.corba.NameService.doStart 
(NameService.java:168)
at  
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance 
(GBeanInstance.java:986)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart 
(GBeanInstanceState.java:267)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstance.start 
(GBeanInstance.java:529)
at  
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart 
(GBeanDependency.java:111)
at  
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget 
(GBeanDependency.java:146)
at org.apache.geronimo.gbean.runtime.GBeanDependency 
$1.running(GBeanDependency.java:120)
at  
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve 
nt(BasicLifecycleMonitor.java:173)
at  
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300 
(BasicLifecycleMonitor.java:41)
at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor 
$RawLifecycleBroadcaster.fireRunningEvent 
(BasicLifecycleMonitor.java:251)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart 
(GBeanInstanceState.java:292)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
(GBeanInstanceState.java:102)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive 
(GBeanInstanceState.java:124)
at  
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive 
(GBeanInstance.java:543)
at  
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean 
(BasicKernel.java:379)
at  
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio 
nGBeans(ConfigurationUtil.java:437)
at  
org.apache.geronimo.kernel.config.KernelConfigurationManager.start 
(KernelConfigurationManager.java:188)
at  
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon 
figuration(SimpleConfigurationManager.java:530)
at  
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon 
figuration(



-sachin

Re: server startup problems with yoko

[Sachin Patel]

java -jar server.jar

-sachin


On May 7, 2007, at 12:21 PM, Rick McGuire wrote:

How are you starting up the server?  Have you verified that the  
yoko-spec-corba jar file is in the lib/endorsed directory and that  
lib/endorsed is getting added to the java.endorsed.dirs path?


Rick


Sachin Patel wrote:

I'm running into the following starting the server...

[*>  ] 79%  68s Starting  
org.apache.ger...11:43:40,654 ERROR [NameService] Incorrect level  
of org.omg.CORBA classes found.

Likely cause is an incorrect java.endorsed.dirs configuration
11:43:40,657 ERROR [GBeanInstanceState] Error while starting;  
GBean is now in the FAILED state:  
abstractName="org.apache.geronimo.configs/j2ee-corba-yoko/2.0- 
SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-corba- 
yoko/2.0-SNAPSHOT/car,j2eeType=CORBANameService,name=NameServer"
org.apache.geronimo.gbean.InvalidConfigurationException: CORBA  
usage requires Yoko CORBA spec classes in java.endorsed.dirs  
classpath
at org.apache.geronimo.corba.NameService.doStart 
(NameService.java:168)
at  
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance 
(GBeanInstance.java:986)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart 
(GBeanInstanceState.java:267)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstance.start 
(GBeanInstance.java:529)
at  
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart 
(GBeanDependency.java:111)
at  
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget 
(GBeanDependency.java:146)
at org.apache.geronimo.gbean.runtime.GBeanDependency 
$1.running(GBeanDependency.java:120)
at  
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve 
nt(BasicLifecycleMonitor.java:173)
at  
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300 
(BasicLifecycleMonitor.java:41)
at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor 
$RawLifecycleBroadcaster.fireRunningEvent 
(BasicLifecycleMonitor.java:251)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart 
(GBeanInstanceState.java:292)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
(GBeanInstanceState.java:102)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive 
(GBeanInstanceState.java:124)
at  
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive 
(GBeanInstance.java:543)
at  
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean 
(BasicKernel.java:379)
at  
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio 
nGBeans(ConfigurationUtil.java:437)
at  
org.apache.geronimo.kernel.config.KernelConfigurationManager.start 
(KernelConfigurationManager.java:188)
at  
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon 
figuration(SimpleConfigurationManager.java:530)
at  
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon 
figuration(



-sachin

server startup problems with yoko

[Sachin Patel]

I'm running into the following starting the server...

[*>  ] 79%  68s Starting org.apache.ger... 
11:43:40,654 ERROR [NameService] Incorrect level of org.omg.CORBA  
classes found.

Likely cause is an incorrect java.endorsed.dirs configuration
11:43:40,657 ERROR [GBeanInstanceState] Error while starting; GBean  
is now in the FAILED state: abstractName="org.apache.geronimo.configs/ 
j2ee-corba-yoko/2.0-SNAPSHOT/car? 
ServiceModule=org.apache.geronimo.configs/j2ee-corba-yoko/2.0- 
SNAPSHOT/car,j2eeType=CORBANameService,name=NameServer"
org.apache.geronimo.gbean.InvalidConfigurationException: CORBA usage  
requires Yoko CORBA spec classes in java.endorsed.dirs classpath
at org.apache.geronimo.corba.NameService.doStart 
(NameService.java:168)
at  
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance 
(GBeanInstance.java:986)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart 
(GBeanInstanceState.java:267)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstance.start 
(GBeanInstance.java:529)
at  
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart 
(GBeanDependency.java:111)
at  
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget 
(GBeanDependency.java:146)
at org.apache.geronimo.gbean.runtime.GBeanDependency 
$1.running(GBeanDependency.java:120)
at  
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent( 
BasicLifecycleMonitor.java:173)
at  
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300 
(BasicLifecycleMonitor.java:41)
at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor 
$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java: 
251)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart 
(GBeanInstanceState.java:292)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start 
(GBeanInstanceState.java:102)
at  
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive 
(GBeanInstanceState.java:124)
at  
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive 
(GBeanInstance.java:543)
at  
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean 
(BasicKernel.java:379)
at  
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGB 
eans(ConfigurationUtil.java:437)
at  
org.apache.geronimo.kernel.config.KernelConfigurationManager.start 
(KernelConfigurationManager.java:188)
at  
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfig 
uration(SimpleConfigurationManager.java:530)
at  
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfig 
uration(



-sachin

Re: Naming the servers

[Sachin Patel]

+1

-sachin


On May 4, 2007, at 10:52 AM, Paul McMahan wrote:



On May 4, 2007, at 10:45 AM, David Jencks wrote:

2. I think the predominant use of uncustomized geronimo will be as  
a single server so I'm reluctant to, for this use, hide "var"  
under a couple more directories.  It would certainly make my use  
of geronimo more complicated.  I'm worried that to make life a  
little easier for advanced users we may be making it more  
complicated for beginners.  What do other people think?


I agree.  I think Ideally this new feature would be invisible  
unless a user decides to user it.


Best wishes,
Paul

Re: Naming the servers

[Sachin Patel]

I'm not sure how others feel, on paper geronimo0 sounds fine but when  
I cd into the actual distribution and the first my eye catches is a  
geronimo0 folder and seems more like a typo error to me.


What about just geronimo-default, or default-instance, or just  
default?  Or perhaps an instances folder, with geronimo0 inside.  I  
just have an issue with geronimo0 as a root folder.


-sachin


On May 4, 2007, at 7:50 AM, Anita Kulshreshtha wrote:


  I have committed changes in rev 535158. The name of the default
instance is now 'geronimo0', i.e. its 'var' is at geronimo0/var. This
has been tested only on windows. I do not expect any problems with  
this

change.. In case of a problem, creating an empty var/temp should help.

Thanks
Anita

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Re: CXF - jaxb-impl 2.0.5 dependency missing

[Sachin Patel]

I don't think 2.05 is published anywhere, or atleast where I could  
find, and we have an exclusion on cxf-tools-common to exlude it.  You  
may have not updated to pick up this exclude, or the exclude isn't  
working.


-sachin


On May 3, 2007, at 9:14 AM, Gianny Damour wrote:


Hi,

New CXF snapshots have been deployed and they seem to depend on  
com.sun.xml.bind:jaxb-impl:jar:2.0.5:


1) com.sun.xml.bind:jaxb-impl:jar:2.0.5

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=com.sun.xml.bind - 
DartifactId=jaxb-impl \

  -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
1) org.apache.geronimo.modules:geronimo-cxf:jar:2.0-SNAPSHOT
2) org.apache.cxf:cxf-rt-transports-http:jar:2.0-incubator- 
SNAPSHOT

3) org.apache.cxf:cxf-tools-common:jar:2.0-incubator-SNAPSHOT
4) com.sun.xml.bind:jaxb-impl:jar:2.0.5

Where can I get this version?

Thanks,
Gianny

Re: web site update

[Sachin Patel]

+1.

-sachin


On May 1, 2007, at 4:21 PM, Jason Dillon wrote:

I'd still like to see things organized in the same way that  
AcitveMQ does:

Fwd: [wtp-dev] New Axis2 Web services tools in WTP 2.0

[Sachin Patel]

FYI, the axis2 runtime is now supported in the driver indicated.  You  
can use the Geronimo WTP Server Adapter daily drivers to target  
Geronimo through these wizards.


If there are integration issues with Geronimo, please open JIRA's  
against GERONIMODEVTOOLS as usual.


thx.

-sachin


Begin forwarded message:


From: Kathy Chan <[EMAIL PROTECTED]>
Date: April 26, 2007 5:07:34 PM EDT
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],  
[EMAIL PROTECTED]

Subject: [wtp-dev] New Axis2 Web services tools in WTP 2.0
Reply-To: "General discussion of project-wide or architectural  
issues." <[EMAIL PROTECTED]>



Hi,

Please note that the Axis2 [1] Web services runtime is now  
supported by the Web services tools in this week's WTP 2.0  
integration driver.  You can now create bottom-up, top-down Axis2  
Web service and  Axis2 Web service client using the Web services  
tools that is currently in WTP.


This is the result of the initial contribution by WSO2 [2] to  
integrate Axis2 into WTP (RFE 165664) [3] and includes the  
following RFEs:


- 168762 - Create Axis2 bottom-up and top-down Java Web service. [4]
- 172186 - Create Axis2 Web service client. [5]
- 168765 - User-specified Axis2 runtime location. [6]
- 168766 - Adding Axis2 facet. [7]
- 168937 - Axis2 preference page. [8]

Please refer to the "Axis2 integration in WTP" wiki [9] for more  
information on the ongoing Axis2 integration effort and for RFEs  
being considered for post-WTP 2.0.


Two new Axis2 Web services tools tutorials have been created under  
the Web Services tutorials section in the WTP Web site:


- Creating bottom-up Axis2 Web service [10]
- Creating top-down Axis2 Web service [11]

In addition, a Webinar "Introduction to Web services tools in  
WTP" [12] will be held on May 3 at 3:00 pmGMT (11:00 EST).  This  
would include a demonstration of the Axis2 Web services tools.


[1] http://ws.apache.org/axis2/
[2] http://wso2.com/
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=165664
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=168762
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=172186
[6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=168765
[7] https://bugs.eclipse.org/bugs/show_bug.cgi?id=168766
[8] https://bugs.eclipse.org/bugs/show_bug.cgi?id=168937
[9] http://wiki.eclipse.org/index.php/Axis2_Integration_in_WTP
[10]  http://www.eclipse.org/webtools/community/tutorials/ 
BottomUpAxis2WebService/bu_tutorial.html
[11] http://www.eclipse.org/webtools/community/tutorials/ 
TopDownAxis2WebService/td_tutorial.html

[12] http://live.eclipse.org/node/251

Thanks goes to Lahiru Sandakith for making the contribution and for  
Sanjiva Weerawarana for supporting WSO2's contribution of Axis2  
tools into Eclipse WTP!


Regards,

Kathy Chan
Rational Java Web Services, IBM Toronto Lab
D3-354, D3/R8V/8200/MKM, 8200 Warden Avenue, Markham, Ontario,  
Canada, L6G 1C7
[EMAIL PROTECTED], (905) 413-3022, tieline: 969-6038, fax: (905)  
413-4920

___
wtp-dev mailing list
[EMAIL PROTECTED]
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: M5 Build Error

[Sachin Patel]

You'll need to -Dstage=bootstrap first.

-sachin


On Apr 26, 2007, at 1:40 PM, Tim McConnell wrote:

Hi, I'm not able to build M5 using an empty M2 repo. Does anyone  
know where I can pickup this Plugin ??


[INFO]  
-- 
--

[ERROR] BUILD ERROR
[INFO]  
-- 
--
[INFO] Plugin could not be found - check that the goal name is  
correct: Unable to download the artifact from any repository


Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.plugins - 
DartifactId=car-maven-plugin \

-Dversion=2.0-M5 -Dpackaging=maven-plugin -Dfile=/path/to/file


  org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0-M5


--
Thanks,
Tim McConnell

Re: [DISCUSS] 2.0-M5 (rc1) binaries available

[Sachin Patel]

I would not have any objection to doing this.  The reason being we  
have no formal test process in place for our milestone drivers and GA  
releases as everyone has a different opinion as to what constitutes a  
+1.  Until we have a process in place and are in agreement of what  
defines a daily, integration, milestone, and GA release a non-voting  
weekly unstable driver is a good idea.


-sachin


On Apr 26, 2007, at 1:05 PM, Matt Hogstrom wrote:

Here is a question to ponder.  Would anyone object if I simply made  
these binaries available from people as a monthly unstable  
release?  Given the amount of time it takes to spin this up and  
vote I'd rather just pick an svn version and make it available.  I  
think it burns up a lot of people's time to follow the release  
process.  Simply pop out the binary, let people play with it and if  
things are broken there is always trunk.  Perhaps we could move to  
a weekly unstable.


Anyway, I'd like some thoughts on this.


On Apr 26, 2007, at 2:39 AM, Matt Hogstrom wrote:


Starting DISCUSS thread if necessary for this release.

Re: [VOTE] 2.0-M5 rc1 binaries available for review and vote.

[Sachin Patel]

+1

-sachin


On Apr 26, 2007, at 2:38 AM, Matt Hogstrom wrote:

The 2.0-M5 binaries are available at http://people.apache.org/ 
~hogstrom/2.0-M5-rc1


The binaries addressed a problem seen in 2.0-M4 which was  
subsequently scrubbed where 2.0-Mn and 2.0-Mn-SNAPSHOT binaries  
were included.  Building with a clean repo has resolved that issue.


It is possible to build this release but as it is dependent on  
SNAPSHOTs it is not expected that it will have a long lived  
repeatable build (as has been the case in previous Milestones).   
Given that SNAPSHOTs are really for users to pick up a work in  
progress this should not be an issues as a new Milestone will  
generally be available in the next 30 days.


Thanks for taking time to review these binaries.

Please use this thread for your vote and the DISCUSS thread for  
comments.  Thanks


[ ] +1 Approve the binaries for release
[ ] 0
[ ] -1 Do not ship binaries.

This vote will conclude on April 29th at 0300 ET unless superceded  
by a new -rc vote.

Re: J2G Mavenized

[Sachin Patel]

done

-sachin


On Apr 23, 2007, at 8:05 PM, Jason Dillon wrote:

If the tests fail, then you should set truemaven.test.skip> in the top-level pom.


Its very bad practice to use -Dmaven.test.skip=true as something  
one might automatically add to every mvn invocation.


--jason


On Apr 23, 2007, at 4:58 PM, Sachin Patel wrote:

I've finished mavenizing the J2G contribution and the assembly can  
be generated with:


mvn install -Dmaven.test.skip=true assembly:assembly

The tests fail currently, so you'll have to disable them.

I only worked on mavenizing the build and packaging and have not  
looked into any usage or functional issues.  So though it  
compiles, it may or may not run.  If someone else in the community  
or if the original contributers wants to pick up where I left off,  
this would be great.  Let me know and I can open a JIRA component  
if one doesn't exist already, and patches can be submitted through  
it.


thanks.

-sachin

J2G Mavenized

[Sachin Patel]

I've finished mavenizing the J2G contribution and the assembly can be  
generated with:


mvn install -Dmaven.test.skip=true assembly:assembly

The tests fail currently, so you'll have to disable them.

I only worked on mavenizing the build and packaging and have not  
looked into any usage or functional issues.  So though it compiles,  
it may or may not run.  If someone else in the community or if the  
original contributers wants to pick up where I left off, this would  
be great.  Let me know and I can open a JIRA component if one doesn't  
exist already, and patches can be submitted through it.


thanks.

-sachin

[jira] Closed: (GERONIMODEVTOOLS-143) Remove OpenEJB reference from plugins/org.apache.geronimo.runtime.v20/LICENSE

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-143.
-

   Resolution: Fixed
Fix Version/s: 2.0

> Remove OpenEJB reference from plugins/org.apache.geronimo.runtime.v20/LICENSE
> -
>
> Key: GERONIMODEVTOOLS-143
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-143
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ted Kirby
> Fix For: 2.0
>
>
> This LICENSE file is the same for the 10, 11 and 12 runtimes.
> However, these runtimes include openejb-builder, and the 20 runtime does not.
> Therefore, the OpenEJB reference may be removed from the 20 LICENSE file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r530139 - in /geronimo/sandbox/j2g/src/main/resources: j2g-configure.bat j2g-configure.cmd j2g-configure.sh jdesc2g.bat jdesc2g.cmd jdesc2g.sh jres2g.bat jres2g.cmd jres2g.sh jsrc2g.ba

[Sachin Patel]

Oh nevermind, they were from the wrong tag.

-sachin


On Apr 18, 2007, at 6:22 PM, Jason Dillon wrote:

Which scripts did you copy them from?  The bits in server/trunk/ 
assemblies/geronimo-boilerplate-minimal/src/main/resources/bin all  
have the correct header.


--jason


On Apr 18, 2007, at 3:00 PM, Sachin Patel wrote:

ok thx, i copied them out of our scripts, so our scripts need  
updating too then.


-sachin


On Apr 18, 2007, at 3:52 PM, Jason Dillon wrote:

These headers don't look like the latest rev of the text we are  
required to use for releases, should be:



/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements.  See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership.  The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License.  You may obtain a copy of the License at
*
*  http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied.  See the License for the
* specific language governing permissions and limitations
* under the License.
*/


w/ the correct @REM/# muck for the scripts of course.

--jason


On Apr 18, 2007, at 12:43 PM, [EMAIL PROTECTED] wrote:


Author: sppatel
Date: Wed Apr 18 12:43:01 2007
New Revision: 530139

URL: http://svn.apache.org/viewvc?view=rev&rev=530139
Log:
unix scripts, update copyrights

Added:
geronimo/sandbox/j2g/src/main/resources/j2g-configure.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/j2g-configure.cmd
geronimo/sandbox/j2g/src/main/resources/j2g-configure.sh
(with props)

geronimo/sandbox/j2g/src/main/resources/jdesc2g.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/jdesc2g.cmd
geronimo/sandbox/j2g/src/main/resources/jdesc2g.sh   (with  
props)

geronimo/sandbox/j2g/src/main/resources/jres2g.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/jres2g.cmd
geronimo/sandbox/j2g/src/main/resources/jres2g.sh   (with  
props)

geronimo/sandbox/j2g/src/main/resources/jsrc2g.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/jsrc2g.cmd
geronimo/sandbox/j2g/src/main/resources/jsrc2g.sh   (with  
props)

Removed:
geronimo/sandbox/j2g/src/main/resources/j2g-configure.cmd
geronimo/sandbox/j2g/src/main/resources/jdesc2g.cmd
geronimo/sandbox/j2g/src/main/resources/jres2g.cmd
geronimo/sandbox/j2g/src/main/resources/jsrc2g.cmd

Copied: geronimo/sandbox/j2g/src/main/resources/j2g- 
configure.bat (from r530100, geronimo/sandbox/j2g/src/main/ 
resources/j2g-configure.cmd)
URL: http://svn.apache.org/viewvc/geronimo/sandbox/j2g/src/main/ 
resources/j2g-configure.bat?view=diff&rev=530139&p1=geronimo/ 
sandbox/j2g/src/main/resources/j2g- 
configure.cmd&r1=530100&p2=geronimo/sandbox/j2g/src/main/ 
resources/j2g-configure.bat&r2=530139
=== 
===
--- geronimo/sandbox/j2g/src/main/resources/j2g-configure.cmd  
(original)
+++ geronimo/sandbox/j2g/src/main/resources/j2g-configure.bat  
Wed Apr 18 12:43:01 2007

@@ -1,17 +1,20 @@
-/**
- *  Licensed to the Apache Software Foundation (ASF) under one  
or more
- *  contributor license agreements.  See the NOTICE file  
distributed with
- *  this work for additional information regarding copyright  
ownership.
- *  The ASF licenses this file to You under the Apache License,  
Version 2.0
- *  (the "License"); you may not use this file except in  
compliance with

- *  the License.  You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- *  Unless required by applicable law or agreed to in writing,  
software
- *  distributed under the License is distributed on an "AS IS"  
BASIS,
- *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either  
express or implied.
- *  See the License for the specific language governing  
permissions and

- *  limitations under the License.
- */
- java -cp configurator.jar org.apache.geronimo.j2g.Configurator  
%ECLIPSE_HOME%

\ No newline at end of file
[EMAIL PROTECTED]
[EMAIL PROTECTED]  Copyright 2005 The Apache Software Foundation
[EMAIL PROTECTED]
[EMAIL PROTECTED]   Licensed under the Apache License, Version 2.0 (the  
"License");
[EMAIL PROTECTED]   you may not use this file except in compliance with the  
License.

[EMAIL PROTECTED]   You may obtain a copy of the License at
[EMAIL PROTECTED]
[EMAIL PROTECTED]  http://www.apache.org/licenses/LICENSE-2.0
[EMAIL PROTECTED]
[EMAIL PROTECTED]   Unless required by applicabl

Re: svn commit: r530139 - in /geronimo/sandbox/j2g/src/main/resources: j2g-configure.bat j2g-configure.cmd j2g-configure.sh jdesc2g.bat jdesc2g.cmd jdesc2g.sh jres2g.bat jres2g.cmd jres2g.sh jsrc2g.ba

[Sachin Patel]

ok thx, i copied them out of our scripts, so our scripts need  
updating too then.


-sachin


On Apr 18, 2007, at 3:52 PM, Jason Dillon wrote:

These headers don't look like the latest rev of the text we are  
required to use for releases, should be:



/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements.  See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership.  The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License.  You may obtain a copy of the License at
*
*  http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied.  See the License for the
* specific language governing permissions and limitations
* under the License.
*/


w/ the correct @REM/# muck for the scripts of course.

--jason


On Apr 18, 2007, at 12:43 PM, [EMAIL PROTECTED] wrote:


Author: sppatel
Date: Wed Apr 18 12:43:01 2007
New Revision: 530139

URL: http://svn.apache.org/viewvc?view=rev&rev=530139
Log:
unix scripts, update copyrights

Added:
geronimo/sandbox/j2g/src/main/resources/j2g-configure.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/j2g-configure.cmd
geronimo/sandbox/j2g/src/main/resources/j2g-configure.sh
(with props)

geronimo/sandbox/j2g/src/main/resources/jdesc2g.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/jdesc2g.cmd

geronimo/sandbox/j2g/src/main/resources/jdesc2g.sh   (with props)
geronimo/sandbox/j2g/src/main/resources/jres2g.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/jres2g.cmd

geronimo/sandbox/j2g/src/main/resources/jres2g.sh   (with props)
geronimo/sandbox/j2g/src/main/resources/jsrc2g.bat
  - copied, changed from r530100, geronimo/sandbox/j2g/src/ 
main/resources/jsrc2g.cmd

geronimo/sandbox/j2g/src/main/resources/jsrc2g.sh   (with props)
Removed:
geronimo/sandbox/j2g/src/main/resources/j2g-configure.cmd
geronimo/sandbox/j2g/src/main/resources/jdesc2g.cmd
geronimo/sandbox/j2g/src/main/resources/jres2g.cmd
geronimo/sandbox/j2g/src/main/resources/jsrc2g.cmd

Copied: geronimo/sandbox/j2g/src/main/resources/j2g-configure.bat  
(from r530100, geronimo/sandbox/j2g/src/main/resources/j2g- 
configure.cmd)
URL: http://svn.apache.org/viewvc/geronimo/sandbox/j2g/src/main/ 
resources/j2g-configure.bat?view=diff&rev=530139&p1=geronimo/ 
sandbox/j2g/src/main/resources/j2g- 
configure.cmd&r1=530100&p2=geronimo/sandbox/j2g/src/main/resources/ 
j2g-configure.bat&r2=530139
= 
=
--- geronimo/sandbox/j2g/src/main/resources/j2g-configure.cmd  
(original)
+++ geronimo/sandbox/j2g/src/main/resources/j2g-configure.bat Wed  
Apr 18 12:43:01 2007

@@ -1,17 +1,20 @@
-/**
- *  Licensed to the Apache Software Foundation (ASF) under one or  
more
- *  contributor license agreements.  See the NOTICE file  
distributed with
- *  this work for additional information regarding copyright  
ownership.
- *  The ASF licenses this file to You under the Apache License,  
Version 2.0
- *  (the "License"); you may not use this file except in  
compliance with

- *  the License.  You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- *  Unless required by applicable law or agreed to in writing,  
software
- *  distributed under the License is distributed on an "AS IS"  
BASIS,
- *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express  
or implied.
- *  See the License for the specific language governing  
permissions and

- *  limitations under the License.
- */
- java -cp configurator.jar org.apache.geronimo.j2g.Configurator % 
ECLIPSE_HOME%

\ No newline at end of file
[EMAIL PROTECTED]
[EMAIL PROTECTED]  Copyright 2005 The Apache Software Foundation
[EMAIL PROTECTED]
[EMAIL PROTECTED]   Licensed under the Apache License, Version 2.0 (the  
"License");
[EMAIL PROTECTED]   you may not use this file except in compliance with the  
License.

[EMAIL PROTECTED]   You may obtain a copy of the License at
[EMAIL PROTECTED]
[EMAIL PROTECTED]  http://www.apache.org/licenses/LICENSE-2.0
[EMAIL PROTECTED]
[EMAIL PROTECTED]   Unless required by applicable law or agreed to in writing,  
software
[EMAIL PROTECTED]   distributed under the License is distributed on an "AS IS"  
BASIS,
[EMAIL PROTECTED]   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either  
express or implied.
[EMAIL PROTECTED]   See the License for the specific language governing  
permissions and

[EMAIL PROTECTED]   limitations under the License.
+
[EMAIL PROTECTED]  

Re: [VOTE] Release geronimo-annotation_1.0_spec-1.1 jar (1st vote)

[Sachin Patel]

+1

-sachin


On Apr 18, 2007, at 12:23 PM, Matt Hogstrom wrote:

Please review and vote on the binaries for geronimo- 
annotation_1.0_spec-1.1.  the binaries can be seen in:


http://people.apache.org/~hogstrom/spec-rc1

[ ] +1 Release these binaries
[ ] 0
[ ] -1  Do not release these binaries

This vote will conclude Saturday April 21 at 1300 Eastern

Re: [VOTE] Release geronimo-jpa_3.0_spec-1.1 jar (1st vote)

[Sachin Patel]

+1

-sachin


On Apr 18, 2007, at 12:22 PM, Matt Hogstrom wrote:

Please review and vote on the binaries for geronimo- 
jpa_3.0_spec-1.1.  the binaries can be seen in:


http://people.apache.org/~hogstrom/spec-rc1

[ ] +1 Release these binaries
[ ] 0
[ ] -1  Do not release these binaries

This vote will conclude Saturday April 21 at 1300 Eastern

Re: [VOTE] Release geronimo-stax-api_1.0_spec-1.0 jar (1st vote)

[Sachin Patel]

+1

-sachin


On Apr 18, 2007, at 12:22 PM, Matt Hogstrom wrote:

Please review and vote on the binaries for geronimo-stax- 
api_1.0_spec-1.0.  the binaries can be seen in:


http://people.apache.org/~hogstrom/spec-rc1

[ ] +1 Release these binaries
[ ] 0
[ ] -1  Do not release these binaries

This vote will conclude Saturday April 21 at 1300 Eastern

Re: [VOTE] Release geronimo-ws-metadata_2.0_spec-1.1 jar (1st vote)

[Sachin Patel]

+1

-sachin


On Apr 18, 2007, at 12:22 PM, Matt Hogstrom wrote:

Please review and vote on the binaries for geronimo-ws- 
metadata_2.0_spec-1.2.  the binaries can be seen in:


http://people.apache.org/~hogstrom/spec-rc1

[ ] +1 Release these binaries
[ ] 0
[ ] -1  Do not release these binaries

This vote will conclude Saturday April 21 at 1300 Eastern

Re: svn commit: r529386 - in /geronimo/devtools/eclipse-plugin/trunk: plugins/org.apache.geronimo.runtime.common/pom.xml pom.xml

[Sachin Patel]

i am using dependency management for most of the stuff.  However,  
keep in mind, devtools is a very unique case.  I sometime depend on  
multiple versions of a given module, so sometimes use of properties  
is required.


Prediciting your next response on why multiple versions are needed...

Every release of the G plugins provide cumalative support for  
previous version of Geronimo.  So while Geronimo moves on with  
development, forgetting prior releases, from a tooling perspective I  
cannot do that.  So while trunk it geronimo implies "2.0 and 2.0"  
only.  Trunk in devtools implies "1.0, 1.1.x, and 2.0 support on the  
latest version of WTP (installable as individual features).


-sachin


On Apr 16, 2007, at 4:36 PM, Jason Dillon wrote:

You really should use the dependencyManagement feature of maven 2  
to manage versions, please don't use properties like this.


--jason


On Apr 16, 2007, at 1:30 PM, [EMAIL PROTECTED] wrote:


Author: sppatel
Date: Mon Apr 16 13:30:21 2007
New Revision: 529386

URL: http://svn.apache.org/viewvc?view=rev&rev=529386
Log:
allow eclipse install location to be passed

Modified:
geronimo/devtools/eclipse-plugin/trunk/plugins/ 
org.apache.geronimo.runtime.common/pom.xml

geronimo/devtools/eclipse-plugin/trunk/pom.xml

Modified: geronimo/devtools/eclipse-plugin/trunk/plugins/ 
org.apache.geronimo.runtime.common/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/ 
trunk/plugins/org.apache.geronimo.runtime.common/pom.xml? 
view=diff&rev=529386&r1=529385&r2=529386
= 
=
--- geronimo/devtools/eclipse-plugin/trunk/plugins/ 
org.apache.geronimo.runtime.common/pom.xml (original)
+++ geronimo/devtools/eclipse-plugin/trunk/plugins/ 
org.apache.geronimo.runtime.common/pom.xml Mon Apr 16 13:30:21 2007

@@ -29,6 +29,7 @@
 
 2.0.0
 1.0.4
+1.0
 
 
 

Modified: geronimo/devtools/eclipse-plugin/trunk/pom.xml
URL: http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/ 
trunk/pom.xml?view=diff&rev=529386&r1=529385&r2=529386
= 
=

--- geronimo/devtools/eclipse-plugin/trunk/pom.xml (original)
+++ geronimo/devtools/eclipse-plugin/trunk/pom.xml Mon Apr 16  
13:30:21 2007

@@ -73,7 +73,7 @@
 
 
 
-
+${settings.localRepository}/eclipseeclipseInstall>
 2.0.0org.apache.geronimo.feature_version>
 2.0.0org.apache.geronimo.v10.feature_version>
 2.0.0org.apache.geronimo.v11.feature_version>

@@ -81,8 +81,6 @@
 2.0.0org.apache.geronimo.v20.feature_version>
  
2.0.0< 
/org.apache.geronimo.installableruntime.tomcat.feature_version>
  
2.0.0org.apache.geronimo.installableruntime.jetty.feature_version>

-
-1.0
 
 
 
@@ -120,7 +118,7 @@
 
 
 ../../target/ 
dependency-maven-plugin-markers
-$ 
{settings.localRepository}/eclipse
+${eclipseInstall} 


 
 
 org.eclipse.gefgroupId>

@@ -332,4 +330,4 @@
 features
 assembly
 
-
+
\ No newline at end of file

Re: svn commit: r528976 - in /geronimo/devtools/maven-plugins/trunk: maven-eclipse-plugin/ maven-geronimodevtools-plugin/

[Sachin Patel]

Ok, I can rename it again. :) How about maven-eclipsepde-plugin?

The pde-maven-plugin basically wraps the Eclipse-PDE-Builder.  So  
using it would be essentially unmavenizing it, and would require ant  
scripts to configure the eclipse pde builder, and then eclipse itself  
would be building the plugins and features, not maven.  Using it  
would be a regression in my mind and a huge step back from even what  
Maven currently has and is working to provide.


-sachin


On Apr 15, 2007, at 7:15 PM, Jason Dillon wrote:


On Apr 15, 2007, at 3:20 PM, Sachin Patel wrote:
These maven plugins are needed into order to build "eclipse- 
plugins".  I extracted them out for use with J2G.  Maven's eclipse  
plugin has made significant improvements since I initially created  
these plugins, but they still don't address many issues that are  
needed to build "eclipse plugins" or I don't like the way maven  
provides a solution to some of the issues that my plugins handle  
better.


Ya, I know the eclipse plugin has some faults.  Though it would be  
nice to see us not need this custom plugin and get the changes  
needed merged into the official plugin.  By the way, have you  
looked at the pde-maven-plugin ( http://mojo.codehaus.org/pde-maven- 
plugin/ )?




See...

http://www.eclipse.org/articles/article.php?file=Article-Eclipse- 
and-Maven2/index.html.


Also, there is no conflict with maven's eclipse plugin and this  
one.  So eclipse:goal still fine.


That is not true... or I would not have mentioned it... its not  
like I just started using Maven 2 yesterday :-P


Your plugin will also get bound with the prefix "eclipse" due to  
the artifact name.  And IMO that is bad practice to provide another  
plugin that uses the same prefix as the core plugins (like the  
maven-eclipse-plugin).


Yes, it might work asis, but it is a bad practice.

--jason

Re: svn commit: r528976 - in /geronimo/devtools/maven-plugins/trunk: maven-eclipse-plugin/ maven-geronimodevtools-plugin/

[Sachin Patel]

Here is some more info on maven & the eclipse team working to better  
support eclipse plugin builds.


http://docs.codehaus.org/display/MAVEN/Barriers+to+Building+Eclipse 
+with+Maven


-sachin


On Apr 15, 2007, at 6:20 PM, Sachin Patel wrote:

These maven plugins are needed into order to build "eclipse- 
plugins".  I extracted them out for use with J2G.  Maven's eclipse  
plugin has made significant improvements since I initially created  
these plugins, but they still don't address many issues that are  
needed to build "eclipse plugins" or I don't like the way maven  
provides a solution to some of the issues that my plugins handle  
better.


See...

http://www.eclipse.org/articles/article.php?file=Article-Eclipse- 
and-Maven2/index.html.


Also, there is no conflict with maven's eclipse plugin and this  
one.  So eclipse:goal still fine.


-sachin


On Apr 15, 2007, at 4:39 PM, Jason Dillon wrote:

Yikes dude... having another maven-eclipse-plugin, or (eclipse- 
maven-plugin for that matter) is going to cause problems when one  
executes `mvn eclipse:` in a project that has these configured.


And actually... why is this needed?

--jason


On Apr 15, 2007, at 6:51 AM, [EMAIL PROTECTED] wrote:


Author: sppatel
Date: Sun Apr 15 06:51:32 2007
New Revision: 528976

URL: http://svn.apache.org/viewvc?view=rev&rev=528976
Log:
rename plugin

Added:
geronimo/devtools/maven-plugins/trunk/maven-eclipse-plugin/
  - copied from r528975, geronimo/devtools/maven-plugins/ 
trunk/maven-geronimodevtools-plugin/

Removed:
geronimo/devtools/maven-plugins/trunk/maven-geronimodevtools- 
plugin/

Re: how do i get maven generated doc live?

[Sachin Patel]

-sachin


On Apr 15, 2007, at 4:34 PM, Jason Dillon wrote:


On Apr 15, 2007, at 8:25 AM, Sachin Patel wrote:
I've run site:site site:deploy on devtools/eclipse-plugin which  
successfully built and published to:


people.apache.org/www/geronimo.apache.org/maven/devtools/eclipse- 
plugin


What, if anything, do I need to do next to make it live on

http://geronimo.apache.org/maven/devtools/eclipse-plugin?


You just have to wait for the site sync to happen, so sit back and  
do nothing and check again in an hour or so.


 * * *

Please update the permissions, these files should all be g+w, but  
they are not:


drwxr-xr-x   4 sppatel   geronimo   512 Apr 15 08:20 devtools

To fix run:

chmod -R g+w /www/geronimo.apache.org/maven/devtools


Fixed.



It would also be really nice if you would use the same site skin as  
the other Maven-generated site.  If you would have just used the  
Genesis project-config pom as your parent then you would have  
picked this up automatically.  I created project-config for a  
specific reason... to allow common configuration to be shared.  But  
that only works if you actually use it.


I think genesis may be too much for me too pull in, as I'm not sure  
what it all does.  So I'll just pick the pieces I need and if it ends  
up that it need alot of what genesis provides, then I can make use it  
as the parent.  But for now, I don't think that is the case.




Are there actually any reports generated for these modules?  I did  
a quick check and I just see the project-info reports.  And looks  
like none of these modules have descriptions.  What is the point of  
the Maven-generated site if you don't update the pom to describe  
the module and enable useful reports?


No not yet.  I was playing around with the site functionality for the  
first time, so I just trying to get something basic setup.  Sorry.




--jason

Re: svn commit: r528976 - in /geronimo/devtools/maven-plugins/trunk: maven-eclipse-plugin/ maven-geronimodevtools-plugin/

[Sachin Patel]

These maven plugins are needed into order to build "eclipse- 
plugins".  I extracted them out for use with J2G.  Maven's eclipse  
plugin has made significant improvements since I initially created  
these plugins, but they still don't address many issues that are  
needed to build "eclipse plugins" or I don't like the way maven  
provides a solution to some of the issues that my plugins handle better.


See...

http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and- 
Maven2/index.html.


Also, there is no conflict with maven's eclipse plugin and this one.   
So eclipse:goal still fine.


-sachin


On Apr 15, 2007, at 4:39 PM, Jason Dillon wrote:

Yikes dude... having another maven-eclipse-plugin, or (eclipse- 
maven-plugin for that matter) is going to cause problems when one  
executes `mvn eclipse:` in a project that has these configured.


And actually... why is this needed?

--jason


On Apr 15, 2007, at 6:51 AM, [EMAIL PROTECTED] wrote:


Author: sppatel
Date: Sun Apr 15 06:51:32 2007
New Revision: 528976

URL: http://svn.apache.org/viewvc?view=rev&rev=528976
Log:
rename plugin

Added:
geronimo/devtools/maven-plugins/trunk/maven-eclipse-plugin/
  - copied from r528975, geronimo/devtools/maven-plugins/trunk/ 
maven-geronimodevtools-plugin/

Removed:
geronimo/devtools/maven-plugins/trunk/maven-geronimodevtools- 
plugin/

how do i get maven generated doc live?

[Sachin Patel]

I've run site:site site:deploy on devtools/eclipse-plugin which  
successfully built and published to:


people.apache.org/www/geronimo.apache.org/maven/devtools/eclipse-plugin

What, if anything, do I need to do next to make it live on

http://geronimo.apache.org/maven/devtools/eclipse-plugin?

-sachin

axis2 test failure

[Sachin Patel]

---
T E S T S
---
Running org.apache.geronimo.axis2.Axis2HandlerResolverTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.859  
sec

Running org.apache.geronimo.axis2.Axis2WebServiceContainerTest
java.lang.ExceptionInInitializerError
at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:555)
at org.apache.axis2.deployment.DescriptionBuilder.buildOM 
(DescriptionBuilder.java:94)
at  
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig 
(AxisConfigBuilder.java:76)
at  
org.apache.axis2.context.ConfigurationContextFactory.createDefaultConfig 
urationContext(ConfigurationContextFactory.java:270)
at org.apache.geronimo.axis2.Axis2WebServiceContainer. 
(Axis2WebServiceContainer.java:109)
at  
org.apache.geronimo.axis2.pojo.POJOWebServiceContainer. 
(POJOWebServiceContainer.java:61)
at  
org.apache.geronimo.axis2.Axis2WebServiceContainerTest.invokeWithWSDL 
(Axis2WebServiceContainerTest.java:144)
at  
org.apache.geronimo.axis2.Axis2WebServiceContainerTest.testInvokeWithWSD 
L(Axis2WebServiceContainerTest.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute 
(JUnitTestSet.java:210)
at  
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSe 
t(AbstractDirectoryTestSuite.java:135)
at  
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute 
(AbstractDirectoryTestSuite.java:122)

at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at  
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess 
(SurefireBooter.java:225)
at org.apache.maven.surefire.booter.SurefireBooter.main 
(SurefireBooter.java:747)
Caused by: java.lang.IllegalStateException: No valid ObjectCreator  
found.
at org.apache.axiom.om.util.StAXUtils$Pool. 
(StAXUtils.java:42)
at org.apache.axiom.om.util.StAXUtils. 
(StAXUtils.java:66)

... 34 more
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.314  
sec <<< FAILURE!


Results :
Tests run: 8, Failures: 0, Errors: 2, Skipped: 0

[INFO]  


[ERROR] BUILD FAILURE
[INFO]  


[INFO] There are test failures.
[INFO]  




-sachin

Re: [BUILD] TRUNK: Failed for Revision: 527493

[Sachin Patel]

Yep i'm working on this.. fixed soon.

-sachin


On Apr 11, 2007, at 11:24 AM, Prasad Kashyap wrote:


In Revision 527514, Jarek fixed this above error. It continues further
and fails at configs/jee-specs

[INFO]  
-- 
--

[ERROR] BUILD ERROR
[INFO]  
-- 
--

[INFO] Failed to resolve artifact.

Missing:
--
1) javax.xml:jsr173:jar:1.0

 Try downloading the file manually from:
 http://ftpna2.bea.com/pub/downloads/jsr173.jar

 Then, install it using the command:
 mvn install:install-file -DgroupId=javax.xml - 
DartifactId=jsr173 \

 -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file

 Path to dependency:
   1) org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT
   2) com.sun.xml.bind:jaxb-impl:jar:2.0
   3) javax.xml:jaxb-api:jar:2.0
   4) javax.xml:jsr173:jar:1.0

--
1 required artifact is missing.

for artifact:
 org.apache.geronimo.configs:jee-specs:car:2.0-SNAPSHOT


Should this dependency in configs/jee-specs/pom.xml be removed too ?



com.sun.xml.bind
jaxb-impl


Cheers
Prasad

On 11 Apr 2007 14:24:51 -, [EMAIL PROTECTED]  
<[EMAIL PROTECTED]> wrote:

Building with Maven version: 2.0.5
Revision: 527493 built with tests skipped
See the full build-1000.log file at http://people.apache.org/ 
~prasad/binaries/20070411/build-1000.log


2911K downloaded
Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/ 
apache/ws/commons/schema/XmlSchema/1.2/XmlSchema-1.2.jar
[WARNING] Unable to get resource  
'org.apache.ws.commons.schema:XmlSchema:jar:1.2' from repository  
tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository)
Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/apache/ws/commons/schema/XmlSchema/1.2/ 
XmlSchema-1.2.jar
[WARNING] Unable to get resource  
'org.apache.ws.commons.schema:XmlSchema:jar:1.2' from repository  
apache-incubator (http://people.apache.org/repo/m2-incubating- 
repository/)
Downloading: http://repo1.maven.org/maven2/org/apache/ws/commons/ 
schema/XmlSchema/1.2/XmlSchema-1.2.jar

125K downloaded
Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/ 
mortbay/jetty/servlet-api-2.5/6.1.2rc0/servlet-api-2.5-6.1.2rc0.jar
[WARNING] Unable to get resource 'org.mortbay.jetty:servlet- 
api-2.5:jar:6.1.2rc0' from repository tomcat-m2-repo (http:// 
tomcat.apache.org/dev/dist/m2-repository)
Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/mortbay/jetty/servlet-api-2.5/6.1.2rc0/servlet- 
api-2.5-6.1.2rc0.jar
[WARNING] Unable to get resource 'org.mortbay.jetty:servlet- 
api-2.5:jar:6.1.2rc0' from repository apache-incubator (http:// 
people.apache.org/repo/m2-incubating-repository/)
Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/ 
servlet-api-2.5/6.1.2rc0/servlet-api-2.5-6.1.2rc0.jar

128K downloaded
Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/ 
mortbay/jetty/jetty/6.1.2rc0/jetty-6.1.2rc0.jar
[WARNING] Unable to get resource 'org.mortbay.jetty:jetty:jar: 
6.1.2rc0' from repository tomcat-m2-repo (http://tomcat.apache.org/ 
dev/dist/m2-repository)
Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/mortbay/jetty/jetty/6.1.2rc0/jetty-6.1.2rc0.jar
[WARNING] Unable to get resource 'org.mortbay.jetty:jetty:jar: 
6.1.2rc0' from repository apache-incubator (http:// 
people.apache.org/repo/m2-incubating-repository/)
Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/jetty/ 
6.1.2rc0/jetty-6.1.2rc0.jar

450K downloaded
Downloading: http://people.apache.org/repo/m2-snapshot-repository/ 
org/apache/cxf/cxf-rt-frontend-jaxws/2.0-incubator-RC-SNAPSHOT/cxf- 
rt-frontend-jaxws-2.0-incubator-RC-20070411.013316-22.jar

191K downloaded
Downloading: http://people.apache.org/repo/m2-snapshot-repository/ 
org/apache/cxf/cxf-rt-databinding-jaxb/2.0-incubator-RC-SNAPSHOT/ 
cxf-rt-databinding-jaxb-2.0-incubator-RC-20070411.013316-22.jar

45K downloaded
Downloading: http://people.apache.org/repo/m2-snapshot-repository/ 
org/apache/cxf/cxf-rt-bindings-soap/2.0-incubator-RC-SNAPSHOT/cxf- 
rt-bindings-soap-2.0-incubator-RC-20070411.013316-22.jar

76K downloaded
Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/ 
springframework/spring-core/2.0.3/spring-core-2.0.3.jar
[WARNING] Unable to get resource 'org.springframework:spring- 
core:jar:2.0.3' from repository tomcat-m2-repo (http:// 
tomcat.apache.org/dev/dist/m2-repository)
Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/springframework/spring-core/2.0.3/spring- 
core-2.0.3.jar
[WARNING] Unable to get resource 'org.springframework:spring- 
core:jar:2.0.3' from repository apache-incubator (http:// 
people.apache.org/repo/m2-incubating-repository/)
Downloading: http://repo1.maven.org/maven2/org/springframework/ 
spring-core/2.0.3/spring-core-2.0.3.jar

174K downloaded
Downloading: http:

Re: Build Failed in Openejb builder

[Sachin Patel]

Actually, jaxb should to be downgraded to 2.0.0.

-sachin


On Apr 11, 2007, at 6:00 AM, Kevan Miller wrote:



On Apr 11, 2007, at 5:45 AM, Lasantha Ranaweera wrote:


Kevan,

Thanks for the reply.

Yes now it is over and CXF gives following.

Missing:
--
1) com.sun.xml.bind:jaxb-impl:jar:2.0.5

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=com.sun.xml.bind - 
DartifactId=jaxb-impl \

-Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file

Path to dependency:
1) org.apache.geronimo.modules:geronimo-cxf:jar:2.0-SNAPSHOT
2) org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.0-incubator-RC-SNAPSHOT
3) org.apache.cxf:cxf-tools-common:jar:2.0-incubator-RC-SNAPSHOT
4) com.sun.xml.bind:jaxb-impl:jar:2.0.5


Lasantha,
The following should fix your immediate problem.

edit geronimo/server/trunk/pom.xml
search for jaxb-impl
change the  from 2.0.3 to 2.0.5.

I'm guessing that this is a pretty safe upgrade. However, I'll let  
someone more familiar with our jaxb usage make the change...


--kevan

build failure

[Sachin Patel]

[ERROR] BUILD FAILURE
[INFO]  


[INFO] Compilation failure
/Users/sppatel/svn/server/trunk/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/EjbDeployment.java:[211,49]  
createProxy(org.apache.openejb.ProxyInfo) has protected access in  
org.apache.openejb.core.ivm.EjbHomeProxyHandler




/Users/sppatel/svn/server/trunk/modules/geronimo-openejb/src/main/ 
java/org/apache/geronimo/openejb/EjbDeployment.java:[211,49]  
createProxy(org.apache.openejb.ProxyInfo) has protected access in  
org.apache.openejb.core.ivm.EjbHomeProxyHandler



-sachin

Re: [DISCUSS] 2.0-M4 Binaries available (rc1) - rc1 is dead

[Sachin Patel]

So moving forward is reproducibility of our milestone builds always  
going to be an issue?  I think this is pretty ridiculous that this is  
such a painful process and I understand Matt's frustration.


Does any one know if Maven is using us as a case-study and working  
toward addressing some of our major concerns? If not, do we look  
toward another build solution in the future?


-sachin


On Apr 4, 2007, at 11:33 AM, Matt Hogstrom wrote:


Here's my 0.02 c.

The process is owrking well as (I think it was Rakesh) that  
identified something odd about the binaries.  We should not have  
both artifacts (2.0-M4 and 2.0-M4-SNAPSHOT) in the binaries.


As release manager I am not comfortable releasing these and I'm  
concerned about where they got picked up and will investigate this.


I will work today to spin up a corrected set of binaries that  
addresses the issues we've been discussing (buildability, etc.)


I have to say that every release is a learning experience.  So, for  
my part doing this once a month has been useful as it flushes out a  
new set of issues.  Geronimo is so dependent on external projects  
that we are in a unique (and difficult) position from a release  
standpoint as our dependent projects do not release in a  
coordinated fashion.


I have a check list of how to build and am augmenting it with a  
list of things to look for...something new every time :)

Re: [Fwd: Is the GERONIMODEVTOOLS JIRA still under RTC?]

[Sachin Patel]

I see close as an action.  Perhaps your permissions are not correct.   
But no, DEVTOOLS is not  under RTC and the workflow should have been  
removed from this project as well.


-sachin


On Apr 2, 2007, at 9:23 PM, Donald Woods wrote:


Resending as this never showed up on the list

 Original Message 
Subject: Is the GERONIMODEVTOOLS JIRA still under RTC?
Date: Mon, 02 Apr 2007 20:11:13 -0400
From: Donald Woods <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: gdev 

I'm trying to close GERONIMODEVTOOLS-139, which is a duplicate of 132
that I just fixed and closed, but 139 only gives me workflow  
actions of-

Begin RTC Review
Start Progress
For 132, I had the Resolve option and could close it as fixed.

What's up?

-Donald

Re: [ANNOUNCE] Dain Sundstrom is the newest member of the Geronimo PMC

[Sachin Patel]

congrats!

-sachin


On Mar 30, 2007, at 2:26 PM, Matt Hogstrom wrote:

The Apache Geronimo PMC is pleased to announce that Dain Sundstrom  
has accepted an invitation to join the PMC.


Nuf 'said.

Welcome :-0

[jira] Closed: (GERONIMODEVTOOLS-138) Shipped plugin too large

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-138.
-

Resolution: Invalid

> Shipped plugin too large
> 
>
> Key: GERONIMODEVTOOLS-138
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-138
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Reporter: Ted Kirby
> Attachments: Rev518130-Rev515752-jars.txt
>
>
> The 2.0.0 plugin is now 58 MB, but 1.2.1 plugin is only 12 MB.
> It seems some geronimo and eclipse jars are packaged into the plugin, greatly 
> increasing its size.
> Can these be removed to make the 2.0.0 plugin smaller?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-138) Shipped plugin too large

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484951
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-138:
---

Wait, how are you seeing 58 megs? Its only 13 megs. Are you sure you are 
looking at the eclipse plugin and not Geronimo itself?

> Shipped plugin too large
> 
>
> Key: GERONIMODEVTOOLS-138
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-138
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Reporter: Ted Kirby
> Attachments: Rev518130-Rev515752-jars.txt
>
>
> The 2.0.0 plugin is now 58 MB, but 1.2.1 plugin is only 12 MB.
> It seems some geronimo and eclipse jars are packaged into the plugin, greatly 
> increasing its size.
> Can these be removed to make the 2.0.0 plugin smaller?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-138) Shipped plugin too large

[Sachin Patel (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484948
 ] 

Sachin Patel commented on GERONIMODEVTOOLS-138:
---

These are only daily drivers.  The primary install mechanism on the final 
version will be through the update manager and they will be broken down into 
multiple features.  So if you only wanted 2.0 support you only download the 
plugins that provide it.  I can look into creating multiple "deployable.zip" 
distributions for each version of G.

> Shipped plugin too large
> 
>
> Key: GERONIMODEVTOOLS-138
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-138
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Reporter: Ted Kirby
> Attachments: Rev518130-Rev515752-jars.txt
>
>
> The 2.0.0 plugin is now 58 MB, but 1.2.1 plugin is only 12 MB.
> It seems some geronimo and eclipse jars are packaged into the plugin, greatly 
> increasing its size.
> Can these be removed to make the 2.0.0 plugin smaller?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: mvn clean doesn't work?

[Sachin Patel]

thx that was it, i cleaned up the plugins directory in the repo and  
it worked.  weird.


-sachin


On Mar 27, 2007, at 4:01 PM, Jason Dillon wrote:


It appears to work fine for me in server/trunk.

Most problems I've seen related to clean are when the version of  
the plugin was not specified.  For server/trunk this is specified  
in genesis/config/project-config.


You may also have corrupt muck in your local repo.

--jason


On Mar 27, 2007, at 12:56 PM, Sachin Patel wrote:

Anyone, (happened after i cleaned my m2 repo).  I tried devtools,  
openejb, geronimo.


-sachin


On Mar 27, 2007, at 3:03 PM, Jason Dillon wrote:


Er... for which project?

--jason


On Mar 27, 2007, at 11:57 AM, Sachin Patel wrote:

Is it me or does mvn clean no longer work?... I get the  
following error..


[INFO]  
--- 
-

[ERROR] BUILD ERROR
[INFO]  
--- 
-
[INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin'  
does not exist or no valid version could be found



-sachin

Re: mvn clean doesn't work?

[Sachin Patel]

Anyone, (happened after i cleaned my m2 repo).  I tried devtools,  
openejb, geronimo.


-sachin


On Mar 27, 2007, at 3:03 PM, Jason Dillon wrote:


Er... for which project?

--jason


On Mar 27, 2007, at 11:57 AM, Sachin Patel wrote:

Is it me or does mvn clean no longer work?... I get the following  
error..


[INFO]  
- 
---

[ERROR] BUILD ERROR
[INFO]  
- 
---
[INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin'  
does not exist or no valid version could be found



-sachin

mvn clean doesn't work?

[Sachin Patel]

Is it me or does mvn clean no longer work?... I get the following  
error..


[INFO]  


[ERROR] BUILD ERROR
[INFO]  

[INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin' does  
not exist or no valid version could be found



-sachin

Re: [ANNOUNCE] Please welcome Rakesh Midha as a new Geronimo committer

[Sachin Patel]

Congratulations!

-sachin


On Mar 27, 2007, at 2:30 PM, Kevan Miller wrote:


All,

The Geronimo PMC is pleased to announce that Rakesh Midha has  
recently accepted our invitation to become an Apache Geronimo  
committer. Rakesh has contributed a number of significant  
enhancements to our Admin Console and deployment code.


We're looking forward to Rakesh joining our project.

Congratulations and welcome to Rakesh!

--kevan

Re: [ANNOUNCE] Please welcome Donald Woods as a new Geronimo committer

[Sachin Patel]

Congratulations!

-sachin


On Mar 27, 2007, at 2:25 PM, Kevan Miller wrote:


All,

The Geronimo PMC is pleased to announce that Donald Woods has  
recently accepted our invitation to become an Apache Geronimo  
committer. Donald has been a long-term contributor to the Geronimo  
project and has provided valuable fixes and enhancements in a  
number of areas.


We're looking forward to Donald joining our project.

Congratulations and welcome to Donald!

--kevan

Re: [BRANCH NOTICE] 0900 ET on Wednesday March 29 for 2.0-M4

[Sachin Patel]

I'll be glad to help, though I will be out of town and unavailable  
fri-sun.


-sachin


On Mar 27, 2007, at 2:15 AM, Matt Hogstrom wrote:

I had previously posted a note that in looking at the Subject it  
was not clear the intent.  So...based on where we are at I'm going  
to suggest a 24-hour branch notice that will allow Milestone 4 to  
be packaged up be made available a few days later.


If there are outstanding issues please post back to this thread.   
Unless there are any objections I'll proceed on the proposed branch  
timeframe.


Anyone interested in co-piloting ?

Re: org.apache.j2g

[Sachin Patel]

True, but this thing isn't even mavenized yet.  So publishing is not  
a concern for me right now.  But I will mark this as a todo.


-sachin


On Mar 26, 2007, at 4:19 PM, Jason Dillon wrote:

I'm fine to wait to change this a little longer... but as soon as  
we have to start producing artifacts, publishing to repos or making  
assemblies then this should be fixed.


But is it really that muck work to do a global search and replace  
"org.apache.j2g" -> "org.apache.geronimo.j2g" ?  I do this all the  
time with jEdit... its quite simple and quick.


--jason


On Mar 26, 2007, at 1:12 PM, Sachin Patel wrote:

Yeah we should insert ".geronimo" before j2g, but I just got done  
refactoring alot of stuff and don't want to spend the time redoing  
it all overagain. Its not just the packages that would have to get  
changed again, but bundle id's, manifest references, extension  
points, etc...


Since Its currently in sandbox, we can just make it a requirement  
before we move it out of sandbox.


-sachin


On Mar 26, 2007, at 4:02 PM, Jason Dillon wrote:


I asked about this before, but got no answer.

Why is the code for "geronimo/sandbox/j2g" using "org.apache.j2g"  
as a package name?  This seems *very* inconsistent wrt other  
codelines which are hosted by the geronimo svn.


Why?

--jason

Re: org.apache.j2g

[Sachin Patel]

Yeah we should insert ".geronimo" before j2g, but I just got done  
refactoring alot of stuff and don't want to spend the time redoing it  
all overagain. Its not just the packages that would have to get  
changed again, but bundle id's, manifest references, extension  
points, etc...


Since Its currently in sandbox, we can just make it a requirement  
before we move it out of sandbox.


-sachin


On Mar 26, 2007, at 4:02 PM, Jason Dillon wrote:


I asked about this before, but got no answer.

Why is the code for "geronimo/sandbox/j2g" using "org.apache.j2g"  
as a package name?  This seems *very* inconsistent wrt other  
codelines which are hosted by the geronimo svn.


Why?

--jason

Re: [BUILD] TRUNK: Failed for Revision: 522459

[Sachin Patel]

why do we need jtidy, lets get rid of it.

-sachin


On Mar 26, 2007, at 9:36 AM, Prasad Kashyap wrote:


Once in a bluemoon, we get this error downloading jtidy.

The other known unknown error is getting activation-spec

Cheers
Prasad

On 3/26/07, Kanchana Welagedara <[EMAIL PROTECTED]> wrote:

I successfully built this on Linux just now!
Regards
Kanchana

On Mon, 2007-03-26 at 09:23 +, [EMAIL PROTECTED] wrote:
> Building with Maven version: 2.0.5
> Revision: 522459 built with tests included
> See the full build-0500.log file at http://people.apache.org/ 
~prasad/binaries/20070326/build-0500.log

>
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
artifact-manager:jar:2.0.4' from repository tomcat-m2-repo (http:// 
tomcat.apache.org/dev/dist/m2-repository/)
> Downloading: http://ws.zones.apache.org/repository2//org/ 
apaconhe/maven/maven-artifact-manager/2.0.4/maven-artifact- 
manager-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
artifact-manager:jar:2.0.4' from repository axis2-m2-repo (http:// 
ws.zones.apache.org/repository2/)
> Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/apache/maven/maven-artifact-manager/2.0.4/maven- 
artifact-manager-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
artifact-manager:jar:2.0.4' from repository apache-incubator  
(http://people.apache.org/repo/m2-incubating-repository/)
> Downloading: http://repository.codehaus.org/org/apache/maven/ 
maven-artifact-manager/2.0.4/maven-artifact-manager-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
artifact-manager:jar:2.0.4' from repository codehaus (http:// 
repository.codehaus.org)
> Downloading: http://repo1.maven.org/maven2/org/apache/maven/ 
maven-artifact-manager/2.0.4/maven-artifact-manager-2.0.4.jar

> 47K downloaded
> Downloading: http://people.apache.org/repo/m2-snapshot- 
repository/org/apache/maven/surefire/surefire-api/2.1-SNAPSHOT/ 
surefire-api-2.1-20070108.094711-10.jar

> 48K downloaded
> Downloading: http://tomcat.apache.org/dev/dist/m2-repository// 
org/apache/maven/maven-project/2.0.4/maven-project-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
project:jar:2.0.4' from repository tomcat-m2-repo (http:// 
tomcat.apache.org/dev/dist/m2-repository/)
> Downloading: http://ws.zones.apache.org/repository2//org/apache/ 
maven/maven-project/2.0.4/maven-project-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
project:jar:2.0.4' from repository axis2-m2-repo (http:// 
ws.zones.apache.org/repository2/)
> Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/apache/maven/maven-project/2.0.4/maven- 
project-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
project:jar:2.0.4' from repository apache-incubator (http:// 
people.apache.org/repo/m2-incubating-repository/)
> Downloading: http://repository.codehaus.org/org/apache/maven/ 
maven-project/2.0.4/maven-project-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
project:jar:2.0.4' from repository codehaus (http:// 
repository.codehaus.org)
> Downloading: http://repo1.maven.org/maven2/org/apache/maven/ 
maven-project/2.0.4/maven-project-2.0.4.jar

> 106K downloaded
> Downloading: http://tomcat.apache.org/dev/dist/m2-repository// 
org/apache/maven/maven-repository-metadata/2.0.4/maven-repository- 
metadata-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
repository-metadata:jar:2.0.4' from repository tomcat-m2-repo  
(http://tomcat.apache.org/dev/dist/m2-repository/)
> Downloading: http://ws.zones.apache.org/repository2//org/apache/ 
maven/maven-repository-metadata/2.0.4/maven-repository- 
metadata-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
repository-metadata:jar:2.0.4' from repository axis2-m2-repo  
(http://ws.zones.apache.org/repository2/)
> Downloading: http://people.apache.org/repo/m2-incubating- 
repository//org/apache/maven/maven-repository-metadata/2.0.4/maven- 
repository-metadata-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
repository-metadata:jar:2.0.4' from repository apache-incubator  
(http://people.apache.org/repo/m2-incubating-repository/)
> Downloading: http://repository.codehaus.org/org/apache/maven/ 
maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.jar
> [WARNING] Unable to get resource 'org.apache.maven:maven- 
repository-metadata:jar:2.0.4' from repository codehaus (http:// 
repository.codehaus.org)
> Downloading: http://repo1.maven.org/maven2/org/apache/maven/ 
maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.jar

> 19K downloaded
> [INFO] [compiler:compile]
> [INFO] Compiling 27 source files to /home/prasad/geronimo/trunk/ 
maven-plugins/geronimo-maven-plugin/target/classes

> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile

Re: [ANNOUNCE] Welcome Prasad Kashyap as the newest member of the Geronimo PMC

[Sachin Patel]

congratulations!

-sachin


On Mar 22, 2007, at 10:22 AM, Hernan Cunico wrote:


Hi All,
Please welcome Prasad Kashyap as the newest member of the Geronimo  
PMC. We're very happy to have him joining us to help with the  
oversight of the Geronimo project.


Way to go Prasad !!!

The Apache Geronimo PMC

Cheers!
Hernan

[jira] Closed: (GERONIMODEVTOOLS-137) Deployment plan editor does not display

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMODEVTOOLS-137.
-

Resolution: Invalid

The daily drivers require Eclipse 3.3 and WTP 2.0.  Please re-open if you still 
see the issue after upgrading.

> Deployment plan editor does not display
> ---
>
> Key: GERONIMODEVTOOLS-137
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-137
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
> Environment: Eclipse 3.2.2 with JDK 1.6.0 or JDK 1.5.0_11.running 
> Windows XP SP2.
> Plugin is the March 14th 2007 version.
>Reporter: Ivan Biddles
>
> I am running the 14-March daily build of the Geronimo Eclipse plug-in.
> I am unable to open the Geronimo Deployment Plan Editor.
> I have included the messages I get from the Eclipse startup as they may be 
> relevant.
> This happens whether I run Eclipse 3.2.2 with JDK 1.6.0 or with JDK 1.5.0_11.
> I am running Windows XP SP2.
> =
> JDK 1.6.0
> =
> !SESSION 2007-03-21 10:42:27.562 
> ---
> eclipse.buildId=M20070212-1330
> java.version=1.6.0
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Command-line arguments:  -os win32 -ws win32 -arch x86 -clean -debug
> !ENTRY org.eclipse.emf.ecore 2 0 2007-03-21 10:42:38.359
> !MESSAGE Both 'org.apache.geronimo.deployment.model' and 
> 'org.apache.geronimo.v11.deployment.model' register an extension parser for 
> 'deployment'
> !ENTRY org.eclipse.emf.ecore 2 0 2007-03-21 10:42:38.359
> !MESSAGE Both 'org.apache.geronimo.deployment.model' and 
> 'org.apache.geronimo.v11.deployment.model' register an extension parser for 
> 'naming'
> !ENTRY org.eclipse.emf.ecore 2 0 2007-03-21 10:42:38.359
> !MESSAGE Both 'org.apache.geronimo.deployment.model' and 
> 'org.apache.geronimo.v11.deployment.model' register an extension parser for 
> 'web'
> 
> JDK 1.5.0_11
> 
> !SESSION 2007-03-21 10:46:15.625 
> ---
> eclipse.buildId=M20070212-1330
> java.version=1.5.0_11
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Command-line arguments:  -os win32 -ws win32 -arch x86 -clean -debug
> !ENTRY org.eclipse.emf.ecore 2 0 2007-03-21 10:46:22.421
> !MESSAGE Both 'org.apache.geronimo.deployment.model' and 
> 'org.apache.geronimo.v11.deployment.model' register an extension parser for 
> 'deployment'
> !ENTRY org.eclipse.emf.ecore 2 0 2007-03-21 10:46:22.421
> !MESSAGE Both 'org.apache.geronimo.deployment.model' and 
> 'org.apache.geronimo.v11.deployment.model' register an extension parser for 
> 'naming'
> !ENTRY org.eclipse.emf.ecore 2 0 2007-03-21 10:46:22.421
> !MESSAGE Both 'org.apache.geronimo.deployment.model' and 
> 'org.apache.geronimo.v11.deployment.model' register an extension parser for 
> 'web'
> ===
> When I try to open the Geronimo Deployment Plan Editor, I get:
> ===
> !ENTRY org.eclipse.jface 4 2 2007-03-21 10:50:02.187
> !MESSAGE Problems occurred when invoking code from plug-in: 
> "org.eclipse.jface".
> !STACK 0
> java.lang.NoClassDefFoundError: org/eclipse/core/resources/IFile
>   at 
> org.apache.geronimo.st.ui.editors.SharedDeploymentPlanEditor.getLoader(SharedDeploymentPlanEditor.java:94)
>   at 
> org.apache.geronimo.st.ui.editors.SharedDeploymentPlanEditor.loadDeploymentPlan(SharedDeploymentPlanEditor.java:86)
>   at 
> org.apache.geronimo.st.ui.editors.AbstractGeronimoDeploymentPlanEditor.init(AbstractGeronimoDeploymentPlanEditor.java:181)
>   at 
> org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
>   at 
> org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
>   at 
> org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
>   at 
> org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
>   at 
> org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
>   at 
> org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(Wor

Re: [jira] Closed: (GERONIMO-2638) Improve ModuleBuilder and ConfigurationBuilder interfaces to replace use of JarFile

[Sachin Patel]

yes it is.

-sachin


On Mar 21, 2007, at 9:07 AM, Tim McConnell wrote:


Hi Sachin, is this a duplicate of GERONIMO-1526 ??

Thanks,
Tim McConnell


Sachin Patel (JIRA) wrote:
 [ https://issues.apache.org/jira/browse/GERONIMO-2638? 
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sachin Patel closed GERONIMO-2638.
--
Resolution: Later
After reflecting on this solution, it does not fit in nicely with  
the current architecture and will need to investigate alternate  
solutions.
Improve ModuleBuilder and ConfigurationBuilder interfaces to  
replace use of JarFile
 
---


Key: GERONIMO-2638
URL: https://issues.apache.org/jira/browse/ 
GERONIMO-2638

Project: Geronimo
 Issue Type: RTC
 Security Level: public(Regular issues)  Components:  
deployment

   Affects Versions: 2.0-M1
   Reporter: Sachin Patel
Assigned To: Sachin Patel
Fix For: 2.0-M3

Attachments: GERONIMO-1526-v1.2.patch, GERONIMO-1526- 
v1.2.patch2

Re: org.apache.geronimo.system.main.Daemon and commons-cli

[Sachin Patel]

I agree, this is a usability regression.

-sachin


On Mar 20, 2007, at 5:08 PM, Jason Dillon wrote:

You have to wait several seconds for the bootstrap kernel to  
load... just to display the cli usage... that seems wrong IMO.

[jira] Closed: (GERONIMO-2638) Improve ModuleBuilder and ConfigurationBuilder interfaces to replace use of JarFile

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMO-2638.
--

Resolution: Later

After reflecting on this solution, it does not fit in nicely with the current 
architecture and will need to investigate alternate solutions.

> Improve ModuleBuilder and ConfigurationBuilder interfaces to replace use of 
> JarFile
> ---
>
> Key: GERONIMO-2638
> URL: https://issues.apache.org/jira/browse/GERONIMO-2638
> Project: Geronimo
>  Issue Type: RTC
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.0-M1
>Reporter: Sachin Patel
> Assigned To: Sachin Patel
> Fix For: 2.0-M3
>
> Attachments: GERONIMO-1526-v1.2.patch, GERONIMO-1526-v1.2.patch2
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-1594) deployment of a simple (only one jsp) web project failed

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMO-1594.
--

Resolution: Fixed

The Geronimo Eclipse Plugin works with Eclipse being launched with either 1.4.2 
or 1.5

> deployment of a simple (only one jsp) web project failed
> 
>
> Key: GERONIMO-1594
> URL: https://issues.apache.org/jira/browse/GERONIMO-1594
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
> Environment: windows xp SP2 with jsdk 1.4.2_10, geronimo 1.0, eclipse 
> Version: 3.1.1 Build id: M20050929-0840, st 1.0.0, geronimo plugin 1.0.0 
> (build of 25.01)
>Reporter: Mark Mauerwerk
> Fix For: Verification Required
>
>
> following the instructions of the ibm article deployment of a simple (only 
> one jsp) web project failed 
> Despite geronimo management console displays web app as running, my test jsp 
> is not there.
> I did not found any error message in the console window, but in .log (see 
> below) 
> !ENTRY org.apache.geronimo.devtools.eclipse.core 4 0 2006-02-05 19:16:45.78
> !MESSAGE Starting of configuration failed.  See .log for details.
> !STACK 0
> java.lang.Exception: Error unmarshaling return; nested exception is: 
>   java.lang.ClassNotFoundException: 
> org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI 
> class loader disabled)
> java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: 
>   java.lang.ClassNotFoundException: 
> org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI 
> class loader disabled)
>   at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
>   at sun.rmi.server.UnicastRef.invoke(Unknown Source)
>   at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
>   at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown 
> Source)
>   at 
> javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(Unknown
>  Source)
>   at 
> org.apache.geronimo.kernel.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:339)
>   at 
> org.apache.geronimo.kernel.jmx.KernelDelegate.getGBeanState(KernelDelegate.java:121)
>   at 
> org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:64)
>   at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI 
> class loader disabled)
>   at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
>   at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
>   at java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source)
>   at java.rmi.server.RMIClassLoader.loadClass(Unknown Source)
>   at sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source)
>   at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
>   at java.io.ObjectInputStream.readClassDesc(Unknown Source)
>   at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
>   at java.io.ObjectInputStream.readObject0(Unknown Source)
>   at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
>   at java.io.ObjectInputStream.readSerialData(Unknown Source)
>   at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
>   at java.io.ObjectInputStream.readObject0(Unknown Source)
>   at java.io.ObjectInputStream.readObject(Unknown Source)
>   ... 9 more
>   at 
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:352)
>   at 
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:299)
>   at 
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:241)
>   at 
> org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:225)
>   at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658)
>   at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738)
>   at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596)
>   at 
> org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799)
>   at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788)
>   at 
> org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-1454) Deploy tool/API running on 1.5 jre fails against Geronimo 1.0 running in 1.4

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMO-1454.
--

   Resolution: Fixed
Fix Version/s: (was: Verification Required)
   1.1.1

This was fixed in devtools a long time ago.

> Deploy tool/API running on 1.5 jre fails against Geronimo 1.0 running in 1.4
> 
>
> Key: GERONIMO-1454
> URL: https://issues.apache.org/jira/browse/GERONIMO-1454
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 1.0
> Environment: Eclipse: 3.1.1 (Build ID: M20050929-0840)
> Java SE: 1.5.0_06-b05 (aka 5.0)
> OS: Linux ubuntu-abysssix 2.6.12-10-686-smp
> eclipse-plugin: trunk
> build cmd: maven build (without any Java VM option)
>Reporter: Daniel S. Haischt
>Priority: Critical
> Fix For: 1.1.1
>
>
> If starting Eclipse with a 5.x JDK, the Geronimo WTP-Adapter picks the 5.0 
> JDK as its runtime environment, even if the adapter and each corresponding 
> project was configured to *explicitly* use a Java 2 SE v1.4.x.
> Unfortunatly if using 5.x as its runtime env, Geronimo (i.e. the adapter) 
> obviously fails to deploy a J2EE app.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-1076) Deployment of an unpacked EAR defining an unpacked nested module does not work

[Sachin Patel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sachin Patel closed GERONIMO-1076.
--

   Resolution: Fixed
Fix Version/s: (was: Wish List)
   2.0

> Deployment of an unpacked EAR defining an unpacked nested module does not work
> --
>
> Key: GERONIMO-1076
> URL: https://issues.apache.org/jira/browse/GERONIMO-1076
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 1.0-M1, 1.0-M2, 1.0-M3, 1.0-M4, 1.0-M5
>Reporter: Gianny Damour
> Assigned To: Sachin Patel
> Fix For: 2.0
>
>
> An unpacked EAR defining an unpacked EJB module cannot be distributed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.