Re: GEP and Geronimo Source Archive

[Jack Cai]

Is it for debugging purpose? So that people can step in Geronimo source
code... My guess.

-Jack

2008/8/21 Ted Kirby <[EMAIL PROTECTED]>

> Now that you mention it...  I have never done anything with this
> screen.  I am not even sure what it is for.  Can we remove this screen
> from the define server dialog?
>
> Ted
>
> On Wed, Aug 20, 2008 at 5:53 PM, Jacek Laskowski <[EMAIL PROTECTED]>
> wrote:
> > Hi,
> >
> > I wonder what I should point the Geronimo Source Archive field when I
> > have the Geronimo sources checked? What about people without the
> > sources locally? What value(s) do people use for the field? Is it
> > described somewhere?
> >
> > Jacek
> >
> > --
> > Jacek Laskowski
> > Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
> >
>

[jira] Commented: (GERONIMODEVTOOLS-492) GEP v2.1.1 installation error in eclipse Ganymede JEE package

[Forrest Xia (JIRA)]

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

Forrest Xia commented on GERONIMODEVTOOLS-492:
--

Agreed to close it, thanks for pointing this out :)

> GEP v2.1.1 installation error in eclipse Ganymede JEE package
> -
>
> Key: GERONIMODEVTOOLS-492
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-492
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.1
> Environment: OS: Windows XP SP2 and Ubuntu 8.04
> Eclipse: Eclipse Ganymede JEE package, based on Version: 3.4.0 Build id: 
> I20080617-2000
> JDK: IBM SDK 5 sr6b
>Reporter: Forrest Xia
>Assignee: Ted Kirby
> Fix For: 2.1.2
>
>
> Steps:
> 1. Download and lauch eclipse ganymede
> 2. click "Software Updates..."->"Available Software" to add a site point to 
> http://www.apache.org/dist/geronimo/eclipse/updates
> 3. Choose "Geronimo v2.1 Server Adapter" to install
> Symptom:
> An install error shows up as follows:
> Cannot complete the request.  See the details.
> Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.apache.geronimo.feature.feature.group/[2.1.1,2.1.1]

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

Re: GEP and Geronimo Source Archive

[Ted Kirby]

Now that you mention it...  I have never done anything with this
screen.  I am not even sure what it is for.  Can we remove this screen
from the define server dialog?

Ted

On Wed, Aug 20, 2008 at 5:53 PM, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I wonder what I should point the Geronimo Source Archive field when I
> have the Geronimo sources checked? What about people without the
> sources locally? What value(s) do people use for the field? Is it
> described somewhere?
>
> Jacek
>
> --
> Jacek Laskowski
> Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
>

[jira] Commented: (GERONIMODEVTOOLS-493) Update failure when upgrading GEP 2.1.1 to 2.1.2 using staging site

[Ted Kirby (JIRA)]

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

Ted Kirby commented on GERONIMODEVTOOLS-493:


1. That is an old staging site.  The staging site for the current vote on GEP 
2.1.2 is http://people.apache.org/~mcconne/releases/2.1.2/RC2/staging_site/

2. As far as I know, we have never supported an update scenario.  We only 
support a new install scenario.  I will let Tim comment on this, and suggest 
further action.

> Update failure when upgrading GEP 2.1.1 to 2.1.2 using staging site
> ---
>
> Key: GERONIMODEVTOOLS-493
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-493
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.1
> Environment: Windows XP SP2
> Eclipse Ganymede JEE package
> IBM SDK 5 SR6b
>Reporter: Forrest Xia
>Assignee: Tim McConnell
>
> Steps:
> 1. Install GEP 2.1.1 through "Download additional server adapters"
> 2. Configure the staging site point to 
> "http://people.apache.org/~tkirby/releases/2.1.2/RC1/staging_site/eclipse/updates/";
> 3. Click "Software Updates..."->"Installed Software"->"Geronimo v2.1 Server 
> Adapter", then click "Update..." button.
> Symptom:
> The P2 update program recognized new version 2.1.2 from the configured 
> staging site, but the size and detail info is missing, anyway click Finish 
> button to start upgrading. After a while, an error shows up as follows:
> "An error occurred during provisioning.
>   Failed to prepare partial IU: [R]org.apache.geronimo.st.schemas 2.1.2.
> "
> Considering GEP community will face upgrading existing GEP 2.1.1 to 2.1.2, so 
> the scenario described above should be valid :)

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

[jira] Closed: (GERONIMODEVTOOLS-492) GEP v2.1.1 installation error in eclipse Ganymede JEE package

[Ted Kirby (JIRA)]

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

Ted Kirby closed GERONIMODEVTOOLS-492.
--

   Resolution: Invalid
Fix Version/s: 2.1.2
 Assignee: Ted Kirby  (was: Tim McConnell)

Ganymede support was not added until GEP 2.1.2 in GERONIMODEVTOOLS-402.

> GEP v2.1.1 installation error in eclipse Ganymede JEE package
> -
>
> Key: GERONIMODEVTOOLS-492
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-492
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.1
> Environment: OS: Windows XP SP2 and Ubuntu 8.04
> Eclipse: Eclipse Ganymede JEE package, based on Version: 3.4.0 Build id: 
> I20080617-2000
> JDK: IBM SDK 5 sr6b
>Reporter: Forrest Xia
>Assignee: Ted Kirby
> Fix For: 2.1.2
>
>
> Steps:
> 1. Download and lauch eclipse ganymede
> 2. click "Software Updates..."->"Available Software" to add a site point to 
> http://www.apache.org/dist/geronimo/eclipse/updates
> 3. Choose "Geronimo v2.1 Server Adapter" to install
> Symptom:
> An install error shows up as follows:
> Cannot complete the request.  See the details.
> Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
> Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
> requiredCapability: 
> org.eclipse.equinox.p2.iu/org.apache.geronimo.feature.feature.group/[2.1.1,2.1.1]

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

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[Lin Sun]

+1.  Tested with Eclipse 3.4.

I did notice one prob.  I installed the Geronimo WTP server adapter
for 2.1.2 first via update site.  Then I went back to Eclipse update
manager to select Apache Geronimo Runtimes, but the Install button is
greyed out.  Does this mean we don't allow users to install Geronimo
runtimes from update manager now?   If so, we should take it off the
list.  I remember we had discussions on not allowing users to download
and install geronimo server from GEP, but don't recall any discussion
on taking it off eclipse update manager.

Lin

On Wed, Aug 20, 2008 at 9:15 PM, YunFeng Ma <[EMAIL PROTECTED]> wrote:
> +1
>
> -- YunFeng
>
> Tim McConnell wrote:
>
> Hi everyone, Please review and vote on the maintenance release of the
> Geronimo Eclipse Plugin 2.1.2 RC2.
>
> The deployable zip file is here:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip
>
> The update site zip file is here:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip
>
> The current svn location is here (revision number 686865):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2
>
> The future svn location will be here (when approved):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2
>
> If you would like to review and/or comment on the release notes, they are
> here:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt
>
> There is a rudimentary set of install instructions available at the URL
> below that will hopefully describe the necessary prereq(s) and steps
> required to install and run the GEP:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt
>
> In an effort to get more people to review and vote I'd recommend going
> through this quick but useful tutorial demonstrating some of the
> capabilities of the GEP:
>
> >
> http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>
> Additionally, there is an ant build.xml file that can be used to download
> the prereq(s) for the GEP. It is documented in the instructions.
> Finally, I've created a Staging Site that can used to test the update
> manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP
> itself. This is also documented in the instructions. Please let me know if
> there are any questions and/or problems.
>
> The vote is open for 72 hours and will conclude on Thursday (8/21) at 6:30
> PM ET.
>
> [ ] +1  Release Geronimo Eclipse Plugin 2.1.2
> [ ] +0  No opinion
> [ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2
>
>
>

Re: [jira] Resolved: (GERONIMO-4235) JNDI search should be case-insensitive by default

[Lin Sun]

Yes, thanks for updating this one for me.

Lin

On Wed, Aug 20, 2008 at 8:00 PM, Donald Woods <[EMAIL PROTECTED]> wrote:
> Lin, don't forget to set the Fix Version field, so we can easily generate
> release notes with an accurate list of included JIRAs...
>
>
> -Donald
>
>
> Lin Sun (JIRA) wrote:
>>
>> [
>> https://issues.apache.org/jira/browse/GERONIMO-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Lin Sun resolved GERONIMO-4235.
>> ---
>>
>>Resolution: Fixed
>>
>> see subversion commit tab for commits.
>>
>>> JNDI search should be case-insensitive by default
>>> -
>>>
>>>Key: GERONIMO-4235
>>>URL: https://issues.apache.org/jira/browse/GERONIMO-4235
>>>Project: Geronimo
>>> Issue Type: Improvement
>>> Security Level: public(Regular issues) Components: console
>>>   Affects Versions: 2.1.2
>>>   Reporter: Jürgen Weber
>>>   Assignee: Lin Sun
>>>   Priority: Minor
>>>
>>> Search in the JNDI tree should be case-insensitive by default. There
>>> should be a checkbox [ ] case sensitive which should be off by default.
>>
>
>

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[YunFeng Ma]

+1

-- YunFeng

Tim McConnell wrote: 
Hi everyone, Please review and vote on the maintenance release of the Geronimo 
Eclipse Plugin 2.1.2 RC2. 

The deployable zip file is here: 

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip
 

The update site zip file is here: 

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip
 

The current svn location is here (revision number 686865): 

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2
 

The future svn location will be here (when approved): 

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 

If you would like to review and/or comment on the release notes, they are here: 

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt
 

There is a rudimentary set of install instructions available at the URL below 
that will hopefully describe the necessary prereq(s) and steps 
required to install and run the GEP: 

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt
 

In an effort to get more people to review and vote I'd recommend going through 
this quick but useful tutorial demonstrating some of the capabilities of the 
GEP: 

> 
http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
 

Additionally, there is an ant build.xml file that can be used to download the 
prereq(s) for the GEP. It is documented in the instructions. 
Finally, I've created a Staging Site that can used to test the update manager 
functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP itself. 
This 
is also documented in the instructions. Please let me know if there are any 
questions and/or problems. 

The vote is open for 72 hours and will conclude on Thursday (8/21) at 6:30 PM 
ET. 

[ ] +1  Release Geronimo Eclipse Plugin 2.1.2 
[ ] +0  No opinion 
[ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2 


  

[jira] Updated: (GERONIMO-4235) JNDI search should be case-insensitive by default

[Donald Woods (JIRA)]

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

Donald Woods updated GERONIMO-4235:
---

Affects Version/s: 2.2
Fix Version/s: 2.2
   2.1.3

> JNDI search should be case-insensitive by default
> -
>
> Key: GERONIMO-4235
> URL: https://issues.apache.org/jira/browse/GERONIMO-4235
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.2, 2.2
>Reporter: Jürgen Weber
>Assignee: Lin Sun
>Priority: Minor
> Fix For: 2.1.3, 2.2
>
>
> Search in the JNDI tree should be case-insensitive by default. There should 
> be a checkbox [ ] case sensitive which should be off by default.

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

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[Donald Woods]

+1


-Donald


Tim McConnell wrote:
Hi everyone, Please review and vote on the maintenance release of the 
Geronimo Eclipse Plugin 2.1.2 RC2.


The deployable zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip 



The update site zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip 



The current svn location is here (revision number 686865):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 



The future svn location will be here (when approved):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 



If you would like to review and/or comment on the release notes, they 
are here:


> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt 



There is a rudimentary set of install instructions available at the URL 
below that will hopefully describe the necessary prereq(s) and steps

required to install and run the GEP:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt 



In an effort to get more people to review and vote I'd recommend going 
through this quick but useful tutorial demonstrating some of the 
capabilities of the GEP:


> 
http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html 



Additionally, there is an ant build.xml file that can be used to 
download the prereq(s) for the GEP. It is documented in the instructions.
Finally, I've created a Staging Site that can used to test the update 
manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the 
GEP itself. This is also documented in the instructions. Please let me 
know if there are any questions and/or problems.


The vote is open for 72 hours and will conclude on Thursday (8/21) at 
6:30 PM ET.


[ ] +1  Release Geronimo Eclipse Plugin 2.1.2
[ ] +0  No opinion
[ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [jira] Resolved: (GERONIMO-4235) JNDI search should be case-insensitive by default

[Donald Woods]

Lin, don't forget to set the Fix Version field, so we can easily 
generate release notes with an accurate list of included JIRAs...



-Donald


Lin Sun (JIRA) wrote:

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

Lin Sun resolved GERONIMO-4235.
---

Resolution: Fixed

see subversion commit tab for commits.


JNDI search should be case-insensitive by default
-

Key: GERONIMO-4235
URL: https://issues.apache.org/jira/browse/GERONIMO-4235
Project: Geronimo
 Issue Type: Improvement
 Security Level: public(Regular issues) 
 Components: console

   Affects Versions: 2.1.2
   Reporter: Jürgen Weber
   Assignee: Lin Sun
   Priority: Minor

Search in the JNDI tree should be case-insensitive by default. There should be 
a checkbox [ ] case sensitive which should be off by default.






smime.p7s
Description: S/MIME Cryptographic Signature

Re: Documentation of new 2.2 features in current wiki?

[Donald Woods]

Joe, thanks for doing this.  The maintenance of multiple spaces is worth 
enabling the community to start working on the 2.2 docs.



-Donald


Joe Bohn wrote:



To get things moving I went ahead and did an export of the current 
Geronimo 2.1 space (GMOxDOC21) and restored it as Geronimo 2.2 
(GMOxDOC22).  I only changed the space name and the initial title so 
there are tons of references to Geronimo 2.1 in this new space still.

Here's a link to the new space:
http://cwiki.apache.org/GMOxDOC22/documentation.html

As you can see it looks a lot like the 2.1 space still since it has not 
yet been updated with any 2.2 specifics (beyond a few title changes).


Everyone,
Now that we have 2 spaces we will need to mirror appropriate updates in 
the 2.1 space into the 2.2 space.  Please help us keep the doc 
consistent where appropriate.  Also, feel free to update the new space 
with specifics for Geronimo 2.2 now that we have it.


Rebekah,
I think this should get you moving on making the proposed updates. 
Please update/remove/etc... the references to Geronimo 2.1 as necessary 
to reflect that this is for Geronimo 2.2.


Thanks,
Joe


wei zhang wrote:
Well, only the Export/Restore actions require administrator authority. 
Others like move and copy pages can be done by author, and I have 
tried those actions.



 
On 8/19/08, *Joe Bohn* <[EMAIL PROTECTED] 
> wrote:



Hmmm ... it seems that we might have a problem then.  If admin
authority is required to export/restore then it is also most likely
the case that admin is required to move pages and such for the
proposed new structure.  It might not be possible for Rebekah to
make these changes.

I'm also wondering if we are really at the point where it makes
sense to copy the 2.1 doc to 2.2 and start incurring the duplicate
maintenance costs.  There are not yet any 2.2 pages created under
the parent page that we made for that purpose.  Is now really the
time to export/restore?

Joe

PS.  I also attempted to do a quick export/restore with a very
simple space prior to leaving for vacation.  I had some problems too
... I can't recall what they were at the moment ... I'll have to
give it another shot ... but there might be more than just an
authority issue with this process.


wei zhang wrote:

Hi I tried the Export/Restore option David Belvins suggested,
but couldn't make any progress because only the administrator
can perfrom such actions. Can someone with administrator
authority help?
 Thanks.
Rebekah Zhang

 On 8/19/08, *David Jencks* <[EMAIL PROTECTED]
 >> wrote:


   On Aug 17, 2008, at 11:28 PM, Jack Cai wrote:

   Is someone working on copying 2.1 space to 2.2? :-) If we
don't
   have a solution for the copy approach, maybe we just let
Rebekah
   and her colleagues go ahead to manually copy & 
reorganize...



   David Blevins posted fairly complete instructions for the 
various

   options on aug 1 in this thread.  Is there some problem with
doing
   export/restore?

   thanks
   david jencks



   -Jack










smime.p7s
Description: S/MIME Cryptographic Signature

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[Kevan Miller]

+1. The problems that I saw have all been addressed.

--kevan

On Aug 18, 2008, at 5:24 PM, Tim McConnell <[EMAIL PROTECTED]>  
wrote:


Hi everyone, Please review and vote on the maintenance release of  
the Geronimo Eclipse Plugin 2.1.2 RC2.


The deployable zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip

The update site zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip

The current svn location is here (revision number 686865):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2

The future svn location will be here (when approved):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2

If you would like to review and/or comment on the release notes,  
they are here:


> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt

There is a rudimentary set of install instructions available at the  
URL below that will hopefully describe the necessary prereq(s) and  
steps

required to install and run the GEP:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt

In an effort to get more people to review and vote I'd recommend  
going through this quick but useful tutorial demonstrating some of  
the capabilities of the GEP:


> 
http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html

Additionally, there is an ant build.xml file that can be used to  
download the prereq(s) for the GEP. It is documented in the  
instructions.
Finally, I've created a Staging Site that can used to test the  
update manager functions (i.e., p2 in Ganymede) of Eclipse for  
downloading the GEP itself. This is also documented in the  
instructions. Please let me know if there are any questions and/or  
problems.


The vote is open for 72 hours and will conclude on Thursday (8/21)  
at 6:30 PM ET.


[ ] +1  Release Geronimo Eclipse Plugin 2.1.2
[ ] +0  No opinion
[ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2

--
Thanks,
Tim McConnell

GEP and Geronimo Source Archive

[Jacek Laskowski]

Hi,

I wonder what I should point the Geronimo Source Archive field when I
have the Geronimo sources checked? What about people without the
sources locally? What value(s) do people use for the field? Is it
described somewhere?

Jacek

-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[Jacek Laskowski]

+1

Jacek

On Tue, Aug 19, 2008 at 12:24 AM, Tim McConnell <[EMAIL PROTECTED]> wrote:
> Hi everyone, Please review and vote on the maintenance release of the
> Geronimo Eclipse Plugin 2.1.2 RC2.
>
> The deployable zip file is here:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip
>
> The update site zip file is here:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip
>
> The current svn location is here (revision number 686865):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2
>
> The future svn location will be here (when approved):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2
>
> If you would like to review and/or comment on the release notes, they are
> here:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt
>
> There is a rudimentary set of install instructions available at the URL
> below that will hopefully describe the necessary prereq(s) and steps
> required to install and run the GEP:
>
> >
> http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt
>
> In an effort to get more people to review and vote I'd recommend going
> through this quick but useful tutorial demonstrating some of the
> capabilities of the GEP:
>
> >
> http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>
> Additionally, there is an ant build.xml file that can be used to download
> the prereq(s) for the GEP. It is documented in the instructions.
> Finally, I've created a Staging Site that can used to test the update
> manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the GEP
> itself. This is also documented in the instructions. Please let me know if
> there are any questions and/or problems.
>
> The vote is open for 72 hours and will conclude on Thursday (8/21) at 6:30
> PM ET.
>
> [ ] +1  Release Geronimo Eclipse Plugin 2.1.2
> [ ] +0  No opinion
> [ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2
>
> --
> Thanks,
> Tim McConnell
>
>
>



-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

Re: svn commit: r687475 - /geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.jee.v21.jaxbmodel/src/main/java/org/apache/geronimo/jee/deployment/Artifact.java

[Jacek Laskowski]

On Wed, Aug 20, 2008 at 11:34 PM,  <[EMAIL PROTECTED]> wrote:
> Author: mcconne
> Date: Wed Aug 20 14:34:53 2008
> New Revision: 687475
>
> URL: http://svn.apache.org/viewvc?rev=687475&view=rev
> Log:
> GERONIMODEVTOOLS-489 Clean-up insertion of empty xml tags. Thanks to BJ Reed 
> for this patch !!
>
> Modified:
>
> geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.jee.v21.jaxbmodel/src/main/java/org/apache/geronimo/jee/deployment/Artifact.java
>
> Modified: 
> geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.jee.v21.jaxbmodel/src/main/java/org/apache/geronimo/jee/deployment/Artifact.java
> URL: 
> http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.jee.v21.jaxbmodel/src/main/java/org/apache/geronimo/jee/deployment/Artifact.java?rev=687475&r1=687474&r2=687475&view=diff
> ==
> --- 
> geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.jee.v21.jaxbmodel/src/main/java/org/apache/geronimo/jee/deployment/Artifact.java
>  (original)
> +++ 
> geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.jee.v21.jaxbmodel/src/main/java/org/apache/geronimo/jee/deployment/Artifact.java
>  Wed Aug 20 14:34:53 2008
> @@ -168,7 +168,10 @@
>  *
>  */
> public void setVersion(String value) {
> -this.version = value;
> +if (value == null || value.length() == 0)
> +this.version = null;
> +else
> +this.version = value;
> }

Shouldn't curly braces be used in the if stmt? (cf.
http://geronimo.apache.org/coding-standards.html)

Jacek

-- 
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

[jira] Resolved: (GERONIMODEVTOOLS-489) New Dependency popup window creates empty xml tags when no value provided

[Tim McConnell (JIRA)]

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

Tim McConnell resolved GERONIMODEVTOOLS-489.


Resolution: Fixed

Applied with r687475. Thanks BJ Reed for this patch .

> New Dependency popup window creates empty xml tags when no value provided
> -
>
> Key: GERONIMODEVTOOLS-489
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-489
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Jacek Laskowski
>Assignee: Tim McConnell
>Priority: Trivial
> Fix For: 2.1.3
>
> Attachments: GERONIMODEVTOOLS-489.patch
>
>
> Use Add button in Server Dependencies in Geronimo Deployment Plan Editor to 
> define a new dependency. When Version and Artifact Type are empty, empty xml 
> tags  and  are created. They're unnecessary.

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

[jira] Updated: (GERONIMODEVTOOLS-489) New Dependency popup window creates empty xml tags when no value provided

[Tim McConnell (JIRA)]

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

Tim McConnell updated GERONIMODEVTOOLS-489:
---

 Priority: Trivial  (was: Major)
Fix Version/s: 2.1.3

> New Dependency popup window creates empty xml tags when no value provided
> -
>
> Key: GERONIMODEVTOOLS-489
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-489
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Jacek Laskowski
>Assignee: Tim McConnell
>Priority: Trivial
> Fix For: 2.1.3
>
> Attachments: GERONIMODEVTOOLS-489.patch
>
>
> Use Add button in Server Dependencies in Geronimo Deployment Plan Editor to 
> define a new dependency. When Version and Artifact Type are empty, empty xml 
> tags  and  are created. They're unnecessary.

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

Re: Documentation of new 2.2 features in current wiki?

[Lin Sun]

I wish there is a way to tag a document page and say that it applies
to whatever release(s), then we can generate user docs for a release
based on documents that are tagged for that release.  It seems
reasonable for certain document pages to stay the same between
multiple releases.

Lin

On Wed, Aug 20, 2008 at 5:27 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
> Lin Sun wrote:
>>
>> I am concerned at making changes in two places and we should eliminate
>> that if possible.   Should we only copy the documents that are
>> complete?   Is the check mark next to the document link a good
>> indication of completeness?
>
> I agree with the concern (in fact I raised it myself yesterday) ... but it
> seems that the time is right to start the 2.2 doc.  We have people willing
> to jump in and help out with a new structure (like Rebekah and Jack) that
> were currently stuck and people were also interested in documenting 2.2
> functions.  It was agreed that seeding the 2.2 doc from the 2.1 space was
> the right approach.  Unfortunately, the export/restore is an "all or
> nothing" proposition.  You either copy the entire space or manually copy
> each individual page.  I have no idea if the checkmarks are accurate ... but
> I suspect they are not.
>
> As far as maintaining the 2 docs, I think we all should take the following
> approach:
> - Treat the 2.2 documentation as the "primary" documentation.  In other
> words, update this first if there are changes to be made.
> - Mirror updates from the 2.2 doc back to the 2.1 doc.
>
> That way, if there is any discrepancy we will know that the 2.2 doc is "more
> correct" and the things just might not have been mirrored back to 2.1 (or
> perhaps changed in 2.2).
>
> Joe
>
>
>>
>> Lin
>>
>> On Wed, Aug 20, 2008 at 4:39 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
>>
>>> Everyone,
>>> Now that we have 2 spaces we will need to mirror appropriate updates in
>>> the
>>> 2.1 space into the 2.2 space.  Please help us keep the doc consistent
>>> where
>>> appropriate.  Also, feel free to update the new space with specifics for
>>> Geronimo 2.2 now that we have it.
>>>
>>
>>> Thanks,
>>> Joe
>>
>
>

[jira] Updated: (GERONIMO-3469) From console: database pool doesn't work well if the name contains a / like jdbc/EmployeeDataSource

[Lin Sun (JIRA)]

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

Lin Sun updated GERONIMO-3469:
--

Attachment: G3469.patch

Is there any reason to use pool name as the artifactId?   I propose we use pool 
name as artifactId if there is no / in the pool, otherwise, we just use the 
pool name portion after / as the artifactId.  Or do we want to let our users 
set their artifactId?

> From console: database pool doesn't work well if the name contains a / like 
> jdbc/EmployeeDataSource
> ---
>
> Key: GERONIMO-3469
> URL: https://issues.apache.org/jira/browse/GERONIMO-3469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: databases
>Affects Versions: 2.0.1
> Environment: winxp + Sun JDK 1.5
>Reporter: Lin Sun
>Assignee: Lin Sun
> Attachments: G3469.patch
>
>
> 1) If I create a database pool called jdbc/EmployeeDataSource, I won't be 
> able to delete it from the database pool portlet page.   
> 2) Also, while creating a new database pool, it seems not giving the option 
> to have different input boxes for the artifact name and the database pool 
> name.  They are in the same input box.  This was not true for previous 
> releases IIRC.  For example, if I name the database pool 
> jdbc/EmployeeDataSource, the full artifact name will be 
> console.dbpool/jdbc%2FEmployeeDatasource/1.0/rar.  This is undesired and 
> error prune, as I don't want that / in the artifact name.
> Seems fixing No. 2 may fix No. 1.   

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

Re: Documentation of new 2.2 features in current wiki?

[Joe Bohn]

Lin Sun wrote:

I am concerned at making changes in two places and we should eliminate
that if possible.   Should we only copy the documents that are
complete?   Is the check mark next to the document link a good
indication of completeness?


I agree with the concern (in fact I raised it myself yesterday) ... but 
it seems that the time is right to start the 2.2 doc.  We have people 
willing to jump in and help out with a new structure (like Rebekah and 
Jack) that were currently stuck and people were also interested in 
documenting 2.2 functions.  It was agreed that seeding the 2.2 doc from 
the 2.1 space was the right approach.  Unfortunately, the export/restore 
is an "all or nothing" proposition.  You either copy the entire space or 
manually copy each individual page.  I have no idea if the checkmarks 
are accurate ... but I suspect they are not.


As far as maintaining the 2 docs, I think we all should take the 
following approach:
- Treat the 2.2 documentation as the "primary" documentation.  In other 
words, update this first if there are changes to be made.

- Mirror updates from the 2.2 doc back to the 2.1 doc.

That way, if there is any discrepancy we will know that the 2.2 doc is 
"more correct" and the things just might not have been mirrored back to 
2.1 (or perhaps changed in 2.2).


Joe




Lin

On Wed, Aug 20, 2008 at 4:39 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:


Everyone,
Now that we have 2 spaces we will need to mirror appropriate updates in the
2.1 space into the 2.2 space.  Please help us keep the doc consistent where
appropriate.  Also, feel free to update the new space with specifics for
Geronimo 2.2 now that we have it.




Thanks,
Joe

Re: Documentation of new 2.2 features in current wiki?

[Lin Sun]

I am concerned at making changes in two places and we should eliminate
that if possible.   Should we only copy the documents that are
complete?   Is the check mark next to the document link a good
indication of completeness?

Lin

On Wed, Aug 20, 2008 at 4:39 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

> Everyone,
> Now that we have 2 spaces we will need to mirror appropriate updates in the
> 2.1 space into the 2.2 space.  Please help us keep the doc consistent where
> appropriate.  Also, feel free to update the new space with specifics for
> Geronimo 2.2 now that we have it.
>

> Thanks,
> Joe

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[Tim McConnell]

+1

Tim McConnell wrote:
Hi everyone, Please review and vote on the maintenance release of the 
Geronimo Eclipse Plugin 2.1.2 RC2.


The deployable zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip 



The update site zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip 



The current svn location is here (revision number 686865):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 



The future svn location will be here (when approved):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 



If you would like to review and/or comment on the release notes, they 
are here:


> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt 



There is a rudimentary set of install instructions available at the URL 
below that will hopefully describe the necessary prereq(s) and steps

required to install and run the GEP:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt 



In an effort to get more people to review and vote I'd recommend going 
through this quick but useful tutorial demonstrating some of the 
capabilities of the GEP:


> 
http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html 



Additionally, there is an ant build.xml file that can be used to 
download the prereq(s) for the GEP. It is documented in the instructions.
Finally, I've created a Staging Site that can used to test the update 
manager functions (i.e., p2 in Ganymede) of Eclipse for downloading the 
GEP itself. This is also documented in the instructions. Please let me 
know if there are any questions and/or problems.


The vote is open for 72 hours and will conclude on Thursday (8/21) at 
6:30 PM ET.


[ ] +1  Release Geronimo Eclipse Plugin 2.1.2
[ ] +0  No opinion
[ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2



--
Thanks,
Tim McConnell

Re: Documentation of new 2.2 features in current wiki?

[Joe Bohn]

To get things moving I went ahead and did an export of the current 
Geronimo 2.1 space (GMOxDOC21) and restored it as Geronimo 2.2 
(GMOxDOC22).  I only changed the space name and the initial title so 
there are tons of references to Geronimo 2.1 in this new space still.

Here's a link to the new space:
http://cwiki.apache.org/GMOxDOC22/documentation.html

As you can see it looks a lot like the 2.1 space still since it has not 
yet been updated with any 2.2 specifics (beyond a few title changes).


Everyone,
Now that we have 2 spaces we will need to mirror appropriate updates in 
the 2.1 space into the 2.2 space.  Please help us keep the doc 
consistent where appropriate.  Also, feel free to update the new space 
with specifics for Geronimo 2.2 now that we have it.


Rebekah,
I think this should get you moving on making the proposed updates. 
Please update/remove/etc... the references to Geronimo 2.1 as necessary 
to reflect that this is for Geronimo 2.2.


Thanks,
Joe


wei zhang wrote:
Well, only the Export/Restore actions require administrator authority. 
Others like move and copy pages can be done by author, and I have tried 
those actions.



 
On 8/19/08, *Joe Bohn* <[EMAIL PROTECTED] 
> wrote:



Hmmm ... it seems that we might have a problem then.  If admin
authority is required to export/restore then it is also most likely
the case that admin is required to move pages and such for the
proposed new structure.  It might not be possible for Rebekah to
make these changes.

I'm also wondering if we are really at the point where it makes
sense to copy the 2.1 doc to 2.2 and start incurring the duplicate
maintenance costs.  There are not yet any 2.2 pages created under
the parent page that we made for that purpose.  Is now really the
time to export/restore?

Joe

PS.  I also attempted to do a quick export/restore with a very
simple space prior to leaving for vacation.  I had some problems too
... I can't recall what they were at the moment ... I'll have to
give it another shot ... but there might be more than just an
authority issue with this process.


wei zhang wrote:

Hi I tried the Export/Restore option David Belvins suggested,
but couldn't make any progress because only the administrator
can perfrom such actions. Can someone with administrator
authority help?
 Thanks.
Rebekah Zhang

 On 8/19/08, *David Jencks* <[EMAIL PROTECTED]
 >> wrote:


   On Aug 17, 2008, at 11:28 PM, Jack Cai wrote:

   Is someone working on copying 2.1 space to 2.2? :-) If we
don't
   have a solution for the copy approach, maybe we just let
Rebekah
   and her colleagues go ahead to manually copy & reorganize...


   David Blevins posted fairly complete instructions for the various
   options on aug 1 in this thread.  Is there some problem with
doing
   export/restore?

   thanks
   david jencks



   -Jack

[jira] Updated: (GERONIMODEVTOOLS-390) common deployment plan editor improvements

[B.J. Reed (JIRA)]

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

B.J. Reed updated GERONIMODEVTOOLS-390:
---

Issue Type: Task  (was: Improvement)

> common deployment plan editor improvements
> --
>
> Key: GERONIMODEVTOOLS-390
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-390
> Project: Geronimo-Devtools
>  Issue Type: Task
>  Components: eclipse-plugin
>Affects Versions: 2.1.3
>Reporter: B.J. Reed
>Assignee: B.J. Reed
>Priority: Minor
> Fix For: 2.1.2
>
>
> This is a place holder for any issues that are common between multiple 
> deployment plan editors.
> Please add any minor issues or improvements as sub-tasks.

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

[jira] Resolved: (GERONIMO-4235) JNDI search should be case-insensitive by default

[Lin Sun (JIRA)]

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

Lin Sun resolved GERONIMO-4235.
---

Resolution: Fixed

see subversion commit tab for commits.

> JNDI search should be case-insensitive by default
> -
>
> Key: GERONIMO-4235
> URL: https://issues.apache.org/jira/browse/GERONIMO-4235
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.2
>Reporter: Jürgen Weber
>Assignee: Lin Sun
>Priority: Minor
>
> Search in the JNDI tree should be case-insensitive by default. There should 
> be a checkbox [ ] case sensitive which should be off by default.

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

[jira] Assigned: (GERONIMO-4235) JNDI search should be case-insensitive by default

[Lin Sun (JIRA)]

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

Lin Sun reassigned GERONIMO-4235:
-

Assignee: Lin Sun

> JNDI search should be case-insensitive by default
> -
>
> Key: GERONIMO-4235
> URL: https://issues.apache.org/jira/browse/GERONIMO-4235
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.2
>Reporter: Jürgen Weber
>Assignee: Lin Sun
>Priority: Minor
>
> Search in the JNDI tree should be case-insensitive by default. There should 
> be a checkbox [ ] case sensitive which should be off by default.

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

Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.2 (RC2)

[B.J. Reed]

+1

Tim McConnell wrote:
Hi everyone, Please review and vote on the maintenance release of the 
Geronimo Eclipse Plugin 2.1.2 RC2.


The deployable zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-deployable.zip 



The update site zip file is here:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/geronimo-eclipse-plugin-2.1.2-updatesite.zip 



The current svn location is here (revision number 686865):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.1.2 



The future svn location will be here (when approved):

> 
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.1.2 



If you would like to review and/or comment on the release notes, they 
are here:


> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/PLUGIN_RELEASE-NOTES-2.1.2.txt 



There is a rudimentary set of install instructions available at the 
URL below that will hopefully describe the necessary prereq(s) and steps

required to install and run the GEP:

> 
http://people.apache.org/~mcconne/releases/2.1.2/RC2/Geronimo_Eclipse_Plugin_2.1.2_Instructions-RC2.txt 



In an effort to get more people to review and vote I'd recommend going 
through this quick but useful tutorial demonstrating some of the 
capabilities of the GEP:


> 
http://cwiki.apache.org/GMOxDOC21/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html 



Additionally, there is an ant build.xml file that can be used to 
download the prereq(s) for the GEP. It is documented in the instructions.
Finally, I've created a Staging Site that can used to test the update 
manager functions (i.e., p2 in Ganymede) of Eclipse for downloading 
the GEP itself. This is also documented in the instructions. Please 
let me know if there are any questions and/or problems.


The vote is open for 72 hours and will conclude on Thursday (8/21) at 
6:30 PM ET.


[ ] +1  Release Geronimo Eclipse Plugin 2.1.2
[ ] +0  No opinion
[ ] -1  Don't release Geronimo Eclipse Plugin 2.1.2

[jira] Resolved: (GERONIMODEVTOOLS-176) GeronimoServerBehaviourDelegate always uses rmi port 1099

[Tim McConnell (JIRA)]

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

Tim McConnell resolved GERONIMODEVTOOLS-176.


Resolution: Fixed

Tried all combinations that I could think of. Ran server both in and outside of 
Eclipse using non-default RMI naming port and Eclipse is able to synchronize 
with the server. Deployed and undeployed various artifacts using port  and 
all deployed and ran fine. Nice work. Applied to GEP trunk at r687428. Thanks 
BJ Reed for the patch.

> GeronimoServerBehaviourDelegate always uses rmi port 1099
> -
>
> Key: GERONIMODEVTOOLS-176
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-176
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.3
>Reporter: Donald Woods
>Assignee: Tim McConnell
> Fix For: 2.1.3
>
> Attachments: GERONIMODEVTOOLS-176.patch
>
>
> We need to allow the user to reconfigure the RMI port, for the cases where 
> they have mapped the server to use something besides the default 1099 port.  
> Also, this would allow the plugin to support the new multiple server instance 
> feature in the 2.0 server

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

[jira] Resolved: (GERONIMODEVTOOLS-488) Incorrect names for Group Id and Artifact Id columns in Server Dependencies in deployment plan editor

[Tim McConnell (JIRA)]

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

Tim McConnell resolved GERONIMODEVTOOLS-488.


   Resolution: Fixed
Fix Version/s: 2.1.3

Works fine and applied BJ's patch at r687417. Thanks BJ Reed for the patch !!

> Incorrect names for Group Id and Artifact Id columns in Server Dependencies 
> in deployment plan editor
> -
>
> Key: GERONIMODEVTOOLS-488
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-488
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Jacek Laskowski
>Assignee: B.J. Reed
> Fix For: 2.1.3
>
> Attachments: GERONIMODEVTOOLS-488.patch
>
>
> In Geronimo Deployment Plan Editor, in Server Dependencies of Deployment, the 
> Group Id and Artifact Id column names are incorrect (they should change their 
> places).

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

[jira] Updated: (GERONIMODEVTOOLS-489) New Dependency popup window creates empty xml tags when no value provided

[B.J. Reed (JIRA)]

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

B.J. Reed updated GERONIMODEVTOOLS-489:
---

Attachment: GERONIMODEVTOOLS-489.patch

Patch included should fix this.  I'm certain that we have a bunch of small 
problems that are very similar to these.  I started a list at 
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-395 to try to keep them 
somewhat together.  If you find more (and I'm pretty sure you will), please add 
them to that list.

> New Dependency popup window creates empty xml tags when no value provided
> -
>
> Key: GERONIMODEVTOOLS-489
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-489
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Jacek Laskowski
>Assignee: Tim McConnell
> Attachments: GERONIMODEVTOOLS-489.patch
>
>
> Use Add button in Server Dependencies in Geronimo Deployment Plan Editor to 
> define a new dependency. When Version and Artifact Type are empty, empty xml 
> tags  and  are created. They're unnecessary.

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

[jira] Updated: (GERONIMODEVTOOLS-488) Incorrect names for Group Id and Artifact Id columns in Server Dependencies in deployment plan editor

[B.J. Reed (JIRA)]

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

B.J. Reed updated GERONIMODEVTOOLS-488:
---

Attachment: GERONIMODEVTOOLS-488.patch

2 line patch that fixes the GUIthe add/edit dialog was also reversed order.

> Incorrect names for Group Id and Artifact Id columns in Server Dependencies 
> in deployment plan editor
> -
>
> Key: GERONIMODEVTOOLS-488
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-488
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Jacek Laskowski
>Assignee: B.J. Reed
> Attachments: GERONIMODEVTOOLS-488.patch
>
>
> In Geronimo Deployment Plan Editor, in Server Dependencies of Deployment, the 
> Group Id and Artifact Id column names are incorrect (they should change their 
> places).

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

[BUILD] trunk: Failed for Revision: 687314

[gawor]

Geronimo Revision: 687314 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080820/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080820
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 40 minutes 23 seconds
[INFO] Finished at: Wed Aug 20 09:44:03 EDT 2008
[INFO] Final Memory: 369M/1015M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080820/logs-0900-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080820/logs-0900-jetty/test.log
 
 
Downloading: 
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: 
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: jetty
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache-snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty6-javaee5/2.2-SNAPSHOT/geronimo-jetty6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:39.661
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 32 test build(s)
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:01:06.713) 
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:30.208) 
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:18.754) 
[INFO] commands-testsuite/shutdown  RUNNING
[INFO] commands-testsuite/shutdown  SUCCESS (0:00:16.581) 
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:08.271) 
[INFO] console-testsuite/advanced   RUNNING
[INFO] console-testsuite/advanced   FAILURE (0:01:21.342) Java 
returned: 1
[INFO] console-testsuite/basic  RUNNING
[INFO] console-testsuite/basic  SUCCESS (0:01:50.454) 
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.539) 
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:01:05.984) 
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:44.526) 
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:31.087) 
[INFO] deployment-testsuite/jca-cms-tests   RUNNING
[INFO] deployment-testsuite/jca-cms-tests   SUCCESS (0:00:28.578) 
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:30.379) 
[INFO] enterprise-testsuite/ejb-tests   RUNNING
[INFO] enterprise-testsuite/ejb-tests   SUCCESS (0:00:32.899) 
[INFO] enterprise-testsuite

[jira] Assigned: (GERONIMODEVTOOLS-488) Incorrect names for Group Id and Artifact Id columns in Server Dependencies in deployment plan editor

[B.J. Reed (JIRA)]

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

B.J. Reed reassigned GERONIMODEVTOOLS-488:
--

Assignee: B.J. Reed  (was: Tim McConnell)

> Incorrect names for Group Id and Artifact Id columns in Server Dependencies 
> in deployment plan editor
> -
>
> Key: GERONIMODEVTOOLS-488
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-488
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Jacek Laskowski
>Assignee: B.J. Reed
>
> In Geronimo Deployment Plan Editor, in Server Dependencies of Deployment, the 
> Group Id and Artifact Id column names are incorrect (they should change their 
> places).

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

[jira] Commented: (GERONIMO-4241) NPE when calling folder.getDeletedMessageCount() for POP3 store

[Dave Rushall (JIRA)]

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

Dave Rushall commented on GERONIMO-4241:


Perhaps I'm missing something, but I don't understand why 
getDeletedMessageCount() is attempting to open the second connection, at all. 
If the application already has the folder open (read/write), then attempting to 
open the second session to the same POP3 folder is going to fail, isn't it? I 
would have thought that the POP3 folder implementation should be able to 
determine the count without making a second connection - getMessageCount() 
doesn't make a second connection, for example.

For now, I'm working around the problem for POP3 by assuming that 
getDeletedMessageCount() always returns 0, unless I have deleted a message in 
my active session. It seems odd that I have to do this and this workaround does 
not seem to be necessary when using another implementation of Javamail.


> NPE when calling folder.getDeletedMessageCount() for POP3 store
> ---
>
> Key: GERONIMO-4241
> URL: https://issues.apache.org/jira/browse/GERONIMO-4241
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: mail
> Environment: geronimo-javamail_1.4_mail-1.4.jar
> IBM JRE 6 SR 1
> Windows XP
>Reporter: Dave Rushall
>
> Calling folder.getDeletedMessageCount() for POP3 store results in the 
> following NPE...
> java.lang.NullPointerException
>   at 
> org.apache.geronimo.javamail.store.pop3.POP3Store.isConnected(POP3Store.java:238)
>   at 
> org.apache.geronimo.javamail.store.pop3.POP3Folder.isOpen(POP3Folder.java:354)
>   at javax.mail.Folder.getCount(Folder.java:436)
>   at javax.mail.Folder.getDeletedMessageCount(Folder.java:432)
> Note that calling folder.getMessageCount() functions as expected.
> The debug logs suggest that getDeletedMessageCount() attempts to open a 
> second simultaneous connection, which is refused by the server...
> Loading javamail.default.providers from 
> jar:file:/C:/Documents%20and%20Settings/Administrator/Desktop/Calico/other/geronimo-javamail_1.4_mail-1.4.jar!/META-INF/javamail.default.providers
> DEBUG: loading new provider protocol=smtp, 
> className=org.apache.geronimo.javamail.transport.smtp.SMTPTransport, 
> vendor=Apache Software Foundation, version=1.0
> DEBUG: loading new provider protocol=smtps, 
> className=org.apache.geronimo.javamail.transport.smtp.SMTPTSransport, 
> vendor=Apache Software Foundation, version=1.0
> DEBUG: loading new provider protocol=nntp-post, 
> className=org.apache.geronimo.javamail.transport.nntp.NNTPTransport, 
> vendor=Apache Software Foundation, version=1.0
> DEBUG: loading new provider protocol=nntp, 
> className=org.apache.geronimo.javamail.store.nntp.NNTPStore, vendor=Apache 
> Software Foundation, version=1.0
> DEBUG: loading new provider protocol=pop3, 
> className=org.apache.geronimo.javamail.store.pop3.POP3Store, vendor=Apache 
> Software Foundation, version=1.0
> DEBUG: loading new provider protocol=pop3s, 
> className=org.apache.geronimo.javamail.store.pop3.POP3SSLStore, vendor=Apache 
> Software Foundation, version=1.0
> DEBUG: loading new provider protocol=imap, 
> className=org.apache.geronimo.javamail.store.imap.IMAPStore, vendor=Apache 
> Software Foundation, version=1.0
> DEBUG: loading new provider protocol=imaps, 
> className=org.apache.geronimo.javamail.store.imap.IMAPSSLStore, vendor=Apache 
> Software Foundation, version=1.0
> DEBUG: getProvider() returning provider protocol=pop3; [EMAIL PROTECTED]; 
> class=org.apache.geronimo.javamail.store.pop3.POP3Store; vendor=Apache 
> Software Foundation;version=1.0
> IMAPStore DEBUG: Attempting plain socket connection to server null:0
> POP3Store DEBUG: Connecting to server :110 for user 
> IMAPStore DEBUG: Attempting plain socket connection to server :110
> +OK POP3  v2003.83 server ready
> USER 
> +OK User name accepted, password please
> PASS 
> +OK Mailbox open, 0 messages
> NOOP
> +OK No-op to you too!
> STAT
> +OK 0 0
> IMAPStore DEBUG: Attempting plain socket connection to server :110
> +OK POP3  v2003.83 server ready
> USER 
> +OK User name accepted, password please
> PASS 
> -ERR Can't get lock.  Mailbox in use

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

[jira] Updated: (GERONIMO-4257) Problem with processing and delivery jms messages

[Tomasz Mazan (JIRA)]

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

Tomasz Mazan updated GERONIMO-4257:
---

Priority: Critical  (was: Major)

> Problem with processing and delivery jms messages
> -
>
> Key: GERONIMO-4257
> URL: https://issues.apache.org/jira/browse/GERONIMO-4257
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: ActiveMQ, OpenEJB, transaction manager
>Affects Versions: 2.1.1, 2.1.2
> Environment: Windows XPPro SP2, JDK 6
>Reporter: Tomasz Mazan
>Priority: Critical
>
> I've found strange Geronimo 2.1.2 behaviour with using JMS.
> 1) When message is waiting for delivery to MDB i cannot undeploy module with 
> this MDB from command line. I have to stop module via G-console and then 
> undeploy
> 2) If messages are waiting for delivery and I shutdown server (geronimo stop) 
> and the run it again none of messages are delivered to listener
> 3) When MDB onMessage method throws i.e. NullPointerException, the 
> transaction is rolledback but  a) message is not being redelivered anymore, 
> b) module couldn't be restarted == application stops working
> :(
> Geronimo 2.1 hadn't these "features".

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

[jira] Created: (GERONIMO-4257) Problem with processing and delivery jms messages

[Tomasz Mazan (JIRA)]

Problem with processing and delivery jms messages
-

 Key: GERONIMO-4257
 URL: https://issues.apache.org/jira/browse/GERONIMO-4257
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: ActiveMQ, OpenEJB, transaction manager
Affects Versions: 2.1.2, 2.1.1
 Environment: Windows XPPro SP2, JDK 6
Reporter: Tomasz Mazan


I've found strange Geronimo 2.1.2 behaviour with using JMS.

1) When message is waiting for delivery to MDB i cannot undeploy module with 
this MDB from command line. I have to stop module via G-console and then 
undeploy

2) If messages are waiting for delivery and I shutdown server (geronimo stop) 
and the run it again none of messages are delivered to listener

3) When MDB onMessage method throws i.e. NullPointerException, the transaction 
is rolledback but  a) message is not being redelivered anymore, b) module 
couldn't be restarted == application stops working

:(
Geronimo 2.1 hadn't these "features".

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

[jira] Commented: (GERONIMODEVTOOLS-482) missing image for GEP features in "About Eclipse Platform" Dialog

[Delos Dai (JIRA)]

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

Delos Dai commented on GERONIMODEVTOOLS-482:


Tim, thank you for your help.
With the URL you gave, I found no problem of the image. I think I got wrong 
version. Sorry for the mistake. Thank you again!



> missing image for GEP features in "About Eclipse Platform" Dialog
> -
>
> Key: GERONIMODEVTOOLS-482
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-482
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
> Environment: build in Ubuntu 8.04 and Windows XP sp2. Jdk 1.5
>Reporter: Delos Dai
>Assignee: Tim McConnell
> Fix For: 2.1.2
>
> Attachments: screenshot-1.jpg
>
>
> After I successfully build GEP with "mvn install", I get the package 
> "geronimo-eclipse-plugin-2.1.2-deployable.zip" in assembly/target.
> "geronimo-eclipse-plugin-2.1.2-deployable.zip" should be the distribution to 
> user. But when I install GEP of this package, I found the image for GEP 
> feature is missed in "About Eclipse Platform" dialog (see the attachment). In 
> fact, you may find the image file in the package is broken. But I can see the 
> image when I develop GEP in eclipse. 

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

[jira] Created: (GERONIMODEVTOOLS-493) Update failure when upgrading GEP 2.1.1 to 2.1.2 using staging site

[Forrest Xia (JIRA)]

Update failure when upgrading GEP 2.1.1 to 2.1.2 using staging site
---

 Key: GERONIMODEVTOOLS-493
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-493
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.1
 Environment: Windows XP SP2
Eclipse Ganymede JEE package
IBM SDK 5 SR6b
Reporter: Forrest Xia
Assignee: Tim McConnell


Steps:
1. Install GEP 2.1.1 through "Download additional server adapters"
2. Configure the staging site point to 
"http://people.apache.org/~tkirby/releases/2.1.2/RC1/staging_site/eclipse/updates/";
3. Click "Software Updates..."->"Installed Software"->"Geronimo v2.1 Server 
Adapter", then click "Update..." button.

Symptom:
The P2 update program recognized new version 2.1.2 from the configured staging 
site, but the size and detail info is missing, anyway click Finish button to 
start upgrading. After a while, an error shows up as follows:
"An error occurred during provisioning.
  Failed to prepare partial IU: [R]org.apache.geronimo.st.schemas 2.1.2.
"

Considering GEP community will face upgrading existing GEP 2.1.1 to 2.1.2, so 
the scenario described above should be valid :)

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

[jira] Created: (GERONIMODEVTOOLS-492) GEP v2.1.1 installation error in eclipse Ganymede JEE package

[Forrest Xia (JIRA)]

GEP v2.1.1 installation error in eclipse Ganymede JEE package
-

 Key: GERONIMODEVTOOLS-492
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-492
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.1
 Environment: OS: Windows XP SP2 and Ubuntu 8.04
Eclipse: Eclipse Ganymede JEE package, based on Version: 3.4.0 Build id: 
I20080617-2000
JDK: IBM SDK 5 sr6b
Reporter: Forrest Xia
Assignee: Tim McConnell


Steps:
1. Download and lauch eclipse ganymede
2. click "Software Updates..."->"Available Software" to add a site point to 
http://www.apache.org/dist/geronimo/eclipse/updates
3. Choose "Geronimo v2.1 Server Adapter" to install

Symptom:
An install error shows up as follows:
Cannot complete the request.  See the details.
Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
requiredCapability: 
org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] 
requiredCapability: 
org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] 
requiredCapability: 
org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
requiredCapability: 
org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0)
Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] 
requiredCapability: 
org.eclipse.equinox.p2.iu/org.apache.geronimo.feature.feature.group/[2.1.1,2.1.1]


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