Re: [VOTE] Release Geronimo 3.0.1

[Yi Xiao]

Great！
+1


On Fri, May 17, 2013 at 9:56 PM, Forrest Xia  wrote:

> Hi Devs,
>
> Please vote Geronimo 3.0.1 release with these major differences from the
> previous release:
> 1. JSF 2.1 support
> 2. JDBC 4 support
> 3. Some components upgrade, including Tomcat, JPA, Yoko, Tranql, ActiveMQ
> 4. Quite a few bugs fixes
>
> For details, see
> http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1/RELEASE_NOTES-3.0.1.txt
>
> The server code up for vote is:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.zip
>
> The binary code up for vote is:
> Java EE 6 Full Profile Tomcat Assemblies:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.zip
>
> Java EE 6 Web Profile Tomcat Assemblies:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.zip
>
> Little-G Tomcat Assemblies:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.zip
>
> *Staging repo is:*
> https://repository.apache.org/content/repositories/orgapachegeronimo-009/
>
> *The tag has created at:*
> http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1
>
> Java EE 6 TCKs all passed!
>
> Vote will be at least open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> --
> Thanks!
>
> Regards, Forrest
>



-- 
Best regards!


 John Xiao

Re: [VOTE] Release Geronimo Tomcat fork 7.0.39.1

[Yi Xiao]

+1, it looks good to me.
Thanks for Forrest's effort.


On Fri, May 10, 2013 at 10:41 AM, Forrest Xia  wrote:

> Hi,
>
> Please revote for the Geronimo Tomcat 7.0.39.1 release, which is based on
> Tomcat 7.0.39 tag.
>
> The components up for vote are:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-029/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.39/7.0.39.1/tomcat-parent-7.0.39-7.0.39.1-source-release.zip
>
>
> Staging repo is here:
> https://repository.apache.org/content/repositories/orgapachegeronimo-029
>
> tag is here:
>
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.39.1
>
>
>  Vote open 72 hours
>
>  [ ] +1 release this
>  [ ] 0 don't care
>  [ ] -1 don't release this (please explain)
>
> --
> Thanks!
>
> Regards, Forrest
>



-- 
Best regards!


 John Xiao

[jira] [Updated] (GERONIMODEVTOOLS-806) The GEP3 could not install successfully in the customized eclipse which does not contain "org.eclipse.tm.terminal.view" plugin

[Yi Xiao (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-806:
-

Description: 
As some customized eclipse such as RAD does not contain 
"org.eclipse.tm.terminal.view" plugin, when check the dependency of the GEP, it 
will fail.

It's better change the "org.eclipse.tm.terminal.view" dependency as optional, 
and check the existence in GEP code. If not, suggest the user to install the 
plugin first from http://download.eclipse.org/dsdp/tm/updates/3.2.

  was:
As some customized eclipse such as RAD does not contain 
"org.eclipse.tm.terminal.view" plugin, when check the dependency of the GEP, it 
will fail.

It's better change the "org.eclipse.tm.terminal.view" dependency as optional, 
and check the existence in GEP code.


> The GEP3 could not install successfully in the customized eclipse which does 
> not contain "org.eclipse.tm.terminal.view" plugin
> --
>
> Key: GERONIMODEVTOOLS-806
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 3.0, 3.0-beta-1, 3.0-beta-2
>Reporter: Yi Xiao
>
> As some customized eclipse such as RAD does not contain 
> "org.eclipse.tm.terminal.view" plugin, when check the dependency of the GEP, 
> it will fail.
> It's better change the "org.eclipse.tm.terminal.view" dependency as optional, 
> and check the existence in GEP code. If not, suggest the user to install the 
> plugin first from http://download.eclipse.org/dsdp/tm/updates/3.2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMODEVTOOLS-806) The GEP3 could not install successfully in the customized eclipse which does not contain "org.eclipse.tm.terminal.view" plugin

[Yi Xiao (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-806:
-

Summary: The GEP3 could not install successfully in the customized eclipse 
which does not contain "org.eclipse.tm.terminal.view" plugin  (was: The gep3 
could not install successfully in the customized eclipse which does not contain 
"org.eclipse.tm.terminal.view" plugin)

> The GEP3 could not install successfully in the customized eclipse which does 
> not contain "org.eclipse.tm.terminal.view" plugin
> --
>
> Key: GERONIMODEVTOOLS-806
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 3.0, 3.0-beta-1, 3.0-beta-2
>Reporter: Yi Xiao
>
> As some customized eclipse such as RAD does not contain 
> "org.eclipse.tm.terminal.view" plugin, when check the dependency of the GEP, 
> it will fail.
> It's better change the "org.eclipse.tm.terminal.view" dependency as optional, 
> and check the existence in GEP code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-806) The gep3 could not install successfully in the customized eclipse which does not contain "org.eclipse.tm.terminal.view" plugin

[Yi Xiao (JIRA)]

Yi Xiao created GERONIMODEVTOOLS-806:


 Summary: The gep3 could not install successfully in the customized 
eclipse which does not contain "org.eclipse.tm.terminal.view" plugin
 Key: GERONIMODEVTOOLS-806
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806
 Project: Geronimo-Devtools
  Issue Type: Improvement
  Components: eclipse-plugin
Affects Versions: 3.0-beta-1, 3.0, 3.0-beta-2
Reporter: Yi Xiao


As some customized eclipse such as RAD does not contain 
"org.eclipse.tm.terminal.view" plugin, when check the dependency of the GEP, it 
will fail.

It's better change the "org.eclipse.tm.terminal.view" dependency as optional, 
and check the existence in GEP code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [ANNOUNCE] Geronimo Eclipse Plugin (GEP) v3.0.0 Release

[Yi Xiao]

Hi Johannes,

Other versions, like 2.1.7, 2.2.1 in GEP3.0.0 does not have enough test,
some bug fixes only exist on the separated GEP versions, so we still need
more effort to synchronize them :)

I think the Apache Geronimo Runtime could be removed, devs, have some
concerns?

On Tue, Aug 7, 2012 at 4:46 AM, Johannes Weberhofer <
jweberho...@weberhofer.at> wrote:

> Thank you John for the great work!
>
> May I suggest to remove the old stuff from the update site? I think, it's
> not useful for the average user to see lot's of old plugins there:
>
> * Apache Geronimo Runtime
>   - Geronimo 2.1.1 (Jetty) Runtime
>   - Geronimo 2.1.1 (Tomcat) Runtime
>
> * Geronimo WTP Server Adapter
>   - Geronimo Core Feature 2.1.1
>   - Geronimo v1.0 Server Adapter 2.0.0
>   - Geronimo v1.1.x Server Adapter 2.0.0
>   - Geronimo v2.0 Server Adapter 2.1.2
>   - Geronimo v2.1 Server Adapter 2.1.8
>   - Geronimo v2.2 Server Adapter 2.2.1
>   - Geronimo v3.0 Server Adapter 3.0.0
>
> Except the v3.0 Server Adapter all other stuff seems to be obsolete, as
> everything except the v1.0 Adapter (does anybody use that? A very old
> eclipse version is needed, too) seem to be included in v3.0.
>
> I think, also there should be only one version in future. Maybe the
> plugin-update process could be improved, too?
>
> Best regards,
> Johannes
>
>
> Am 06.08.12 10:35, schrieb Yi Xiao:
>
>  The Apache Geronimo project is pleased to announce the available of
>> Apache Geronimo Eclipse Plugin v3.0.0. It provides support for eclipse 3.7,
>> 3.8, 4.2 and latest Geronimo server 3.0.0
>>
>> Visit the link to GEP 3.0.0 release notes:
>> http://apache.org/dist/**geronimo/eclipse/updates/**
>> PLUGIN_RELEASE-NOTES-3.0.0.txt<http://apache.org/dist/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt>
>>
>> The new version have been available through eclipse update site now.
>> http://www.apache.org/dist/**geronimo/eclipse/updates/<http://www.apache.org/dist/geronimo/eclipse/updates/>
>>
>> For manual installation, GEP 3.0.0 can be downloaded from
>> http://apache.org/dist/**geronimo/eclipse/3.0.0/<http://apache.org/dist/geronimo/eclipse/3.0.0/>
>>
>> Thank you all for the contributions to this release!  Great work everyone!
>>
>> --
>> Best regards!
>>
>>
>>John Xiao
>>
>>
> --
> Johannes Weberhofer
> Weberhofer GmbH, Austria, Vienna
>



-- 
Best regards!


 John Xiao

[ANNOUNCE] Geronimo Eclipse Plugin (GEP) v3.0.0 Release

[Yi Xiao]

The Apache Geronimo project is pleased to announce the available of Apache
Geronimo Eclipse Plugin v3.0.0. It provides support for eclipse 3.7, 3.8,
4.2 and latest Geronimo server 3.0.0

Visit the link to GEP 3.0.0 release notes:
http://apache.org/dist/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt

The new version have been available through eclipse update site now.
http://www.apache.org/dist/geronimo/eclipse/updates/

For manual installation, GEP 3.0.0 can be downloaded from
http://apache.org/dist/geronimo/eclipse/3.0.0/

Thank you all for the contributions to this release!  Great work everyone!

-- 
Best regards!


 John Xiao

[RESULT][Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3

[Yi Xiao]

Hi devs,

The vote to release the Geronimo Eclipse Plugin 3.0.0 RC3 passes!

+1 votes: John, Johannes, Shawn, Viola, Forrest, Kevan
No -1 and 0 votes.

There are 3 "+1" from PMC members.

Thanks all for your time of review and vote.

-- 
Best regards!


 John Xiao

[Result][Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3

[Yi Xiao]

Hi devs,

The vote to release the Geronimo Eclipse Plugin 3.0.0 RC3 passes!

+1 votes: John, Johannes, Shawn, Viola, Forrest, Kevan
No -1 and 0 votes.

There are 3 "+1" from PMC members.

Thanks all for your time of review and vote.
-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3

[Yi Xiao]

Thanks for the reminder, Kevan :)

On Wed, Jul 25, 2012 at 11:28 PM, Kevan Miller wrote:

> Looks good. Here's my +1.
>
> One note -- the slf4j entry in the NOTICE file is not necessary. We comply
> with the terms of the SLF4J license:
>
> "The above copyright notice and this permission notice shall be included
> in all copies or substantial portions of the Software. "
>
> By including the SLF4J license in our LICENSE file, we meet the
> requirements of their license. No need to replicate the copyright in the
> NOTICE file. This is minor, IMO. And I'm ok with the NOTICE, as-is.
>
> --kevan
>
> On Jul 23, 2012, at 11:05 AM, Yi Xiao wrote:
>
> > Hi devs,
> >
> > Please help to review and vote on the release of Geronimo Eclipse Plugin
> (GEP) 3.0.0 RC3.
> >
> > GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
> 3.8, 4.2.
> >
> > [Known issue]
> > 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not
> be built successfully on 64bit win7 and 64bit macos. See following JIRAs
> for details.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
> build GEP3.0 under win7-64bit
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
> build GEP3.0 under macos-64bit
> > 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
> still open.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
> build GEP with maven 3.0
> > 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
> license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
> uses Eclipse Public License,  so the rat check on them are failed.
> >
> > The source code zip is here:
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz
> >
> > The tag is here:
> >
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/
> >
> > The deployable zip file is here:
> >
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip
> >
> > The p2 repo zip file is here:
> >
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip
> >
> > Notice: As update site format is not recommend in eclipse, now only
> provide the p2 format.
> >
> > If you would like to review and/or comment on the release notes, you can
> find it here:
> >
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt
> >
> > Finally, I've created a Staging Site that can be used to test the update
> manager functions of  Eclipse (Indigo SR2 and Juno):
> >
> > http://people.apache.org/builds/geronimo/eclipse/updates/
> >
> > The vote will be open for the 72-hour minimum.
> >
> > [  ] +1 about time to push this out the door
> > [  ]  0 no opinion
> > [  ] -1 not this one  (please explain why)
> > --
> > Best regards!
> >
> >
> John Xiao
> >
>
>


-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3

[Yi Xiao]

I build the source on ubuntu 10.04 64bit, run rat check and test run some
simple web apps against the release, it works fine, so my
 +1

On Mon, Jul 23, 2012 at 11:05 PM, Yi Xiao wrote:

> Hi devs,
>
> Please help to review and vote on the release of Geronimo Eclipse Plugin
> (GEP) 3.0.0 RC3.
>
> GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
> 3.8, 4.2.
>
> [Known issue]
> 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
> built successfully on 64bit win7 and 64bit macos. See following JIRAs for
> details.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
> build GEP3.0 under win7-64bit
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
> build GEP3.0 under macos-64bit
> 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
> still open.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
> build GEP with maven 3.0
> 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
> license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
> uses Eclipse Public License,  so the rat check on them are failed.
>
> The source code zip is here:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz
>
> The tag is here:
>
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/
>
> The deployable zip file is here:
>
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip
>
> The p2 repo zip file is here:
>
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip
>
> Notice: As update site format is not recommend in eclipse, now only
> provide the p2 format.
>
> If you would like to review and/or comment on the release notes, you can
> find it here:
>
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt
>
> Finally, I've created a Staging Site that can be used to test the update
> manager functions of  Eclipse (Indigo SR2 and Juno):
>
> http://people.apache.org/builds/geronimo/eclipse/updates/
>
> The vote will be open for the 72-hour minimum.
>
> [  ] +1 about time to push this out the door
> [  ]  0 no opinion
> [  ] -1 not this one  (please explain why)
> --
> Best regards!
>
>
>  John Xiao
>
>


-- 
Best regards!


 John Xiao

[Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3

[Yi Xiao]

Hi devs,

Please help to review and vote on the release of Geronimo Eclipse Plugin
(GEP) 3.0.0 RC3.

GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
3.8, 4.2.

[Known issue]
1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
built successfully on 64bit win7 and 64bit macos. See following JIRAs for
details.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
build GEP3.0 under win7-64bit
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
build GEP3.0 under macos-64bit
2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
still open.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build
GEP with maven 3.0
3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
uses Eclipse Public License,  so the rat check on them are failed.

The source code zip is here:
https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz

The tag is here:
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/

The deployable zip file is here:
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip

The p2 repo zip file is here:
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip

Notice: As update site format is not recommend in eclipse, now only provide
the p2 format.

If you would like to review and/or comment on the release notes, you can
find it here:
http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt

Finally, I've created a Staging Site that can be used to test the update
manager functions of  Eclipse (Indigo SR2 and Juno):

http://people.apache.org/builds/geronimo/eclipse/updates/

The vote will be open for the 72-hour minimum.

[  ] +1 about time to push this out the door
[  ]  0 no opinion
[  ] -1 not this one  (please explain why)
-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC2

[Yi Xiao]

Hi Johannes,

Thanks very much for your valuable test and patch. I committed code based
on your patch into the branch.
I start another vote for release, you could check it :)

On Sat, Jul 21, 2012 at 3:10 PM, Johannes Weberhofer <
jweberho...@weberhofer.at> wrote:

> Dear Yi Xiao!
>
> As I have only 64 environments available, I can not test the build
> process, but I tested the update site which works correct for me.
>
> Unfotunately my openejb-jar.xml files for an geronimo 2.2 server does not
> longer validate. That could have to do with the but I have filed under
> GERONIMODEVTOOLS-802. For previously valid projects I now get the following
> error message.
>
> Best regards,
> Johannes
>
> = Example file: openejb-jar.xml =
> 
> http://geronimo.**apache.org/xml/ns/j2ee/**
> application-2.0 <http://geronimo.apache.org/xml/ns/j2ee/application-2.0>"
> xmlns:client="http://geronimo.**apache.org/xml/ns/j2ee/**
> application-client-2.0<http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0>
> "
> xmlns:conn="http://geronimo.**apache.org/xml/ns/j2ee/**
> connector-1.2 <http://geronimo.apache.org/xml/ns/j2ee/connector-1.2>"
> xmlns:dep="http://geronimo.**apache.org/xml/ns/deployment-**1.2<http://geronimo.apache.org/xml/ns/deployment-1.2>
> "
> 
> xmlns:ejb="http://openejb.**apache.org/xml/ns/openejb-jar-**2.2<http://openejb.apache.org/xml/ns/openejb-jar-2.2>"
> xmlns:log="http://geronimo.**apache.org/xml/ns/loginconfig-**2.0<http://geronimo.apache.org/xml/ns/loginconfig-2.0>
> "
> 
> xmlns:name="http://geronimo.**apache.org/xml/ns/naming-1.2<http://geronimo.apache.org/xml/ns/naming-1.2>"
> xmlns:pers="http://java.sun.**com/xml/ns/persistence<http://java.sun.com/xml/ns/persistence>
> "
> 
> xmlns:pkgen="http://openejb.**apache.org/xml/ns/pkgen-2.1<http://openejb.apache.org/xml/ns/pkgen-2.1>"
> xmlns:sec="http://geronimo.**apache.org/xml/ns/security-2.0<http://geronimo.apache.org/xml/ns/security-2.0>
> **"
> 
> xmlns:web="http://geronimo.**apache.org/xml/ns/j2ee/web-2.**0.1<http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1>
> ">
> 
> 
> project
> ProjectEJB
> 1.0
> ejb
> 
> 
>
> 
> 
> ProjectEJB
> ejb/ProjectEJB<**/ejb:jndi-name>
> ejb/**
> ProjectEJBLocal
> 
> jdbc/projectDs<**
> /name:ref-name>
> projectDs<**
> /name:resource-link>
> 
> 
>
> 
> 
> = /Example file: openejb-jar.xml =
>
> = Error =
> cvc-complex-type.2.4.a: Invalid content was found starting with element
> 'name:resource-ref'. One of '{"http://openejb.apache.org/**
> xml/ns/openejb-jar-2.2 <http://openejb.apache.org/xml/ns/openejb-jar-2.2>
> ":local-**jndi-name, 
> "http://openejb.apache.org/**xml/ns/openejb-jar-2.2<http://openejb.apache.org/xml/ns/openejb-jar-2.2>":jndi,
> "http://openejb.apache.org/**xml/ns/openejb-jar-2.2<http://openejb.apache.org/xml/ns/openejb-jar-2.2>
> ":cache-**size, 
> "http://openejb.apache.org/**xml/ns/openejb-jar-2.2<http://openejb.apache.org/xml/ns/openejb-jar-2.2>
> ":tss-**link, 
> "http://openejb.apache.org/**xml/ns/openejb-jar-2.2<http://openejb.apache.org/xml/ns/openejb-jar-2.2>":tss,
> "http://geronimo.apache.org/**xml/ns/naming-1.2<http://geronimo.apache.org/xml/ns/naming-1.2>
> ":abstract-**naming-entry, 
> "http://geronimo.apache.org/**xml/ns/naming-1.2<http://geronimo.apache.org/xml/ns/naming-1.2>
> ":**persistence-context-ref, "http://geronimo.apache.org/**
> xml/ns/naming-1.2 <http://geronimo.apache.org/xml/ns/naming-1.2>":gbean-ref}'
> is expected.
> = /Error =
>
>
> Am Thu Jul 19 03:06:25 2012 schrieb Yi Xiao:
>
>> Could someone check the build/source and tell me the result?
>>
>> Thank you sincerely :)
>>
>> On Wed, Jul 18, 2012 at 6:05 PM, Yi Xiao > xiaoyijhondevelop@**gmail.com >> wrote:
>>
>> Hi devs,
>>
>> I've changed all the SNAPSHOT in testsuite and add the SLF4J license.
>&g

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC2

[Yi Xiao]

Could someone check the build/source and tell me the result?

Thank you sincerely :)

On Wed, Jul 18, 2012 at 6:05 PM, Yi Xiao wrote:

> Hi devs,
>
> I've changed all the SNAPSHOT in testsuite and add the SLF4J license.
>
> Please help to review and vote on the release of Geronimo Eclipse Plugin
> (GEP) 3.0.0 RC2.
>
> GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
> 3.8, 4.2.
>
> [Known issue]
> 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
> built successfully on 64bit win7 and 64bit macos. See following JIRAs for
> details.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
> build GEP3.0 under win7-64bit
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
> build GEP3.0 under macos-64bit
> 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
> still open.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
> build GEP with maven 3.0
> 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
> license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
> uses Eclipse Public License,  so the rat check on them are failed.
>
> The source code zip is here:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-064/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-064/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz
>
> The tag is here:
>
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/
>
> The deployable zip file is here:
>
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip
>
> The p2 repo zip file is here:
>
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip
>
> Notice: As update site format is not recommend in eclipse, now only
> provide the p2 format.
>
> If you would like to review and/or comment on the release notes, you can
> find it here:
>
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt
>
> Finally, I've created a Staging Site that can be used to test the update
> manager functions of  Eclipse (Indigo SR2 and Juno):
>
> http://people.apache.org/builds/geronimo/eclipse/updates/
>
> The vote will be open for the 72-hour minimum.
>
> [  ] +1 about time to push this out the door
> [  ]  0 no opinion
> [  ] -1 not this one  (please explain why)
> --
> Best regards!
>
>
>  John Xiao
>
>


-- 
Best regards!


 John Xiao

[Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC2

[Yi Xiao]

Hi devs,

I've changed all the SNAPSHOT in testsuite and add the SLF4J license.

Please help to review and vote on the release of Geronimo Eclipse Plugin
(GEP) 3.0.0 RC2.

GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
3.8, 4.2.

[Known issue]
1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
built successfully on 64bit win7 and 64bit macos. See following JIRAs for
details.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
build GEP3.0 under win7-64bit
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
build GEP3.0 under macos-64bit
2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
still open.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build
GEP with maven 3.0
3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
uses Eclipse Public License,  so the rat check on them are failed.

The source code zip is here:
https://repository.apache.org/content/repositories/orgapachegeronimo-064/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
https://repository.apache.org/content/repositories/orgapachegeronimo-064/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz

The tag is here:
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/

The deployable zip file is here:
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip

The p2 repo zip file is here:
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip

Notice: As update site format is not recommend in eclipse, now only provide
the p2 format.

If you would like to review and/or comment on the release notes, you can
find it here:
http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt

Finally, I've created a Staging Site that can be used to test the update
manager functions of  Eclipse (Indigo SR2 and Juno):

http://people.apache.org/builds/geronimo/eclipse/updates/

The vote will be open for the 72-hour minimum.

[  ] +1 about time to push this out the door
[  ]  0 no opinion
[  ] -1 not this one  (please explain why)
-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1

[Yi Xiao]

Thank you very much, Kevan.

I will add the SLF4J license and release again.

On Tue, Jul 17, 2012 at 9:20 PM, Kevan Miller wrote:

>
> On Jul 17, 2012, at 2:29 AM, Yi Xiao wrote:
>
> > Hi Kevan,
> >
> > I think you use maven3 to execute mvn :) now, GEP only support maven2,
> you could refer to [Known issue] 2
> >
> > And also, if you use MAC-64bit, will still get some error infos for
> [Known issue] 1.
>
> Thanks for the reminders John. I forget everytime… ;-)
>
> Everything looks pretty good, except it seems we're missing the slf4j
> license (we're redistributing slffj-api and slf4j-simple in
> org.apache.geronimo.runtime.v30_3.0.0.jar
>
> Here's my -1, until we address that…
>
> As long as we have people validating the build, I'll be +1 once the
> licensing issue is resolved. Thanks!
>
> --kevan
>
>


-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1

[Yi Xiao]

Hi Kevan,

I think you use maven3 to execute mvn :) now, GEP only support maven2, you
could refer to [Known issue] 2

And also, if you use MAC-64bit, will still get some error infos for [Known
issue] 1.


On Tue, Jul 17, 2012 at 12:32 AM, Kevan Miller wrote:

> Anybody building successfully on a Mac? I'm getting errors like:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> (default-compile) on project org.apache.geronimo.runtime.common:
> Compilation failure: Compilation failure:
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.0/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[21,31]
> package org.eclipse.core.runtime does not exist
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.0/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[22,31]
> package org.eclipse.core.runtime does not exist
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.0/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[23,31]
> package org.eclipse.core.runtime does not exist
> [ERROR]
>
> --kevan
>
> On Jul 16, 2012, at 5:23 AM, Yi Xiao wrote:
>
> > Hi devs,
> >
> > Please help to review and vote on the release of Geronimo Eclipse Plugin
> (GEP) 3.0.0 RC1.
> >
> > GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
> 3.8, 4.2.
> >
> > [Known issue]
> > 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not
> be built successfully on 64bit win7 and 64bit macos. See following JIRAs
> for details.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
> build GEP3.0 under win7-64bit
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
> build GEP3.0 under macos-64bit
> > 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
> still open.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
> build GEP with maven 3.0
> > 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
> license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
> uses Eclipse Public License,  so the rat check on them are failed.
> >
> > The source code zip is here:
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz
> >
> > The tag is here:
> >
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/
> >
> > The deployable zip file is here:
> >
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip
> >
> > The p2 repo zip file is here:
> >
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip
> >
> > Notice: As update site format is not recommend in eclipse, now only
> provide the p2 format.
> >
> > If you would like to review and/or comment on the release notes, you can
> find it here:
> >
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt
> >
> > Finally, I've created a Staging Site that can be used to test the update
> manager functions of  Eclipse (Indigo SR2 and Juno):
> > http://people.apache.org/builds/geronimo/eclipse/updates/
> >
> > The vote will be open for the 72-hour minimum.
> >
> > [  ] +1 about time to push this out the door
> > [  ]  0 no opinion
> > [  ] -1 not this one  (please explain why)
> >
> > --
> > Best regards!
> >
> >
> John Xiao
> >
>
>


-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1

[Yi Xiao]

Hi Jarek,

You are right.
 I use mvn release:prepare -Pallsubproject and mvn release:perform
-Pallsubproject but there is no allsubproject profile...

Thank you for pointing it out.
I will re-release it.

On Mon, Jul 16, 2012 at 11:23 PM, Jarek Gawor  wrote:

> John,
>
> Looks like the testsuite pom files still use SNAPSHOT versions.
>
> Jarek
>
> On Mon, Jul 16, 2012 at 5:23 AM, Yi Xiao 
> wrote:
> > Hi devs,
> >
> > Please help to review and vote on the release of Geronimo Eclipse Plugin
> > (GEP) 3.0.0 RC1.
> >
> > GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
> 3.8,
> > 4.2.
> >
> > [Known issue]
> > 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
> > built successfully on 64bit win7 and 64bit macos. See following JIRAs for
> > details.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
> build
> > GEP3.0 under win7-64bit
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
> build
> > GEP3.0 under macos-64bit
> > 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
> > still open.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
> build
> > GEP with maven 3.0
> > 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
> > license and
> plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
> > uses Eclipse Public License,  so the rat check on them are failed.
> >
> > The source code zip is here:
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
> >
> https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz
> >
> > The tag is here:
> >
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/
> >
> > The deployable zip file is here:
> >
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip
> >
> > The p2 repo zip file is here:
> >
> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip
> >
> > Notice: As update site format is not recommend in eclipse, now only
> provide
> > the p2 format.
> >
> > If you would like to review and/or comment on the release notes, you can
> > find it here:
> >
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt
> >
> > Finally, I've created a Staging Site that can be used to test the update
> > manager functions of  Eclipse (Indigo SR2 and Juno):
> > http://people.apache.org/builds/geronimo/eclipse/updates/
> >
> > The vote will be open for the 72-hour minimum.
> >
> > [  ] +1 about time to push this out the door
> > [  ]  0 no opinion
> > [  ] -1 not this one  (please explain why)
> >
> > --
> > Best regards!
> >
> >
> > John Xiao
> >
>



-- 
Best regards!


 John Xiao

[Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1

[Yi Xiao]

Hi devs,

Please help to review and vote on the release of Geronimo Eclipse Plugin
(GEP) 3.0.0 RC1.

GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7,
3.8, 4.2.

[Known issue]
1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
built successfully on 64bit win7 and 64bit macos. See following JIRAs for
details.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
build GEP3.0 under win7-64bit
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
build GEP3.0 under macos-64bit
2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
still open.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build
GEP with maven 3.0
3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C
license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd
uses Eclipse Public License,  so the rat check on them are failed.

The source code zip is here:
https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz

The tag is here:
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/

The deployable zip file is here:
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip

The p2 repo zip file is here:
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip

Notice: As update site format is not recommend in eclipse, now only provide
the p2 format.

If you would like to review and/or comment on the release notes, you can
find it here:
http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt

Finally, I've created a Staging Site that can be used to test the update
manager functions of  Eclipse (Indigo SR2 and Juno):
http://people.apache.org/builds/geronimo/eclipse/updates/

The vote will be open for the 72-hour minimum.

[  ] +1 about time to push this out the door
[  ]  0 no opinion
[  ] -1 not this one  (please explain why)

-- 
Best regards!


 John Xiao

Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1

[Yi Xiao]

Oh, there are two errors in the vote.

*Cancel this one*, I will open a new one.

Sorry for my carelessness.

On Mon, Jul 16, 2012 at 5:04 PM, Shawn Jiang  wrote:

>
>
> On Mon, Jul 16, 2012 at 4:23 PM, Yi Xiao wrote:
>
>> *GEP 3.0-beta**-1 *supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and
>> Eclipse 3.7, 3.8, 4.2
>
>
> I guess GEP 3.0-beta-1 was released ?
>
>
>
>
>
> --
> Shawn
>



-- 
Best regards!


 John Xiao

[Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1

[Yi Xiao]

Hi devs,

Please help to review and vote on the release of Geronimo Eclipse Plugin (
GEP) 3.0.0 RC1.

GEP 3.0-beta-1 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse
3.7, 3.8, 4.2.

[Known issue]
1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
built successfully on 64bit win7 and 64bit macos. See following JIRAs for
details.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
build GEP3.0 under win7-64bit
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
build GEP3.0 under macos-64bit
2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
still open.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build
GEP with maven 3.0
3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd
and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd don't
have apache license, so the rat check on them are fail.

The source code zip is here:
*
https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip
*
*
https://repository.apache.org/content/repositories/orgapachegeronimo-053/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz
*
The tag is here:
*
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/
*

The deployable zip file is here:
*
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip
*

The p2 repo zip file is here:
*
http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip
*

If you would like to review and/or comment on the release notes, you can
find it here:
http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt

Finally, I've created a Staging Site that can be used to test the update
manager functions of  Eclipse (Indigo and helios):
http://people.apache.org/builds/geronimo/eclipse/updates/

The vote will be open for the 72-hour minimum.

[  ] +1 about time to push this out the door
[  ]  0 no opinion
[  ] -1 not this one  (please explain why)

-- 
Best regards!


 John Xiao

Re: [Discuss] Prepare to release GEP3.0.0

[Yi Xiao]

yes, you are right.

On Fri, Jul 13, 2012 at 4:38 PM, Johannes Weberhofer <
jweberho...@weberhofer.at> wrote:

>
>
> Am 13.07.12 07:54, schrieb Yi Xiao:
>
>  Hi Johannes,
>>
>> Thank you for your comments. I think it's a good suggestion :)
>>
>> The only risk is that the previous releases like 2.1.7, 2.2.1 have
>> separated the fixed code in each branch, so we need to
>> get all the fix code and merge into 3.0 branch. I think we could create a
>> task to complete it.
>>
>
> That sounds good. I have always thought, that all patches go to trunk
> first - as the 3.0.0 version offers connectors to most Geronimo versions.
>
> Johannes
>
>
>  On Thu, Jul 12, 2012 at 10:51 PM, Johannes Weberhofer <
>> jweberho...@weberhofer.at 
>> <mailto:jweberhofer@**weberhofer.at>>
>> wrote:
>>
>> Dear John!
>>
>> I'll like to bring this into discussion again:
>>
>> Is it really necessary, to have so many GEP versions in parallel?
>> Shouldn't there be always one version which supports all current Geronimo
>> versions?
>>
>> Currently, there is eg. GEP_2.1.7 (when I'm right), which supports
>> G<2.1.7; GEP_2.2 supports G=2.2 and G<2.1.2 (or similar) etc.
>>
>> I think, that's confusing for someone who likes to install the GEP
>> plugins. I'd recomment to remove all the older versions, and have only one
>> recent version. 3.0.0 could support everything up to 3.0.0; in case a
>> G2.2.1 will be released, there could be a new GEP 3.0.0.1, which adds
>> support to that...
>>
>> Best regards,
>> Johannes
>>
>> Am Thu Jul 12 10:31:25 2012 schrieb Yi Xiao:
>>
>> Hi All,
>>
>> As Geronimo 3.0.0 is released, I think it's the time for
>> releasing GEP3.0.0
>>
>> I've create the branch https://svn.apache.org/repos/_**
>> _asf/geronimo/devtools/**eclipse-__plugin/branches/3.0<https://svn.apache.org/repos/__asf/geronimo/devtools/eclipse-__plugin/branches/3.0><
>> https://svn.apache.org/repos/**asf/geronimo/devtools/eclipse-**
>> plugin/branches/3.0<https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/3.0>>
>> to track the code for release, the base line is @1344906 in trunk,
>>
>> I didn't create the branch from the latest revision as
>> GERONIMODEVTOOLS-796 and GERONIMODEVTOOLS-791 also need the server
>> supports, but Geronimo3.0.0 has been released.
>>
>> However, I will merge other important jiras after 796 into
>> GEP3.0.0 for better user experience and then follow the release process.
>>
>> Have any other suggestions?
>>
>> --
>> Best regards!
>>
>>
>>John Xiao
>>
>>
>> --
>> Johannes Weberhofer
>> Weberhofer GmbH, Austria, Vienna
>>
>>
>>
>>
>> --
>> Best regards!
>>
>>
>>John Xiao
>>
>>
> --
> Johannes Weberhofer
> Weberhofer GmbH, Austria, Vienna
>
>
>


-- 
Best regards!


 John Xiao

Re: [Discuss] Prepare to release GEP3.0.0

[Yi Xiao]

Hi Johannes,

Thank you for your comments. I think it's a good suggestion :)

The only risk is that the previous releases like 2.1.7, 2.2.1 have
separated the fixed code in each branch, so we need to
get all the fix code and merge into 3.0 branch. I think we could create a
task to complete it.

On Thu, Jul 12, 2012 at 10:51 PM, Johannes Weberhofer <
jweberho...@weberhofer.at> wrote:

> Dear John!
>
> I'll like to bring this into discussion again:
>
> Is it really necessary, to have so many GEP versions in parallel?
> Shouldn't there be always one version which supports all current Geronimo
> versions?
>
> Currently, there is eg. GEP_2.1.7 (when I'm right), which supports
> G<2.1.7; GEP_2.2 supports G=2.2 and G<2.1.2 (or similar) etc.
>
> I think, that's confusing for someone who likes to install the GEP
> plugins. I'd recomment to remove all the older versions, and have only one
> recent version. 3.0.0 could support everything up to 3.0.0; in case a
> G2.2.1 will be released, there could be a new GEP 3.0.0.1, which adds
> support to that...
>
> Best regards,
> Johannes
>
> Am Thu Jul 12 10:31:25 2012 schrieb Yi Xiao:
>
>  Hi All,
>>
>> As Geronimo 3.0.0 is released, I think it's the time for releasing
>> GEP3.0.0
>>
>> I've create the branch https://svn.apache.org/repos/**
>> asf/geronimo/devtools/eclipse-**plugin/branches/3.0<https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/3.0>to
>>  track the code for release, the base line is @1344906 in trunk,
>> I didn't create the branch from the latest revision as
>> GERONIMODEVTOOLS-796 and GERONIMODEVTOOLS-791 also need the server
>> supports, but Geronimo3.0.0 has been released.
>>
>> However, I will merge other important jiras after 796 into GEP3.0.0 for
>> better user experience and then follow the release process.
>>
>> Have any other suggestions?
>>
>> --
>> Best regards!
>>
>>
>>   John Xiao
>>
>>
> --
> Johannes Weberhofer
> Weberhofer GmbH, Austria, Vienna
>



-- 
Best regards!


 John Xiao

[jira] [Resolved] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-799.
--

   Resolution: Fixed
Fix Version/s: 3.0

> Could not synchronize the security tab with source tab in 
> geronimo-application.xml and openejb-jar.xml
> --
>
> Key: GERONIMODEVTOOLS-799
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 3.0
>
>
> When edit, add, remove the security realm in geronimo-application.xml and 
> openejb-jar.xml, there is always the ClassCastException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Discuss] Prepare to release GEP3.0.0

[Yi Xiao]

Hi All,

As Geronimo 3.0.0 is released, I think it's the time for releasing GEP3.0.0

I've create the branch
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/3.0
to
track the code for release, the base line is @1344906 in trunk,
I didn't create the branch from the latest revision as GERONIMODEVTOOLS-796
and GERONIMODEVTOOLS-791 also need the server supports, but Geronimo3.0.0
has been released.

However, I will merge other important jiras after 796 into GEP3.0.0 for
better user experience and then follow the release process.

Have any other suggestions?

-- 
Best regards!


 John Xiao

Re: svn commit: r1360074 - /geronimo/devtools/eclipse-plugin/branches/3.0/

[Yi Xiao]

Hi Jarek,

Sorry for making you confuse, I should make the announce first.

I'm prepare for release GEP3.0.0 now, I will send a mail to announce my
release purpose with the steps.

Yes, you are right, I should only change the server version in the branch,
I will change back in trunk later.

Sorry again for not announce the release preparation.

On Wed, Jul 11, 2012 at 10:36 PM, Jarek Gawor  wrote:

> John,
>
> I'm so confused on what's going on... If you are planning a release of
> GEP (and branching the code) that should have been announced to the
> list first. I didn't see such a note. Also, it looks like you branched
> the trunk code from a few days ago (that's good) but if somebody just
> read the svn log message they would assume that latest trunk code was
> branched. We need to be very clear about that. And finally, people are
> actively working on the GEP trunk and now you changed the Geronimo
> version to 3.0 instead 3.0.1-SNAPSHOT as it was correctly updated a
> few days ago. The Geronimo version should have been updated in the GEP
> 3.0 release branch only.
>
> Jarek
>
> On Wed, Jul 11, 2012 at 4:55 AM,   wrote:
> > Author: johnxiao
> > Date: Wed Jul 11 08:55:26 2012
> > New Revision: 1360074
> >
> > URL: http://svn.apache.org/viewvc?rev=1360074&view=rev
> > Log:
> > GERONIMODEVTOOLS-800 Release GEP3.0.0, copy from trunk to branches
> >
> > Added:
> > geronimo/devtools/eclipse-plugin/branches/3.0/   (props changed)
> >   - copied from r1344906, geronimo/devtools/eclipse-plugin/trunk/
> >
> > Propchange: geronimo/devtools/eclipse-plugin/branches/3.0/
> >
> --
> > --- svk:merge (added)
> > +++ svk:merge Wed Jul 11 08:55:26 2012
> > @@ -0,0 +1,2 @@
> >
> +13f79535-47bb-0310-9956-ffa450edef68:/geronimo/devtools/eclipse-plugin/branches/1.2.1:499026
> > +47d51c14-9805-4038-8224-40f2b3020a56:/local/G1526-eclipse:3238
> >
> > Propchange: geronimo/devtools/eclipse-plugin/branches/3.0/
> >
> --
> > --- svn:ignore (added)
> > +++ svn:ignore Wed Jul 11 08:55:26 2012
> > @@ -0,0 +1,3 @@
> > +*.iws
> > +*.ipr
> > +*.iml
> >
> > Propchange: geronimo/devtools/eclipse-plugin/branches/3.0/
> >
> --
> > svn:mergeinfo =
> /geronimo/devtools/eclipse-plugin/branches/2.1.4:734752-734846
> >
> >
>



-- 
Best regards!


 John Xiao

[jira] [Resolved] (GERONIMODEVTOOLS-778) Using GEP3.0.X's eclipse/build.xml to replace the GEP2.1.X's

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-778.
--

Resolution: Fixed

> Using GEP3.0.X's eclipse/build.xml to replace the GEP2.1.X's
> 
>
> Key: GERONIMODEVTOOLS-778
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-778
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.1.8
>    Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: ant, build.xml
> Attachments: usingGep3.0AntScriptInEclipse_778.patch, 
> usingGep3.0AntScriptInEclipse_778_1.patch
>
>
> The build.xml in GEP3.0.x supports the latest eclipse3.7SR1 and is more 
> graceful than GEP2.1.x's.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-779) Release GEP2.1.8

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-779.
--

   Resolution: Fixed
Fix Version/s: 2.1.8

> Release GEP2.1.8
> 
>
> Key: GERONIMODEVTOOLS-779
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-779
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.1.8
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 2.1.8
>
> Attachments: releaseGep218_779.patch, releaseGep218_779_1.patch, 
> releaseGep218_changeVersion_779_1.patch, releaseNotes_779.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-789) Improve SynchronizeProjectOnServerTask

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-789.
--

   Resolution: Fixed
Fix Version/s: 3.0

> Improve SynchronizeProjectOnServerTask
> --
>
> Key: GERONIMODEVTOOLS-789
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-789
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> There are some intermittent problems with SynchronizeProjectOnServerTask that 
> cause modules in the server view to disappear sometimes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-790) Application started twice

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-790.
--

   Resolution: Fixed
Fix Version/s: 3.0

> Application started twice
> -
>
> Key: GERONIMODEVTOOLS-790
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-790
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> Say we have an application that is already deployed to the server and the 
> server is stopped. Now, the application is modified while the server is 
> stopped and server restarted. What happens is that when server starts up, it 
> will start the "old" version of the application. And after the server is full 
> started, Eclipse will automatically deploy the "new" application. That's 
> usuallly ok but if you are dealing with large applications or applications 
> that take some time to initialize that's very painful. 
> So the idea here is that when such case happens only the "new" version of the 
> application is deployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-792.
--

   Resolution: Fixed
Fix Version/s: 3.0

> Provide the GEP build the unique timestamps each time
> -
>
> Key: GERONIMODEVTOOLS-792
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: GEP, timestamp
> Fix For: 3.0
>
>
> Provide the feature to let p2 updates GEP more conveniently.
> Using the -PbuildWithTimestamp(maven cmd parameter) to add the timestamp for 
> build

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMODEVTOOLS-794) Support Eclipse 4.2

[Yi Xiao (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-794:


Assignee: Jarek Gawor

> Support Eclipse 4.2
> ---
>
> Key: GERONIMODEVTOOLS-794
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-794
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
>
> Support GEP on Eclipse 4.2. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-794) Support Eclipse 4.2

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-794.
--

Resolution: Fixed

Have verified the issue, it works well now.

> Support Eclipse 4.2
> ---
>
> Key: GERONIMODEVTOOLS-794
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-794
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
>
> Support GEP on Eclipse 4.2. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-798.
--

Resolution: Fixed

> ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3
> 
>
> Key: GERONIMODEVTOOLS-798
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
> Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200)
> Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455
> Eclipse Web Developer Tools Version: 
> 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 
> 20110922230524)
> geronimo-tomcat7-javaee6-3.0-beta-1
>    Reporter: Michael Seele
>Assignee: Yi Xiao
> Attachments: patch.txt
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 
> you got a ClassCastException.
> The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a 
> IProject into the model instad of a String (please see the attached Patch).
> If you want to try this you can use the sample project from here: 
> https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz
> This is the Exception you get:
> java.lang.ClassCastException: org.eclipse.core.internal.resources.Project 
> cannot be cast to java.lang.String
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385)
>   at 
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207)
>   at 
> org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143)
>   at 
> org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51)
>   at 
> org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318)
>   at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
>   a

[jira] [Commented] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

[Yi Xiao (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-797:
--

Hi Johannes,

The issue has been resolved in GERONIMODEVTOOLS-799, thank you for your patch.

> Latest beta version does not work with Eclipse Juno because of invalid 
> openejb-jar-2.2.xsd file
> ---
>
> Key: GERONIMODEVTOOLS-797
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
> Environment: OS/X, Java 6, Geronimo 2.2.1
>Reporter: Johannes Weberhofer
> Fix For: 3.0
>
> Attachments: openejb-jar-2.2.xsd.patch
>
>
> openejb-jaar-2.2.xsd is not vaild. I have fixed some of the issues, mainly 
> import issues.
> Some notes: 
> * Updated "geronimo-application-1.2.xsd" to geronimo-application-2.0.xsd
> * Replaced "naming:entity-manager-factory-ref" by 
> "naming:persistence-context-ref": I'm not sure if that's correct
> *  is already defined in 
> geronimo-naming-1.2.xsd - but slightly different. For the meoment I removed 
> it from the xsd, but I don't know how the remaining values should be handled
> * In the complexTypes "session-beanType", "openejb-jarType", 
> "message-driven-beanType" and "entity-beanType" there are violations of the 
> "Unique Particle Attribution" 
> (http://www.w3.org/TR/xmlschema-1/#cos-nonambig) in the "xs:choice" sections. 
> I don't know how to handle that correctly.
> For the changed lines, I attach a patch which could be used as basis for 
> further work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

[Yi Xiao (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-797.
--

   Resolution: Fixed
Fix Version/s: 3.0

> Latest beta version does not work with Eclipse Juno because of invalid 
> openejb-jar-2.2.xsd file
> ---
>
> Key: GERONIMODEVTOOLS-797
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
> Environment: OS/X, Java 6, Geronimo 2.2.1
>Reporter: Johannes Weberhofer
> Fix For: 3.0
>
> Attachments: openejb-jar-2.2.xsd.patch
>
>
> openejb-jaar-2.2.xsd is not vaild. I have fixed some of the issues, mainly 
> import issues.
> Some notes: 
> * Updated "geronimo-application-1.2.xsd" to geronimo-application-2.0.xsd
> * Replaced "naming:entity-manager-factory-ref" by 
> "naming:persistence-context-ref": I'm not sure if that's correct
> *  is already defined in 
> geronimo-naming-1.2.xsd - but slightly different. For the meoment I removed 
> it from the xsd, but I don't know how the remaining values should be handled
> * In the complexTypes "session-beanType", "openejb-jarType", 
> "message-driven-beanType" and "entity-beanType" there are violations of the 
> "Unique Particle Attribution" 
> (http://www.w3.org/TR/xmlschema-1/#cos-nonambig) in the "xs:choice" sections. 
> I don't know how to handle that correctly.
> For the changed lines, I attach a patch which could be used as basis for 
> further work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3

[Yi Xiao (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-798:
--

I use eclipse 4.2 to investigate the issue. In 4.2, add the new method 
getModuleParticipants(...) uses the 
J2EEComponentExportDataModelProvider.PROJECT_NAME property.

We should set the J2EEComponentExportDataModelProvider.PROJECT_NAME to the 
String type according to all the usage method in eclipse. I also add the code 
into 
org.apache.geronimo.st.core.DeploymentUtils

I committed at revision 1360166 thanks very much for Michael's patch.

> ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3
> 
>
> Key: GERONIMODEVTOOLS-798
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
> Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200)
> Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455
> Eclipse Web Developer Tools Version: 
> 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 
> 20110922230524)
> geronimo-tomcat7-javaee6-3.0-beta-1
>    Reporter: Michael Seele
>Assignee: Yi Xiao
> Attachments: patch.txt
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 
> you got a ClassCastException.
> The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a 
> IProject into the model instad of a String (please see the attached Patch).
> If you want to try this you can use the sample project from here: 
> https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz
> This is the Exception you get:
> java.lang.ClassCastException: org.eclipse.core.internal.resources.Project 
> cannot be cast to java.lang.String
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385)
>   at 
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207)
>   at 
> org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143)
>   at 
> org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51)
>   at 
> org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717)
>   at 
> org.apache.geron

[jira] [Commented] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3

[Yi Xiao (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-798:
--

Hi Michael,

Thank you for your patch.
I'm not sure if your patch will effect the previous eclipse, I will investigate 
the issue in these days.

> ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3
> 
>
> Key: GERONIMODEVTOOLS-798
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
> Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200)
> Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455
> Eclipse Web Developer Tools Version: 
> 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 
> 20110922230524)
> geronimo-tomcat7-javaee6-3.0-beta-1
>    Reporter: Michael Seele
>Assignee: Yi Xiao
> Attachments: patch.txt
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 
> you got a ClassCastException.
> The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a 
> IProject into the model instad of a String (please see the attached Patch).
> If you want to try this you can use the sample project from here: 
> https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz
> This is the Exception you get:
> java.lang.ClassCastException: org.eclipse.core.internal.resources.Project 
> cannot be cast to java.lang.String
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385)
>   at 
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207)
>   at 
> org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143)
>   at 
> org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51)
>   at 
> org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441)
>   at 
> o

[jira] [Assigned] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3

[Yi Xiao (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-798:


Assignee: Yi Xiao

> ClassCastException deploying EAR under eclipse 3.8 & 4.2 with geronimo-3
> 
>
> Key: GERONIMODEVTOOLS-798
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
> Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200)
> Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455
> Eclipse Web Developer Tools Version: 
> 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 
> 20110922230524)
> geronimo-tomcat7-javaee6-3.0-beta-1
>    Reporter: Michael Seele
>Assignee: Yi Xiao
> Attachments: patch.txt
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 
> you got a ClassCastException.
> The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a 
> IProject into the model instad of a String (please see the attached Patch).
> If you want to try this you can use the sample project from here: 
> https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz
> This is the Exception you get:
> java.lang.ClassCastException: org.eclipse.core.internal.resources.Project 
> cannot be cast to java.lang.String
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191)
>   at 
> org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385)
>   at 
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
>   at 
> org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207)
>   at 
> org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143)
>   at 
> org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51)
>   at 
> org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84)
>   at 
> org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441)
>   at 
> org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318)
>   at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
>   a

[jira] [Deleted] (GERONIMODEVTOOLS-801) Release GEP3.0.0

[Yi Xiao (JIRA)]

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

Yi Xiao deleted GERONIMODEVTOOLS-801:
-


> Release GEP3.0.0
> 
>
> Key: GERONIMODEVTOOLS-801
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-801
> Project: Geronimo-Devtools
>  Issue Type: Task
>    Reporter: Yi Xiao
>Assignee: Yi Xiao
>
> Release the GEP3.0.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-801) Release GEP3.0.0

[Yi Xiao (JIRA)]

Yi Xiao created GERONIMODEVTOOLS-801:


 Summary: Release GEP3.0.0
 Key: GERONIMODEVTOOLS-801
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-801
 Project: Geronimo-Devtools
  Issue Type: Task
Reporter: Yi Xiao
Assignee: Yi Xiao


Release the GEP3.0.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-800) Release GEP3.0.0

[Yi Xiao (JIRA)]

Yi Xiao created GERONIMODEVTOOLS-800:


 Summary: Release GEP3.0.0
 Key: GERONIMODEVTOOLS-800
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-800
 Project: Geronimo-Devtools
  Issue Type: Task
Reporter: Yi Xiao


Release the GEP3.0.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml

[Yi Xiao (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-799:


Assignee: Yi Xiao

> Could not synchronize the security tab with source tab in 
> geronimo-application.xml and openejb-jar.xml
> --
>
> Key: GERONIMODEVTOOLS-799
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>
> When edit, add, remove the security realm in geronimo-application.xml and 
> openejb-jar.xml, there is always the ClassCastException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml

[Yi Xiao (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-799:
--

Committed at revision 1359524 and 1359587

> Could not synchronize the security tab with source tab in 
> geronimo-application.xml and openejb-jar.xml
> --
>
> Key: GERONIMODEVTOOLS-799
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799
> Project: Geronimo-Devtools
>  Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Yi Xiao
>
> When edit, add, remove the security realm in geronimo-application.xml and 
> openejb-jar.xml, there is always the ClassCastException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml

[Yi Xiao (JIRA)]

Yi Xiao created GERONIMODEVTOOLS-799:


 Summary: Could not synchronize the security tab with source tab in 
geronimo-application.xml and openejb-jar.xml
 Key: GERONIMODEVTOOLS-799
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799
 Project: Geronimo-Devtools
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Yi Xiao


When edit, add, remove the security realm in geronimo-application.xml and 
openejb-jar.xml, there is always the ClassCastException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Release Geronimo 3.0.0 (3rd Try)

[Yi Xiao]

 the build is ok, Signature/checksum looks good,
+1

On Fri, Jul 6, 2012 at 4:26 PM, Rex Wang  wrote:

> +1, All looked good to me, great to see 3.0!! Thanks Forrest!
>
> -Rex
>
>
> 2012/7/6 Forrest Xia 
>
>>
>>
>> On Thu, Jul 5, 2012 at 10:17 PM, Kevan Miller wrote:
>>
>>>
>>> On Jul 5, 2012, at 9:27 PM, Forrest Xia wrote:
>>>
>>> >
>>> >
>>> > On Fri, Jul 6, 2012 at 6:05 AM, Kevan Miller 
>>> wrote:
>>> >
>>> > On Jul 5, 2012, at 2:23 PM, David Jencks wrote:
>>> >
>>> > > I'm a little confused by the LICENSE and NOTICE in the source.  I've
>>> been telling people for years that these should apply to what is actually
>>> in the source, however these appear to be the ones appropriate for the
>>> binary distros.  For instance they point to files in the repository folder
>>> which only exists in the binary distro.
>>> >
>>> > That can be debated. And I've seen both styles used. I'm not sure
>>> which style I prefer. Separate source and binary license files may be more
>>> accurate, but they also may be misinterpreted. I do agree that
>>> license/notice in jar files should be source licenses…
>>> >
>>> > In any event, the current source LICENSE file clearly indicates what
>>> applies to source and binaries. A consumer of the source should be able to
>>> easily sort out what applies/doesn't apply… So, I'm fine with it as is…
>>> > Kevan, your vote?
>>>
>>> Was waiting for build to finish. Given the US holidays, etc. I'd give
>>> this a few more days to gather additional votes…
>>>
>> OK, that's fine to wait a couple days for this vote.
>>
>>>
>>> --kevan
>>
>>
>>
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>>
>
>
> --
> Lei Wang (Rex)
> rwonly AT apache.org
>



-- 
Best regards!


 John Xiao

Re: [VOTE] Release Geronimo Samples 3.0.0

[Yi Xiao]

 Signature/checksum looks good, and build is ok
+1

On Fri, Jul 6, 2012 at 3:40 PM, Forrest Xia  wrote:

> Don't forget this one, please!
>
>
> On Wed, Jul 4, 2012 at 12:25 AM, Forrest Xia  wrote:
>
>> Hi Devs,
>>
>> Align with Geronimo 3.0.0 release, here is the Geronimo Samples 3.0.0
>> ready for vote.
>>
>> The source code up for vote is:
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-024/org/apache/geronimo/samples/samples-parent/3.0.0/samples-parent-3.0.0-source-release.tar.gz
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-024/org/apache/geronimo/samples/samples-parent/3.0.0/samples-parent-3.0.0-source-release.zip
>> 
>>
>> Staging repo is:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-024
>>
>>
>> The tag has created at:
>>
>> http://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0.0/
>>
>> Vote will be at least open for 72 hours.
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>>
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Best regards!


 John Xiao

Re: [VOTE] Release Geronimo 3.0.0 (3rd Try)

[Yi Xiao]

 Signature/checksum looks good
 +1

On Fri, Jul 6, 2012 at 3:39 PM, Forrest Xia  wrote:

>
>
> On Thu, Jul 5, 2012 at 10:17 PM, Kevan Miller wrote:
>
>>
>> On Jul 5, 2012, at 9:27 PM, Forrest Xia wrote:
>>
>> >
>> >
>> > On Fri, Jul 6, 2012 at 6:05 AM, Kevan Miller 
>> wrote:
>> >
>> > On Jul 5, 2012, at 2:23 PM, David Jencks wrote:
>> >
>> > > I'm a little confused by the LICENSE and NOTICE in the source.  I've
>> been telling people for years that these should apply to what is actually
>> in the source, however these appear to be the ones appropriate for the
>> binary distros.  For instance they point to files in the repository folder
>> which only exists in the binary distro.
>> >
>> > That can be debated. And I've seen both styles used. I'm not sure which
>> style I prefer. Separate source and binary license files may be more
>> accurate, but they also may be misinterpreted. I do agree that
>> license/notice in jar files should be source licenses…
>> >
>> > In any event, the current source LICENSE file clearly indicates what
>> applies to source and binaries. A consumer of the source should be able to
>> easily sort out what applies/doesn't apply… So, I'm fine with it as is…
>> > Kevan, your vote?
>>
>> Was waiting for build to finish. Given the US holidays, etc. I'd give
>> this a few more days to gather additional votes…
>>
> OK, that's fine to wait a couple days for this vote.
>
>>
>> --kevan
>
>
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Best regards!


 John Xiao

[jira] [Assigned] (GERONIMODEVTOOLS-791) Delete module while server is stopped

[Yi Xiao (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-791:


Assignee: Yi Xiao

> Delete module while server is stopped
> -
>
> Key: GERONIMODEVTOOLS-791
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Yi Xiao
>
> Right now when an application is removed (i.e. undeployed) from server view 
> in Eclipse when the server is stopped, the application is actually undeployed 
> from the server when the server is restarted. And in the process the 
> application is needlessly started before it is undeployed.
> I don't know if that's entirely possible but would be nice to actually delete 
> the application when the server is stopped (assuming GEP is connected to a 
> local server).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-791) Delete module while server is stopped

[Yi Xiao (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-791:
--

commit in GEP At revision: 1357610 and server at revision: 1357585

Like GERONIMODEVTOOLS-790, mark the removed applications when server is 
stopped, and pass them to server when server is started next time, the server 
won't start them, and then in GEP could delete them when synchronizing with 
server.

also, using the -Dorg.apache.geronimo.st.v30.core.manageApplicationStart=true 
system property to enable the feature.

> Delete module while server is stopped
> -
>
> Key: GERONIMODEVTOOLS-791
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>
> Right now when an application is removed (i.e. undeployed) from server view 
> in Eclipse when the server is stopped, the application is actually undeployed 
> from the server when the server is restarted. And in the process the 
> application is needlessly started before it is undeployed.
> I don't know if that's entirely possible but would be nice to actually delete 
> the application when the server is stopped (assuming GEP is connected to a 
> local server).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6368) Could not undeploy the application using deploy in offline mode

[Yi Xiao (JIRA)]

Yi Xiao created GERONIMO-6368:
-

 Summary: Could not undeploy the application using deploy in 
offline mode
 Key: GERONIMO-6368
 URL: https://issues.apache.org/jira/browse/GERONIMO-6368
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 3.0-beta-1
Reporter: Yi Xiao


When server is shutdown, using the command:
deploy -o undeploy moduleId

get the following exception:
java.lang.IllegalArgumentException: Artifact 
org.apache.geronimo.configs/openejb//car is not fully resolved
at 
org.apache.geronimo.kernel.repository.Maven2Repository.getLocation(Maven2Repository.java:37)
at 
org.apache.geronimo.kernel.repository.AbstractRepository.contains(AbstractRepository.java:61)
at 
org.apache.geronimo.system.configuration.DependencyManager.locateBundle(DependencyManager.java:536)
at 
org.apache.geronimo.system.configuration.DependencyManager.installed(DependencyManager.java:454)
at 
org.apache.geronimo.system.configuration.DependencyManager.bundleChanged(DependencyManager.java:118)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at 
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at 
org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1523)
at 
org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1459)
at 
org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:898)
at 
org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:833)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:137)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:131)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:309)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:290)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:125)
at 
org.apache.geronimo.deployment.plugin.local.UndeployCommand.run(UndeployCommand.java:58)
at java.lang.Thread.run(Unknown Source)
Deployer operation failed: load of default/TestWEB0/1.0/war failed
org.apache.geronimo.kernel.config.LifecycleException: load of 
default/TestWEB0/1.0/war failed
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:316)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:290)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:125)
at 
org.apache.geronimo.deployment.plugin.local.UndeployCommand.run(UndeployCommand.java:58)
at java.lang.Thread.run(Unknown Source)
Caused by: org.osgi.framework.BundleException: The bundle 
"default.TestWEB0_1.0.0 [292]" could not be resolved. Reason: Missing 
Constraint: Import-Package:
onimo.yoko; version="[0.0.0,0.0.0]"
at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
at 
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:311)
... 4 more
2012-07-03 19:20:39,887 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Operation failed: load of 
default/TestWEB0/1.0/war failed
org.apache.geronimo.kernel.config.LifecycleException: load of 
default/TestWEB0/1.0/war failed
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:316)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:290)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:125)
at 
org.apache.geronimo.deployment.plugin.local.UndeployCommand.run(UndeployCommand.java:58)
at java.lang.Thread.run(Unknown Source)
Caused by: org.osgi.framework.BundleE

[jira] [Updated] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time

[Yi Xiao (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-792:
-

Description: 
Provide the feature to let p2 updates GEP more conveniently.

Using the -PbuildWithTimestamp(maven cmd parameter) to add the timestamp for 
build

  was:Provide the feature to let p2 updates GEP more conveniently.


> Provide the GEP build the unique timestamps each time
> -
>
> Key: GERONIMODEVTOOLS-792
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: GEP, timestamp
>
> Provide the feature to let p2 updates GEP more conveniently.
> Using the -PbuildWithTimestamp(maven cmd parameter) to add the timestamp for 
> build

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time

[Yi Xiao (JIRA)]

Yi Xiao created GERONIMODEVTOOLS-792:


 Summary: Provide the GEP build the unique timestamps each time
 Key: GERONIMODEVTOOLS-792
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 3.0-beta-1
Reporter: Yi Xiao


Provide the feature to let p2 updates GEP more conveniently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time

[Yi Xiao (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-792:


Assignee: Yi Xiao

> Provide the GEP build the unique timestamps each time
> -
>
> Key: GERONIMODEVTOOLS-792
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792
> Project: Geronimo-Devtools
>  Issue Type: New Feature
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: GEP, timestamp
>
> Provide the feature to let p2 updates GEP more conveniently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6305:
---

If no concerns, I will commit to the trunk and branch.

> Start bundles in EBA according to bundle dependencies
> -
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: osgi-bundles
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: startBundlesInOrder_6305.patch, 
> startBundlesInOrder_6305_fix.patch
>
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[Yi Xiao (Issue Comment Edited) (JIRA)]

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

Yi Xiao edited comment on GERONIMO-6305 at 3/29/12 1:41 AM:


Sorry for response so late.

Ivan,
1&2 I have modified the code and the issues is gone now. About the 3, maybe 
could use the check cycle algorithm in future~

Jarek,

The algorithm you supplied will cause an endless-recursion if A->B->A, so still 
need a flag to mark the bundle is visited. I still
construct the graph first and then use DFS to get the sorted bundles.



  was (Author: john xiao):
Sorry for response so late.

Ivan,
1&2 I have modified the code and the issues is gone now. About the 3, maybe 
could use the check cycle algorithm in future~

Jarek,

The algorithm you supplied will cause an endless-loop if A->B->A, so still need 
a flag to mark the bundle is visited. I still
construct the graph first and then use DFS to get the sorted bundles.


  
> Start bundles in EBA according to bundle dependencies
> -
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>      Components: osgi-bundles
>    Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: startBundlesInOrder_6305.patch, 
> startBundlesInOrder_6305_fix.patch
>
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6305:
--

Attachment: startBundlesInOrder_6305_fix.patch

The new patch is startBundlesInOrder_6305_fix.patch

> Start bundles in EBA according to bundle dependencies
> -
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: osgi-bundles
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: startBundlesInOrder_6305.patch, 
> startBundlesInOrder_6305_fix.patch
>
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6305:
---

Sorry for response so late.

Ivan,
1&2 I have modified the code and the issues is gone now. About the 3, maybe 
could use the check cycle algorithm in future~

Jarek,

The algorithm you supplied will cause an endless-loop if A->B->A, so still need 
a flag to mark the bundle is visited. I still
construct the graph first and then use DFS to get the sorted bundles.



> Start bundles in EBA according to bundle dependencies
> -
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: osgi-bundles
>    Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: startBundlesInOrder_6305.patch, 
> startBundlesInOrder_6305_fix.patch
>
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6305:
--

Patch Info: Patch Available
   Summary: Start bundles in EBA according to bundle dependencies  (was: 
Start bundles in bundle dependency order)

> Start bundles in EBA according to bundle dependencies
> -
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: osgi-bundles
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: startBundlesInOrder_6305.patch
>
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6305:
--

Attachment: startBundlesInOrder_6305.patch

> Start bundles in EBA according to bundle dependencies
> -
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: osgi-bundles
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: startBundlesInOrder_6305.patch
>
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMO-6305) Start bundles in bundle dependency order

[Yi Xiao (Assigned) (JIRA)]

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

Yi Xiao reassigned GERONIMO-6305:
-

Assignee: Yi Xiao

> Start bundles in bundle dependency order
> 
>
> Key: GERONIMO-6305
> URL: https://issues.apache.org/jira/browse/GERONIMO-6305
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: osgi-bundles
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>
> As the bundles have the dependency, so need to provide the correct order when 
> they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6305) Start bundles in bundle dependency order

[Yi Xiao (Created) (JIRA)]

Start bundles in bundle dependency order


 Key: GERONIMO-6305
 URL: https://issues.apache.org/jira/browse/GERONIMO-6305
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: osgi-bundles
Reporter: Yi Xiao


As the bundles have the dependency, so need to provide the correct order when 
they start up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-786) Failed deployment of EAR causes consistent error messages in eclipse following on

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-786.
--

Resolution: Cannot Reproduce

> Failed deployment of EAR causes consistent error messages in eclipse 
> following on
> -
>
> Key: GERONIMODEVTOOLS-786
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-786
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0
> Environment: Eclipse indigo SR1 x64
> Sun JDK 1.6.0_29
> Ubuntu 10.04
>Reporter: Forrest Xia
>Assignee: Yi Xiao
> Attachments: DataCDInfo-JTA-ear-3.0.0.0.ear
>
>
> If you deployed the attached ear file into server via GEP, you will hit 
> consistent error messages when doing other deployment work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-786) Failed deployment of EAR causes consistent error messages in eclipse following on

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-786:
--

I could not reproduce the error, so close it. If any one happened to encounter 
the issue, please add the specified environment info and I will investigate!

> Failed deployment of EAR causes consistent error messages in eclipse 
> following on
> -
>
> Key: GERONIMODEVTOOLS-786
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-786
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0
> Environment: Eclipse indigo SR1 x64
> Sun JDK 1.6.0_29
> Ubuntu 10.04
>    Reporter: Forrest Xia
>Assignee: Yi Xiao
> Attachments: DataCDInfo-JTA-ear-3.0.0.0.ear
>
>
> If you deployed the attached ear file into server via GEP, you will hit 
> consistent error messages when doing other deployment work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMODEVTOOLS-786) Failed deployment of EAR causes consistent error messages in eclipse following on

[Yi Xiao (Assigned) (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-786:


Assignee: Yi Xiao

> Failed deployment of EAR causes consistent error messages in eclipse 
> following on
> -
>
> Key: GERONIMODEVTOOLS-786
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-786
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0
> Environment: Eclipse indigo SR1 x64
> Sun JDK 1.6.0_29
> Ubuntu 10.04
>Reporter: Forrest Xia
>Assignee: Yi Xiao
> Attachments: DataCDInfo-JTA-ear-3.0.0.0.ear
>
>
> If you deployed the attached ear file into server via GEP, you will hit 
> consistent error messages when doing other deployment work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMODEVTOOLS-788) The hot deploy of jsp and other static resource files do not work even under the development mode

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-788:
-

Fix Version/s: 3.0

> The hot deploy of jsp and other static resource files do not work even under 
> the development mode
> -
>
> Key: GERONIMODEVTOOLS-788
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0, 3.0-beta-1
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: hotdeploy
> Fix For: 3.0, 3.0-beta-2
>
>
> First need to set the server in development mode:
> 1 modify the config.xml:
>  name="org.apache.geronimo.configs/tomcat7-deployer/3.0-beta-2-SNAPSHOT/car">
>  
>  propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
>  
> http://java.sun.com/xml/ns/javaee"; 
> xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 
> 
> 
> org.apache.jasper.servlet.JspServlet
> 
> development
> true
> 
> 
> fork
> false
> 
> 
> logVerbosityLevel
> DEBUG
> 
> 
> xpoweredBy
> false
> 
> 
> engineOptionsClass
> 
> org.apache.geronimo.jasper.JspServletOptions
> 
> 
>  
>  
>  
> 
> ...
>  name="org.apache.geronimo.configs/jasper-deployer/3.0-beta-2-SNAPSHOT/car">   
>  
> 
>  propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
>  
> http://java.sun.com/xml/ns/javaee"; 
> xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 
> 
>  jsp
>  
> org.apache.jasper.servlet.JspServlet
>  
>  development
>  true
>  
>  
>  trimSpaces
>  false
>  
>  
>  fork
>  false
>  
>  
>  logVerbosityLevel
>  DEBUG
>  
>  
>  xpoweredBy
>  false
>  
>  
>  engineOptionsClass
>  
> org.apache.geronimo.jasper.JspServletOptions
>  
>  0
>  
>  
>  jsp
>  *.jsp
>  *.jspf
>  *.jspx
>  *.xsp
>  
>  
> 
> 
> 
> 2 set GERONIMO_OPTS
> set GERONIMO_OPTS=-Dorg.apache.geronimo.webapplication.stage=DEVELOPMENT
> Steps:
> 1. Install wep and OSGi tool in a clean eclipse
> 2. Install wasce
> 3. Import the attached sample eba into eclipse
> 4. Modify server configuration to enable hot swap, then run the sample on the 
> defined server
> 5. Open a browser to visit the jsp url
> 6. Update a jsp file and save it
> 7. Check if the jsp is updated by reloading the jsp url
> Symptom: you will see the jsp is not updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMODEVTOOLS-788) The hot deploy of jsp and other static resource files do not work even under the development mode

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-788:
--

Submitted at revision 1295380 and 1295382

> The hot deploy of jsp and other static resource files do not work even under 
> the development mode
> -
>
> Key: GERONIMODEVTOOLS-788
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0, 3.0-beta-1
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: hotdeploy
> Fix For: 3.0-beta-2
>
>
> First need to set the server in development mode:
> 1 modify the config.xml:
>  name="org.apache.geronimo.configs/tomcat7-deployer/3.0-beta-2-SNAPSHOT/car">
>  
>  propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
>  
> http://java.sun.com/xml/ns/javaee"; 
> xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 
> 
> 
> org.apache.jasper.servlet.JspServlet
> 
> development
> true
> 
> 
> fork
> false
> 
> 
> logVerbosityLevel
> DEBUG
> 
> 
> xpoweredBy
> false
> 
> 
> engineOptionsClass
> 
> org.apache.geronimo.jasper.JspServletOptions
> 
> 
>  
>  
>  
> 
> ...
>  name="org.apache.geronimo.configs/jasper-deployer/3.0-beta-2-SNAPSHOT/car">   
>  
> 
>  propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
>  
> http://java.sun.com/xml/ns/javaee"; 
> xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 
> 
>  jsp
>  
> org.apache.jasper.servlet.JspServlet
>  
>  development
>  true
>  
>  
>  trimSpaces
>  false
>  
>  
>  fork
>  false
>  
>  
>  logVerbosityLevel
>  DEBUG
>  
>  
>  xpoweredBy
>  false
>  
>  
>  engineOptionsClass
>  
> org.apache.geronimo.jasper.JspServletOptions
>  
>  0
>  
>  
>  jsp
>  *.jsp
>  *.jspf
>  *.jspx
>  *.xsp
>  
>  
> 
> 
> 
> 2 set GERONIMO_OPTS
> set GERONIMO_OPTS=-Dorg.apache.geronimo.webapplication.stage=DEVELOPMENT
> Steps:
> 1. Install wep and OSGi tool in a clean eclipse
> 2. Install wasce
> 3. Import the attached sample eba into eclipse
> 4. Modify server configuration to enable hot swap, then run the sample on the 
> defined server
> 5. Open a browser to visit the jsp url
> 6. Update a jsp file and save it
> 7. Check if the jsp is updated by reloading the jsp url
> Symptom: you will see the jsp is not updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-788) The hot deploy of jsp and other static resource files do not work even under the development mode

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-788.
--

Resolution: Fixed

> The hot deploy of jsp and other static resource files do not work even under 
> the development mode
> -
>
> Key: GERONIMODEVTOOLS-788
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0, 3.0-beta-1
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: hotdeploy
> Fix For: 3.0-beta-2
>
>
> First need to set the server in development mode:
> 1 modify the config.xml:
>  name="org.apache.geronimo.configs/tomcat7-deployer/3.0-beta-2-SNAPSHOT/car">
>  
>  propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
>  
> http://java.sun.com/xml/ns/javaee"; 
> xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 
> 
> 
> org.apache.jasper.servlet.JspServlet
> 
> development
> true
> 
> 
> fork
> false
> 
> 
> logVerbosityLevel
> DEBUG
> 
> 
> xpoweredBy
> false
> 
> 
> engineOptionsClass
> 
> org.apache.geronimo.jasper.JspServletOptions
> 
> 
>  
>  
>  
> 
> ...
>  name="org.apache.geronimo.configs/jasper-deployer/3.0-beta-2-SNAPSHOT/car">   
>  
> 
>  propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
>  
> http://java.sun.com/xml/ns/javaee"; 
> xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 
> 
>  jsp
>  
> org.apache.jasper.servlet.JspServlet
>  
>  development
>  true
>  
>  
>  trimSpaces
>  false
>  
>  
>  fork
>  false
>  
>  
>  logVerbosityLevel
>  DEBUG
>  
>  
>  xpoweredBy
>  false
>  
>  
>  engineOptionsClass
>  
> org.apache.geronimo.jasper.JspServletOptions
>  
>  0
>  
>  
>  jsp
>  *.jsp
>  *.jspf
>  *.jspx
>  *.xsp
>  
>  
> 
> 
> 
> 2 set GERONIMO_OPTS
> set GERONIMO_OPTS=-Dorg.apache.geronimo.webapplication.stage=DEVELOPMENT
> Steps:
> 1. Install wep and OSGi tool in a clean eclipse
> 2. Install wasce
> 3. Import the attached sample eba into eclipse
> 4. Modify server configuration to enable hot swap, then run the sample on the 
> defined server
> 5. Open a browser to visit the jsp url
> 6. Update a jsp file and save it
> 7. Check if the jsp is updated by reloading the jsp url
> Symptom: you will see the jsp is not updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMODEVTOOLS-788) The hot deploy of jsp and other static resource files do not work even under the development mode

[Yi Xiao (Created) (JIRA)]

The hot deploy of jsp and other static resource files do not work even under 
the development mode
-

 Key: GERONIMODEVTOOLS-788
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0-beta-1, 3.0
Reporter: Yi Xiao
Assignee: Yi Xiao
 Fix For: 3.0-beta-2


First need to set the server in development mode:
1 modify the config.xml:

 

 
http://java.sun.com/xml/ns/javaee"; 
xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 


org.apache.jasper.servlet.JspServlet

development
true


fork
false


logVerbosityLevel
DEBUG


xpoweredBy
false


engineOptionsClass

org.apache.geronimo.jasper.JspServletOptions


 
 
 

...



 
http://java.sun.com/xml/ns/javaee"; 
xmlns:web-app="http://java.sun.com/xml/ns/javaee";> 

 jsp
 
org.apache.jasper.servlet.JspServlet
 
 development
 true
 
 
 trimSpaces
 false
 
 
 fork
 false
 
 
 logVerbosityLevel
 DEBUG
 
 
 xpoweredBy
 false
 
 
 engineOptionsClass
 
org.apache.geronimo.jasper.JspServletOptions
 
 0
 
 
 jsp
 *.jsp
 *.jspf
 *.jspx
 *.xsp
 
 



2 set GERONIMO_OPTS
set GERONIMO_OPTS=-Dorg.apache.geronimo.webapplication.stage=DEVELOPMENT

Steps:
1. Install wep and OSGi tool in a clean eclipse
2. Install wasce
3. Import the attached sample eba into eclipse
4. Modify server configuration to enable hot swap, then run the sample on the 
defined server
5. Open a browser to visit the jsp url
6. Update a jsp file and save it
7. Check if the jsp is updated by reloading the jsp url

Symptom: you will see the jsp is not updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-749) Open the Geronimo plan, an error occurs when the server is started

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-749.
--

Resolution: Fixed

Also submit at trunk, revision: 1294449.

> Open the Geronimo plan, an error occurs when the server is started
> --
>
> Key: GERONIMODEVTOOLS-749
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-749
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.2, 3.0
> Environment: win7 64bit, eclipse3.6SR2, sun_jdk_1.6.25;
> winXP x86, eclipse3.6SR1, sun_jdk_1.6.24;
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 3.0-M2, 3.0
>
> Attachments: classCastException.patch, 
> classCastException_reOpen_749.patch
>
>
> 'Getting Dynamic Infomation from Server' has encountered a problem.
> An internal error occurred during: "Getting Dynamic Information from Server".
> java.lang.ClassCastException: org.apache.geronimo.gbean.AbstractName cannot 
> be cast to org.apache.geronimo.gbean.AbstractName
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.getByType(GeronimoServerInfo.java:395)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.updateDeployedEJBs(GeronimoServerInfo.java:161)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.access$1(GeronimoServerInfo.java:159)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo$1.run(GeronimoServerInfo.java:120)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.doAddPages()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-784) EBA Auto-redeployment failed if not enabling hot swap

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMODEVTOOLS-784.
--

Resolution: Fixed

It's fixed, As the GERONIMO-6288 is completed.

> EBA Auto-redeployment failed if not enabling hot swap
> -
>
> Key: GERONIMODEVTOOLS-784
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-2
> Environment: Eclipse indigo sr1
> sun java 6
> Geronimo 3.0-beta-2-snapshot
> GEP trunk
>Reporter: Forrest Xia
>Priority: Critical
> Attachments: 
> org.apache.aries.samples.blueprint.helloworld.assembly_3.0.0.0.eba
>
>
> Steps to reproduce this issue:
> 1. Having these stuffs installed: eclipse indigo sr1, geronimo web profile 
> assembly 3.0-beta-2-snapshot build, GEP trunk build, IBM OSGi free tool
> 2. Import the attached EBA application into eclipse
> 3. Deploy this application into the server
> 4. Update the wab module to add a new jsp file
> 5. An auto-redeployment will happen to redeploy the changed project into the 
> server, however, an error message shows as following:
> Module 
> application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba
>  already exists in the server.  Try to undeploy it first or use the redeploy 
> command.
> org.apache.geronimo.common.DeploymentException: Module 
> application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba
>  already exists in the server.  Try to undeploy it first or use the redeploy 
> command.
>   at 
> org.apache.geronimo.deployment.Deployer.getConfigID(Deployer.java:320)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
>   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
>   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:597)
>   at 
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
>   at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344)
> ...
> If checked all options in "Publish Advanced" tab, then no such exception. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6288) When deploy a EBA with long symbolicname, showing an error Msg "xxxx already existes in the server"

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6288:
---

Submitted at revision: 1294060 at trunk; 1294061 at 3.0-beta

> When deploy a EBA with long symbolicname, showing an error Msg " already 
> existes in the server" 
> 
>
> Key: GERONIMO-6288
> URL: https://issues.apache.org/jira/browse/GERONIMO-6288
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0, 3.0-beta-1
>        Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: EBA, deployment
> Fix For: 3.0-beta-2
>
>
> see the jira: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMO-6288) When deploy a EBA with long symbolicname, showing an error Msg "xxxx already existes in the server"

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMO-6288.
---

Resolution: Fixed

> When deploy a EBA with long symbolicname, showing an error Msg " already 
> existes in the server" 
> 
>
> Key: GERONIMO-6288
> URL: https://issues.apache.org/jira/browse/GERONIMO-6288
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0, 3.0-beta-1
>        Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: EBA, deployment
> Fix For: 3.0-beta-2
>
>
> see the jira: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMO-6224) NPE while accessing the system modules portlet

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMO-6224.
---

   Resolution: Fixed
Fix Version/s: 3.0-beta-2

> NPE while accessing the system modules portlet
> --
>
> Key: GERONIMO-6224
> URL: https://issues.apache.org/jira/browse/GERONIMO-6224
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Yi Xiao
> Fix For: 3.0-beta-2
>
> Attachments: NPEWhileAccessingTheSystemModulesPorlet_6224.patch
>
>
> When I tried to stop "openejb-deployer", I got the following error. And every 
> time I visit "System Modules" page, I got the same error
> There may be problems in the kernel, while I think that the portlet should be 
> more tolerant for those runtime exception.
> java.lang.NullPointerException
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:251)
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:243)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:863)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:839)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.unloadModule(ConfigManagerPortlet.java:447)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:341)
>at 
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
>at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
>at 
> org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
>at 
> org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
>at 
> org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
>at 
> org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117)
>at 
> org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157)
>at 
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165)
>at 
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:108)
>at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catal

[jira] [Resolved] (GERONIMO-6260) Could not redeploy EJB module

[Yi Xiao (Resolved) (JIRA)]

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

Yi Xiao resolved GERONIMO-6260.
---

   Resolution: Fixed
Fix Version/s: 3.0-beta-2

> Could not redeploy EJB module
> -
>
> Key: GERONIMO-6260
> URL: https://issues.apache.org/jira/browse/GERONIMO-6260
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0-beta-1
> Environment: win7 64bit, oracle jdk1.6.0_25
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: ejb, redeploy
> Fix For: 3.0-beta-2
>
> Attachments: couldNotRedployEJB_6260.patch
>
>
> ERROR [DeploymentPortlet] Unable to identify modules to replace. Check if it 
> has already been stopped or undeployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6260) Could not redeploy EJB module

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6260:
---

Thanks Ivan, I commit the code according to your suggestion.
Committed code in revision: 1294052 at trunk, revision: 1294055 at 3.0-beta

> Could not redeploy EJB module
> -
>
> Key: GERONIMO-6260
> URL: https://issues.apache.org/jira/browse/GERONIMO-6260
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0-beta-1
> Environment: win7 64bit, oracle jdk1.6.0_25
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: ejb, redeploy
> Attachments: couldNotRedployEJB_6260.patch
>
>
> ERROR [DeploymentPortlet] Unable to identify modules to replace. Check if it 
> has already been stopped or undeployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6288) When deploy a EBA with long symbolicname, showing an error Msg "xxxx already existes in the server"

[Yi Xiao (Created) (JIRA)]

When deploy a EBA with long symbolicname, showing an error Msg " already 
existes in the server" 


 Key: GERONIMO-6288
 URL: https://issues.apache.org/jira/browse/GERONIMO-6288
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: deployment
Affects Versions: 3.0-beta-1, 3.0
Reporter: Yi Xiao
Assignee: Yi Xiao
 Fix For: 3.0-beta-2


see the jira: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6224) NPE while accessing the system modules portlet

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6224:
---

committed at revision: 1294046 in trunk, revision: 1294047 in 3.0-beta

> NPE while accessing the system modules portlet
> --
>
> Key: GERONIMO-6224
> URL: https://issues.apache.org/jira/browse/GERONIMO-6224
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Yi Xiao
> Attachments: NPEWhileAccessingTheSystemModulesPorlet_6224.patch
>
>
> When I tried to stop "openejb-deployer", I got the following error. And every 
> time I visit "System Modules" page, I got the same error
> There may be problems in the kernel, while I think that the portlet should be 
> more tolerant for those runtime exception.
> java.lang.NullPointerException
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:251)
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:243)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:863)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:839)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.unloadModule(ConfigManagerPortlet.java:447)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:341)
>at 
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
>at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
>at 
> org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
>at 
> org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
>at 
> org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
>at 
> org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117)
>at 
> org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157)
>at 
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165)
>at 
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:108)
>at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(

[jira] [Commented] (GERONIMODEVTOOLS-749) Open the Geronimo plan, an error occurs when the server is started

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMODEVTOOLS-749:
--

Committed at revision: 1294026.

> Open the Geronimo plan, an error occurs when the server is started
> --
>
> Key: GERONIMODEVTOOLS-749
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-749
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.2, 3.0
> Environment: win7 64bit, eclipse3.6SR2, sun_jdk_1.6.25;
> winXP x86, eclipse3.6SR1, sun_jdk_1.6.24;
>    Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 3.0-M2, 3.0
>
> Attachments: classCastException.patch, 
> classCastException_reOpen_749.patch
>
>
> 'Getting Dynamic Infomation from Server' has encountered a problem.
> An internal error occurred during: "Getting Dynamic Information from Server".
> java.lang.ClassCastException: org.apache.geronimo.gbean.AbstractName cannot 
> be cast to org.apache.geronimo.gbean.AbstractName
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.getByType(GeronimoServerInfo.java:395)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.updateDeployedEJBs(GeronimoServerInfo.java:161)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.access$1(GeronimoServerInfo.java:159)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo$1.run(GeronimoServerInfo.java:120)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.doAddPages()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6270) Re-enable multiple instances support in one installation

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6270:
---

Hi Russell,
Your comments are reasonable, and need more discussion. I think if we indeed 
add the GERONIMO_SERVER, it will also affect GERONIMO-6175, GERONIMO-6174, so 
we'd better open an task to track the changes.

> Re-enable multiple instances support in one installation
> 
>
> Key: GERONIMO-6270
> URL: https://issues.apache.org/jira/browse/GERONIMO-6270
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 3.0-beta-1
>Reporter: Forrest Xia
>Assignee: Yi Xiao
>
> We need to investigate how to re-enable the multiple instances support in one 
> installation.
> Refer to 
> https://issues.apache.org/jira/browse/GERONIMO-6175
> https://issues.apache.org/jira/browse/GERONIMO-6174
> https://issues.apache.org/jira/browse/GERONIMO-5987

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6270) Re-enable multiple instances support in one installation

[Yi Xiao (Commented) (JIRA)]

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

Yi Xiao commented on GERONIMO-6270:
---

There are two problems when enable multiple instance:
(1)When two or more server instances start up, the activeMQ will try to lock 
the var/activemq directory, we can specify the activemq.data in 
var/config/config-subsitutions.properties to resolve it.
(2)When deploy a application in a new repository besides the default one using 
deploy.bat -port RMI_port deploy --targets %other_repo% path/to/application, 
the application could not be started by the "mvn:groupid/artifactId/..." could 
not be resolved error. I think it's the URL handler couldn't resolve the new 
repo, still under investigation.


> Re-enable multiple instances support in one installation
> 
>
> Key: GERONIMO-6270
> URL: https://issues.apache.org/jira/browse/GERONIMO-6270
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 3.0-beta-1
>        Reporter: Forrest Xia
>Assignee: Yi Xiao
>
> We need to investigate how to re-enable the multiple instances support in one 
> installation.
> Refer to 
> https://issues.apache.org/jira/browse/GERONIMO-6175
> https://issues.apache.org/jira/browse/GERONIMO-6174
> https://issues.apache.org/jira/browse/GERONIMO-5987

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (GERONIMO-6270) Re-enable multiple instances support in one installation

[Yi Xiao (Assigned) (JIRA)]

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

Yi Xiao reassigned GERONIMO-6270:
-

Assignee: Yi Xiao

> Re-enable multiple instances support in one installation
> 
>
> Key: GERONIMO-6270
> URL: https://issues.apache.org/jira/browse/GERONIMO-6270
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 3.0-beta-1
>Reporter: Forrest Xia
>Assignee: Yi Xiao
>
> We need to investigate how to re-enable the multiple instances support in one 
> installation.
> Refer to 
> https://issues.apache.org/jira/browse/GERONIMO-6175
> https://issues.apache.org/jira/browse/GERONIMO-6174
> https://issues.apache.org/jira/browse/GERONIMO-5987

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMODEVTOOLS-749) Open the Geronimo plan, an error occurs when the server is started

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-749:
-

Attachment: classCastException_reOpen_749.patch

After investigating, there are two issues:
(1) When load the classes, JMX will use a default classloader to do, we should 
set the right classloader first.
(2) Some ClassCastException could be ignored.

> Open the Geronimo plan, an error occurs when the server is started
> --
>
> Key: GERONIMODEVTOOLS-749
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-749
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.2, 3.0
> Environment: win7 64bit, eclipse3.6SR2, sun_jdk_1.6.25;
> winXP x86, eclipse3.6SR1, sun_jdk_1.6.24;
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 3.0-M2, 3.0
>
> Attachments: classCastException.patch, 
> classCastException_reOpen_749.patch
>
>
> 'Getting Dynamic Infomation from Server' has encountered a problem.
> An internal error occurred during: "Getting Dynamic Information from Server".
> java.lang.ClassCastException: org.apache.geronimo.gbean.AbstractName cannot 
> be cast to org.apache.geronimo.gbean.AbstractName
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.getByType(GeronimoServerInfo.java:395)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.updateDeployedEJBs(GeronimoServerInfo.java:161)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.access$1(GeronimoServerInfo.java:159)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo$1.run(GeronimoServerInfo.java:120)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.doAddPages()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6250) Allow definition of maxParameterCount in gbean

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6250:
--

Attachment: AllowDefinitionOfMaxParameterCountInGbean_For22_6250.patch
AllowDefinitionOfMaxParameterCountInGbean_For30_6250.patch

The patches are created according to the 2.1's, the complication is passed.

> Allow definition of maxParameterCount in gbean
> --
>
> Key: GERONIMO-6250
> URL: https://issues.apache.org/jira/browse/GERONIMO-6250
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.1.8
>Reporter: Forrest Xia
>Assignee: Yi Xiao
> Fix For: 2.1.9
>
> Attachments: 
> AllowDefinitionOfMaxParameterCountInGbean_For22_6250.patch, 
> AllowDefinitionOfMaxParameterCountInGbean_For30_6250.patch
>
>
> maxParameterCount is a new parameter of Tomcat since 6.0.35, we need to 
> update the gbean to allow its definition in Geronimo way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMODEVTOOLS-779) Release GEP2.1.8

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-779:
-

Attachment: releaseGep218_changeVersion_779_1.patch

Change the version of manifest.mf's content and the test pom files

> Release GEP2.1.8
> 
>
> Key: GERONIMODEVTOOLS-779
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-779
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.1.8
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: releaseGep218_779.patch, releaseGep218_779_1.patch, 
> releaseGep218_changeVersion_779_1.patch, releaseNotes_779.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6224) NPE while accessing the system modules portlet

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6224:
--

Patch Info: Patch Available

> NPE while accessing the system modules portlet
> --
>
> Key: GERONIMO-6224
> URL: https://issues.apache.org/jira/browse/GERONIMO-6224
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Yi Xiao
> Attachments: NPEWhileAccessingTheSystemModulesPorlet_6224.patch
>
>
> When I tried to stop "openejb-deployer", I got the following error. And every 
> time I visit "System Modules" page, I got the same error
> There may be problems in the kernel, while I think that the portlet should be 
> more tolerant for those runtime exception.
> java.lang.NullPointerException
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:251)
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:243)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:863)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:839)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.unloadModule(ConfigManagerPortlet.java:447)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:341)
>at 
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
>at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
>at 
> org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
>at 
> org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
>at 
> org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
>at 
> org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117)
>at 
> org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157)
>at 
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165)
>at 
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:108)
>at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatch

[jira] [Updated] (GERONIMODEVTOOLS-781) slf4j version conflict

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-781:
-

Patch Info: Patch Available

> slf4j version conflict
> --
>
> Key: GERONIMODEVTOOLS-781
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-781
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Yi Xiao
> Attachments: slf4jVersionConflict_781.patch
>
>
> I tired installing "Maven Integration for Eclipse" plugin via Eclipse 
> Marketplace on Eclipse 3.6.2 Java EE with the GEP plugin and Rational OSGI 
> tooling installed. The Maven plugin installed fine but it failed to start. I 
> tracked down the problem to a conflict in org.slf4j APIs. The GEP runtime 
> plugins export the org.slf4j.* APIs with the given Geronimo version. For 
> example, the GEP v3 runtime plugin exports org.slf4j.api with version 3. That 
> confuses other plugins in Eclipse and causes the Maven plugin not to start. 
> I'm not sure 1) why we export the org.slf4j.* API out of GEP plugins in the 
> first place and 2) if we need to export them why are we exporting them with 
> the Geronimo version instead of the actual SLF4J version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6260) Could not redeploy EJB module

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6260:
--

Patch Info: Patch Available

> Could not redeploy EJB module
> -
>
> Key: GERONIMO-6260
> URL: https://issues.apache.org/jira/browse/GERONIMO-6260
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0-beta-1
> Environment: win7 64bit, oracle jdk1.6.0_25
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: ejb, redeploy
> Attachments: couldNotRedployEJB_6260.patch
>
>
> ERROR [DeploymentPortlet] Unable to identify modules to replace. Check if it 
> has already been stopped or undeployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMODEVTOOLS-781) slf4j version conflict

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-781:
-

Attachment: slf4jVersionConflict_781.patch

I remove all the org.self4j.* packages from manifest.mf, and test the scenario 
in description, also have some deploy/remove application tests in the new gep 
build, it works fine.

> slf4j version conflict
> --
>
> Key: GERONIMODEVTOOLS-781
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-781
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Yi Xiao
> Attachments: slf4jVersionConflict_781.patch
>
>
> I tired installing "Maven Integration for Eclipse" plugin via Eclipse 
> Marketplace on Eclipse 3.6.2 Java EE with the GEP plugin and Rational OSGI 
> tooling installed. The Maven plugin installed fine but it failed to start. I 
> tracked down the problem to a conflict in org.slf4j APIs. The GEP runtime 
> plugins export the org.slf4j.* APIs with the given Geronimo version. For 
> example, the GEP v3 runtime plugin exports org.slf4j.api with version 3. That 
> confuses other plugins in Eclipse and causes the Maven plugin not to start. 
> I'm not sure 1) why we export the org.slf4j.* API out of GEP plugins in the 
> first place and 2) if we need to export them why are we exporting them with 
> the Geronimo version instead of the actual SLF4J version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6260) Could not redeploy EJB module

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-6260:
--

Attachment: couldNotRedployEJB_6260.patch

The root cause is that we should use openejb-jar.xml, but the ejb-jar.xml 
exists in org.apache.geronimo.deployment.plugin.ConfigIDExtractor. Fix it now.

> Could not redeploy EJB module
> -
>
> Key: GERONIMO-6260
> URL: https://issues.apache.org/jira/browse/GERONIMO-6260
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 3.0-beta-1
> Environment: win7 64bit, oracle jdk1.6.0_25
>Reporter: Yi Xiao
>Assignee: Yi Xiao
>  Labels: ejb, redeploy
> Attachments: couldNotRedployEJB_6260.patch
>
>
> ERROR [DeploymentPortlet] Unable to identify modules to replace. Check if it 
> has already been stopped or undeployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6260) Could not redeploy EJB module

[Yi Xiao (Created) (JIRA)]

Could not redeploy EJB module
-

 Key: GERONIMO-6260
 URL: https://issues.apache.org/jira/browse/GERONIMO-6260
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: deployment
Affects Versions: 3.0-beta-1
 Environment: win7 64bit, oracle jdk1.6.0_25
Reporter: Yi Xiao
Assignee: Yi Xiao


ERROR [DeploymentPortlet] Unable to identify modules to replace. Check if it 
has already been stopped or undeployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: PASS! [Vote] Geronimo Eclipse Plugin (GEP) 2.1.8 RC1

[Yi Xiao]

You are welcome[?]

On Thu, Jan 12, 2012 at 9:53 AM, Forrest Xia  wrote:

> Vote results:
>
> +1 votes: Forrest, Shawn, Ivan, Kevan, Rex, Viola
> No -1 and 0 votes.
>
> I will push the release to maven public repo soon.
>
> Thanks for Yi Xiao's help and everyone review!
>
> On Thu, Jan 12, 2012 at 9:00 AM, Rex Wang  wrote:
>
>> +1, Thanks Yi Xiao and Forrest!
>>
>>
>> 2012/1/6 Forrest Xia 
>>
>>> Hi devs,
>>>
>>> With great help of Yi Xiao, I made a stage repo for GEP 2.1.8 release
>>> vote.
>>>
>>> So everyone, please help to review and vote on the release of Geronimo
>>> Eclipse Plugin (GEP) 2.1.8 RC1 from now on.
>>>
>>> GEP 2.1.8 supports Geronimo server 2.1.8 and Eclipse Indigo SR1(3.7.1).
>>>
>>> The source code zip is here:
>>> *
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.tar.gz
>>> *
>>> *
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.zip
>>> *
>>>
>>> The tag is here:
>>>
>>> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-2.1.8
>>>
>>> The deployable zip file is here:
>>>
>>> http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-deployable.zip
>>>
>>> The update site zip file is here:
>>>
>>> http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-updatesite.zip
>>>
>>> If you would like to review and/or comment on the release notes, you can
>>> find it here:
>>>
>>> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-2.1.8.txt
>>>
>>> Create a Staging Site that can be used to test the update manager
>>> functions of  Eclipse (Indigo and helios):
>>> http://people.apache.org/builds/geronimo/eclipse/updates/
>>>
>>> The vote will be open for the 72-hour minimum.
>>>
>>> [  ] +1 about time to push this out the door
>>> [  ]  0 no opinion
>>> [  ] -1 not this one  (please explain why)
>>>
>>>
>>> --
>>> Thanks!
>>>
>>> Regards, Forrest
>>>
>>>
>>
>>
>> --
>> Lei Wang (Rex)
>> rwonly AT apache.org
>>
>
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Best regards!


 John Xiao
<<328.png>>

[jira] [Assigned] (GERONIMODEVTOOLS-781) slf4j version conflict

[Yi Xiao (Assigned) (JIRA)]

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

Yi Xiao reassigned GERONIMODEVTOOLS-781:


Assignee: Yi Xiao

> slf4j version conflict
> --
>
> Key: GERONIMODEVTOOLS-781
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-781
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0-beta-1
>Reporter: Jarek Gawor
>Assignee: Yi Xiao
>
> I tired installing "Maven Integration for Eclipse" plugin via Eclipse 
> Marketplace on Eclipse 3.6.2 Java EE with the GEP plugin and Rational OSGI 
> tooling installed. The Maven plugin installed fine but it failed to start. I 
> tracked down the problem to a conflict in org.slf4j APIs. The GEP runtime 
> plugins export the org.slf4j.* APIs with the given Geronimo version. For 
> example, the GEP v3 runtime plugin exports org.slf4j.api with version 3. That 
> confuses other plugins in Eclipse and causes the Maven plugin not to start. 
> I'm not sure 1) why we export the org.slf4j.* API out of GEP plugins in the 
> first place and 2) if we need to export them why are we exporting them with 
> the Geronimo version instead of the actual SLF4J version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (GERONIMODEVTOOLS-749) Open the Geronimo plan, an error occurs when the server is started

[Yi Xiao (Reopened) (JIRA)]

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

Yi Xiao reopened GERONIMODEVTOOLS-749:
--


It needs more investigation to solve the problem.

> Open the Geronimo plan, an error occurs when the server is started
> --
>
> Key: GERONIMODEVTOOLS-749
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-749
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.2, 3.0
> Environment: win7 64bit, eclipse3.6SR2, sun_jdk_1.6.25;
> winXP x86, eclipse3.6SR1, sun_jdk_1.6.24;
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 3.0-M2, 3.0
>
> Attachments: classCastException.patch
>
>
> 'Getting Dynamic Infomation from Server' has encountered a problem.
> An internal error occurred during: "Getting Dynamic Information from Server".
> java.lang.ClassCastException: org.apache.geronimo.gbean.AbstractName cannot 
> be cast to org.apache.geronimo.gbean.AbstractName
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.getByType(GeronimoServerInfo.java:395)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.updateDeployedEJBs(GeronimoServerInfo.java:161)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo.access$1(GeronimoServerInfo.java:159)
>   at 
> org.apache.geronimo.st.v30.core.GeronimoServerInfo$1.run(GeronimoServerInfo.java:120)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.doAddPages()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-5956) issues when deploy a standalone ejb web services

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMO-5956:
--

Attachment: NCFWhenStandloneEjbWebServiceDeploy_5956.patch

#2 is the default bundle-classpath is overwrite by WsdlGenerator. the patch is 
available.

> issues when deploy a standalone ejb web services
> 
>
> Key: GERONIMO-5956
> URL: https://issues.apache.org/jira/browse/GERONIMO-5956
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 3.0
>Reporter: Rex Wang
>Assignee: Yi Xiao
> Fix For: 3.0
>
> Attachments: HelloRex_EJB.jar, 
> NCFWhenStandloneEjbWebServiceDeploy_5956.patch
>
>
> 1. the ejb base-dir is not add to the wsdl generator tool's class path, so 
> the an CNF exception will be thrown.
> 2. after resovled #1, the ejb can be deployed successfully, but start failed 
> with the following exceptions:
> Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: 
> Configuration default/Hello_Hello_ejb/1-default/car failed to start due to 
> the following reasons:
>   The service 
> J2EEApplication=null,j2eeType=EJBModule,name=default/Hello_Hello_ejb/1-default/car
>  did not start because Creating application failed: 
> D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar:
>  Error building bean 'Hello'.  Exception: class 
> org.apache.openejb.OpenEJBException: Error while loading bean class 
> com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate 
> the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]:
>  Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. 
> Received message: Cannot locate the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]
> org.apache.openejb.OpenEJBException: Creating application failed: 
> D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar:
>  Error building bean 'Hello'.  Exception: class 
> org.apache.openejb.OpenEJBException: Error while loading bean class 
> com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate 
> the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]:
>  Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. 
> Received message: Cannot locate the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]
> at 
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:784)
> at 
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:457)
> at 
> org.apache.geronimo.openejb.OpenEjbSystemGBean.createApplication(OpenEjbSystemGBean.java:438)
> at 
> org.apache.geronimo.openejb.EjbModuleImpl.doStart(EjbModuleImpl.java:182)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546)
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175)
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningE

[jira] [Assigned] (GERONIMO-6224) NPE while accessing the system modules portlet

[Yi Xiao (Assigned) (JIRA)]

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

Yi Xiao reassigned GERONIMO-6224:
-

Assignee: Yi Xiao

> NPE while accessing the system modules portlet
> --
>
> Key: GERONIMO-6224
> URL: https://issues.apache.org/jira/browse/GERONIMO-6224
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Yi Xiao
> Attachments: NPEWhileAccessingTheSystemModulesPorlet_6224.patch
>
>
> When I tried to stop "openejb-deployer", I got the following error. And every 
> time I visit "System Modules" page, I got the same error
> There may be problems in the kernel, while I think that the portlet should be 
> more tolerant for those runtime exception.
> java.lang.NullPointerException
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stopRecursive(KernelConfigurationManager.java:251)
>at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.stop(KernelConfigurationManager.java:243)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:863)
>at 
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadConfiguration(SimpleConfigurationManager.java:839)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.unloadModule(ConfigManagerPortlet.java:447)
>at 
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:341)
>at 
> javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
>at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
>at 
> org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
>at 
> org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
>at 
> org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
>at 
> org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
>at 
> org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
>at 
> org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117)
>at 
> org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157)
>at 
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165)
>at 
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:108)
>at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
>at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593)
>at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatch

[jira] [Assigned] (GERONIMO-5956) issues when deploy a standalone ejb web services

[Yi Xiao (Assigned) (JIRA)]

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

Yi Xiao reassigned GERONIMO-5956:
-

Assignee: Yi Xiao  (was: Rex Wang)

> issues when deploy a standalone ejb web services
> 
>
> Key: GERONIMO-5956
> URL: https://issues.apache.org/jira/browse/GERONIMO-5956
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: webservices
>Affects Versions: 3.0
>Reporter: Rex Wang
>Assignee: Yi Xiao
> Fix For: 3.0
>
> Attachments: HelloRex_EJB.jar
>
>
> 1. the ejb base-dir is not add to the wsdl generator tool's class path, so 
> the an CNF exception will be thrown.
> 2. after resovled #1, the ejb can be deployed successfully, but start failed 
> with the following exceptions:
> Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: 
> Configuration default/Hello_Hello_ejb/1-default/car failed to start due to 
> the following reasons:
>   The service 
> J2EEApplication=null,j2eeType=EJBModule,name=default/Hello_Hello_ejb/1-default/car
>  did not start because Creating application failed: 
> D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar:
>  Error building bean 'Hello'.  Exception: class 
> org.apache.openejb.OpenEJBException: Error while loading bean class 
> com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate 
> the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]:
>  Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. 
> Received message: Cannot locate the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]
> org.apache.openejb.OpenEJBException: Creating application failed: 
> D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar:
>  Error building bean 'Hello'.  Exception: class 
> org.apache.openejb.OpenEJBException: Error while loading bean class 
> com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate 
> the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]:
>  Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. 
> Received message: Cannot locate the class com.abc.Hello from the codebase 
> [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]
> at 
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:784)
> at 
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:457)
> at 
> org.apache.geronimo.openejb.OpenEjbSystemGBean.createApplication(OpenEjbSystemGBean.java:438)
> at 
> org.apache.geronimo.openejb.EjbModuleImpl.doStart(EjbModuleImpl.java:182)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546)
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
> at 
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175)
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
> at 
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.att

Re: [Vote] Geronimo Eclipse Plugin (GEP) 2.1.8 RC1

[Yi Xiao]

I do the work below to verify the release:
(1) Check out the code and build it on Ubuntu-32bit, winxp-32bit and
win7-64bit, all pass successfully.
(2) Pass rat check.
(3) Install from on-line update site, start/stop server, deploy web
applications into server through it, works fine.

so my +1

On Fri, Jan 6, 2012 at 3:44 PM, Forrest Xia  wrote:

> Hi devs,
>
> With great help of Yi Xiao, I made a stage repo for GEP 2.1.8 release
> vote.
>
> So everyone, please help to review and vote on the release of Geronimo
> Eclipse Plugin (GEP) 2.1.8 RC1 from now on.
>
> GEP 2.1.8 supports Geronimo server 2.1.8 and Eclipse Indigo SR1(3.7.1).
>
> The source code zip is here:
> *
> https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.tar.gz
> *
> *
> https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.zip
> *
>
> The tag is here:
>
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-2.1.8
>
> The deployable zip file is here:
>
> http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-deployable.zip
>
> The update site zip file is here:
>
> http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-updatesite.zip
>
> If you would like to review and/or comment on the release notes, you can
> find it here:
>
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-2.1.8.txt
>
> Create a Staging Site that can be used to test the update manager
> functions of  Eclipse (Indigo and helios):
> http://people.apache.org/builds/geronimo/eclipse/updates/
>
> The vote will be open for the 72-hour minimum.
>
> [  ] +1 about time to push this out the door
> [  ]  0 no opinion
> [  ] -1 not this one  (please explain why)
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Best regards!


 John Xiao

[jira] [Updated] (GERONIMODEVTOOLS-779) Release GEP2.1.8

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-779:
-

Attachment: releaseGep218_779_1.patch

the new patch for release, it contains the 778's patch and also some other 
version changes.

> Release GEP2.1.8
> 
>
> Key: GERONIMODEVTOOLS-779
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-779
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.1.8
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: releaseGep218_779.patch, releaseGep218_779_1.patch, 
> releaseNotes_779.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMODEVTOOLS-779) Release GEP2.1.8

[Yi Xiao (Updated) (JIRA)]

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

Yi Xiao updated GERONIMODEVTOOLS-779:
-

Attachment: releaseNotes_779.patch

> Release GEP2.1.8
> 
>
> Key: GERONIMODEVTOOLS-779
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-779
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.1.8
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Attachments: releaseGep218_779.patch, releaseNotes_779.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira