[jira] Updated: (GERONIMODEVTOOLS-94) Importing archives with non qualified plans cannot be opened with the editor
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94?page=all ] Lin Sun updated GERONIMODEVTOOLS-94: Attachment: devtools94.patch Patch has been tested on importing war projects. JAR project still doesn't want, but that is not because the import portion not working. Creating a new JAR project doesn't work either (devtools 103). > Importing archives with non qualified plans cannot be opened with the editor > > > Key: GERONIMODEVTOOLS-94 > URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 1.1.0 > Environment: Windows XP + AG 1.1 + Devtools 1.1 >Reporter: Lin Sun > Assigned To: Sachin Patel > Attachments: devtools94.patch > > > This looks like a defect. I seem to have forgot to implement support for > importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on > 1.1 plans). > On Aug 1, 2006, at 3:00 PM, Lin Sun wrote: > Hi there, > Has anyone been able to running jar or ear from within eclipse using the > devtools 1.1? > I have a MDB sample (from confluence) and I managed to get it running using > devtools 1.0 within eclipse. However, when I import my jar file in, the > openejb-jar.xml cannot be read by the Geronimo application deployment plan > editor. In the past experience, this is a pre-requisite before I can deploy > anything to Geronimo server in Eclipse. > I also tried to create a dummy EJB project and the default openejb-jar.xml > cannot be opened by the Geronimo application deployment plan editor either. > Similar prob with the EAR project. > I am wondering if this is a known limitation of the 1.1 version of devtools > project? Seems I can only get war project running... > Thanks, Lin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMODEVTOOLS-94) Importing archives with non qualified plans cannot be opened with the editor
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94?page=all ] Sachin Patel updated GERONIMODEVTOOLS-94: - Summary: Importing archives with non qualified plans cannot be opened with the editor (was: cannot run jar or ear from within eclipse) > Importing archives with non qualified plans cannot be opened with the editor > > > Key: GERONIMODEVTOOLS-94 > URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-94 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 1.1.0 > Environment: Windows XP + AG 1.1 + Devtools 1.1 >Reporter: Lin Sun > > This looks like a defect. I seem to have forgot to implement support for > importing non-qualified plans for 1.1. (i.e Running SchemaConversionUtil on > 1.1 plans). > On Aug 1, 2006, at 3:00 PM, Lin Sun wrote: > Hi there, > Has anyone been able to running jar or ear from within eclipse using the > devtools 1.1? > I have a MDB sample (from confluence) and I managed to get it running using > devtools 1.0 within eclipse. However, when I import my jar file in, the > openejb-jar.xml cannot be read by the Geronimo application deployment plan > editor. In the past experience, this is a pre-requisite before I can deploy > anything to Geronimo server in Eclipse. > I also tried to create a dummy EJB project and the default openejb-jar.xml > cannot be opened by the Geronimo application deployment plan editor either. > Similar prob with the EAR project. > I am wondering if this is a known limitation of the 1.1 version of devtools > project? Seems I can only get war project running... > Thanks, Lin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
