Re: [VOTE] GEP 2.2 release - RC1

[Ivan]

With deployable assembly, I could install it to a clean Eclipse 3.5 and
configure a server rumtime for 2.2, it seems to work well for me !

+1

2010/1/6 Delos 

> Hope all PMC members can see the thread, could you help to review the
> release candidate and give your vote?
>
> Thanks very much!
>
> 2010/1/5 Rex Wang 
>
> +1
>> thanks!
>>
>>
>> 2010/1/4 Delos 
>>
>> Hi everyone, Please review and vote on the release of the Geronimo
>>> Eclipse Plugin 2.2 RC1.
>>>
>>> The deployable zip file is here:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
>>>
>>> The update site zip file is here:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
>>>
>>> The current svn location is here (revision number 894784):
>>>
>>> >
>>> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
>>>
>>> The future svn location will be here (when approved):
>>>
>>> >
>>> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
>>>
>>> If you would like to review and/or comment on the release notes, they are
>>> here:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
>>>
>>> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>>>
>>> Finally, I've created a Staging Site that can be used to test the update
>>> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for
>>> downloading the GEP itself. This is also documented in the instructions, but
>>> you must use the staging site created for this vote at:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
>>>
>>> Please let me know if there are any questions and/or problems. The voteis 
>>> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM
>>> ET.
>>>
>>> [ ] +1  Release Geronimo Eclipse Plugin 2.2
>>> [ ] +0  No opinion
>>> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
>>>
>>> Thanks in advance!
>>>
>>> --
>>> Best Regards,
>>>
>>> Delos
>>>
>>
>>
>>
>> --
>> --
>> Lei Wang (Rex)
>> rwonly AT apache.org
>>
>
>
>
> --
> Best Regards,
>
> Delos
>



-- 
Ivan

Re: [Discussion] How about upgrade Dojo version to 1.4.0 for Geronimo 3.0?

[Delos]

As I know, some new widgets are added and most of the widgets from old
version are kept.

I agree with Shawn, we can verify the pages once admin console in G 3.0 is
ready.

Thanks!

2010/1/6 Shawn Jiang 

> Agree , we should test the functions that were using old dojo to see if
> they are still working after upgrading to dojo 1.4.0.
>
> On Wed, Jan 6, 2010 at 2:54 PM, Ivan  wrote:
>
>> Is the new version compatable with the old one ? If yes, I think we could
>> upgrade it.
>>
>> 2010/1/6 Delos 
>>
>> Hi,
>>>
>>> Dojo 1.4.0 has released on Dec.15.  How about upgrade Dojo version to
>>> 1.4.0 for Geronimo 3.0?
>>>
>>> Some new Widgets are provided, such as EnhancedDataGrid; meanswhile a lot
>>> of refactoring work makes it faster than before.
>>>
>>> BTW, for you to feel the improvement of Dojo 1.4.0, I have uploaded a
>>> demo of pluto 2.0 and Dojo 1.4.0 here
>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/portlet+dojo/portlet-dojo1.4.0-demo.zip.
>>>
>>>
>>> Steps to run demo
>>> 1. Extract the zip
>>> 2. launch "bin/startup.sh" or bin/startup.bat"
>>> 3. visit "http://localhost:8080/pluto/portal/BundlePage“, you will see a
>>> portlet showing OSGI bundles with dojo 1.4.0 widgets
>>>
>>> Upgrade to Dojo 1.4.0, any comments?
>>>
>>> Thanks!
>>> --
>>> Best Regards,
>>>
>>> Delos
>>>
>>
>>
>>
>> --
>> Ivan
>>
>
>
>
> --
> Shawn
>



-- 
Best Regards,

Delos

Re: components version in G2.2

[chi runhua]

Thanks Jack for the suggestion.

I've update the page[1] based on component versions in G2.2.

[1] http://cwiki.apache.org/GMOxDOC22/component-versions.html

Could anyone help to review the page?

Any questions, please let me know.

Jeff

On Wed, Dec 30, 2009 at 11:40 AM, Jack Cai  wrote:

> If you have time, you can write a script to transverse the Geronimo
> repository to get the version of all components and filter out
> Geronimo modules... :-)
>
> Thanks so much for putting together all the docs!
>
> -Jack
>
> On Tue, Dec 29, 2009 at 3:56 PM, chi runhua  wrote:
> > Hi devs, I noticed that G2.2 is released, congratulations~~!
> > Regarding G2.2 doc, I think most of pages were updated according to new
> > features and fixes in G2.2. You may refer to [1] for the status.
> > [1]
> >
> http://cwiki.apache.org/GMOxDOC22/apache-geronimo-v22-documentation-development-status.html
> > However, we still need to update one more page about components version
> in
> > G2.2, which is in [2]
> > [2]  http://cwiki.apache.org/GMOxDOC22/component-versions.html
> > Anyone knows how to generate these information in a smarter way or how we
> > did it for previous version?  So far the only way I can think of is to
> find
> > the version number of each component in all pom.xml files, while it's not
> so
> > efficient to me.
> > Thanks in advance.
> >
> > Jeff
> >
> >
>

Re: [Discussion] How about upgrade Dojo version to 1.4.0 for Geronimo 3.0?

[Rex Wang]

So far I can not find dojo 1.4.x in any public repo? However, i am agree for
this update in 3.0 once it done.

In G2.2, the portlets using dojo1.3.2 are ejb portlet and debug view
portlets, some portlets may need rewrite or remove in G3.0, such as
classloaders, ldap... So it is OK to make these changes and lib update all
in one step.

-Rex



2010/1/6 Delos 

> As I know, some new widgets are added and most of the widgets from old
> version are kept.
>
> I agree with Shawn, we can verify the pages once admin console in G 3.0 is
> ready.
>
> Thanks!
>
> 2010/1/6 Shawn Jiang 
>
> Agree , we should test the functions that were using old dojo to see if
>> they are still working after upgrading to dojo 1.4.0.
>>
>> On Wed, Jan 6, 2010 at 2:54 PM, Ivan  wrote:
>>
>>> Is the new version compatable with the old one ? If yes, I think we could
>>> upgrade it.
>>>
>>> 2010/1/6 Delos 
>>>
>>> Hi,

 Dojo 1.4.0 has released on Dec.15.  How about upgrade Dojo version to
 1.4.0 for Geronimo 3.0?

 Some new Widgets are provided, such as EnhancedDataGrid; meanswhile a
 lot of refactoring work makes it faster than before.

 BTW, for you to feel the improvement of Dojo 1.4.0, I have uploaded a
 demo of pluto 2.0 and Dojo 1.4.0 here
 https://svn.apache.org/repos/asf/geronimo/sandbox/delos/portlet+dojo/portlet-dojo1.4.0-demo.zip.


 Steps to run demo
 1. Extract the zip
 2. launch "bin/startup.sh" or bin/startup.bat"
 3. visit "http://localhost:8080/pluto/portal/BundlePage“, you will see
 a portlet showing OSGI bundles with dojo 1.4.0 widgets

 Upgrade to Dojo 1.4.0, any comments?

 Thanks!
 --
 Best Regards,

 Delos

>>>
>>>
>>>
>>> --
>>> Ivan
>>>
>>
>>
>>
>> --
>> Shawn
>>
>
>
>
> --
> Best Regards,
>
> Delos
>



-- 
Lei Wang (Rex)
rwonly AT apache.org

22 branch testsuite does not work.

[Shawn Jiang]

The testsuites did not get executed at all.  See:
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100102/logs-2000-jetty/test.log

[INFO] Scanning for projects...
[INFO] 
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 11 seconds
[INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
[INFO] Final Memory: 29M/565M
[INFO] 



-- 
Shawn

Re: [VOTE] GEP 2.2 release - RC1

[Shawn Jiang]

On Mon, Jan 4, 2010 at 10:00 PM, Delos  wrote:

> Hi everyone, Please review and vote on the release of the Geronimo Eclipse
> Plugin 2.2 RC1.
>
> The deployable zip file is here:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
>
> The update site zip file is here:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
>
> The current svn location is here (revision number 894784):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
>
> The future svn location will be here (when approved):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
>
> If you would like to review and/or comment on the release notes, they are
> here:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.2.txt
>


This file is not available, please correct it.
Not Found

The requested URL
/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.2.txt
was not found on this server.
--
Apache/2.2.13 (Unix) DAV/2 mod_ssl/2.2.13 OpenSSL/0.9.8e Server at
people.apache.org Port 80



>
> 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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
>
> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>
> Finally, I've created a Staging Site that can be used to test the update
> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for
> downloading the GEP itself. This is also documented in the instructions, but
> you must use the staging site created for this vote at:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
>
> Please let me know if there are any questions and/or problems. The vote is
> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM ET.
>
> [ ] +1  Release Geronimo Eclipse Plugin 2.2
> [ ] +0  No opinion
> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
>
> Thanks in advance!
>
> --
> Best Regards,
>
> Delos
>



-- 
Shawn

Re: 22 branch testsuite does not work.

[Shawn Jiang]

The testsuite was turned off by default unless running the build with mvn
-Pit   in [1],  But seems the build script in build system was not updated
for this change.

[1]
https://svn.apache.org/repos/asf/geronimo/server/branches/2.2/testsuite/pom.xml
(Rev.832538)



On Wed, Jan 6, 2010 at 4:57 PM, Shawn Jiang  wrote:

> The testsuites did not get executed at all.  See:
> http://people.apache.org/builds/geronimo/server/binaries/2.2/20100102/logs-2000-jetty/test.log
>
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Building Geronimo TestSuite
> [INFO]task-segment: [install]
> [INFO] 
> 
>
> [INFO] [genesis:validate-configuration {execution: default}]
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] Setting property: classpath.resource.loader.class => 
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
>
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>
> [INFO] [remote-resources:process {execution: default}]
> [INFO] [site:attach-descriptor]
> [INFO] [ianal:verify-legal-files {execution: default}]
> [INFO] [install:install]
> [INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to 
> /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom
>
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 11 seconds
>
> [INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
> [INFO] Final Memory: 29M/565M
> [INFO] 
> 
>
>
>
> --
> Shawn
>



-- 
Shawn

-EA- in the jee6 spec versions.

[Rick McGuire]

I believe the JEE6 specs have finally gone final.  When would be the 
appropriate time to remove the -EA- indicator from the Geronimo spec jar 
versions?


Rick

[jira] Commented: (GERONIMO-4896) Commands to a Secure JMX Connector require the SSL keyStorePassword to be specified on command line

[Ashish Jain (JIRA)]

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

Ashish Jain commented on GERONIMO-4896:
---

Uploading a patch. 
Using this approach you only need to specify keystore location and truststore 
location. something as follows

set 
JAVA_OPTS=-Djavax.net.ssl.keyStore=%GERONIMO_HOME%/var/security/keystore
s/geronimo-default  
-Djavax.net.ssl.trustStore=%GERONIMO_HOME%/var/security/keystores/geroni
mo-default

Once done run a test as follows
deploy.bat --secure list-modules 

you will be prompted for truststore password and keystore password.


> Commands to a Secure JMX Connector require the SSL keyStorePassword to be 
> specified on command line
> ---
>
> Key: GERONIMO-4896
> URL: https://issues.apache.org/jira/browse/GERONIMO-4896
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.5, 2.2, 3.0
>Reporter: Kevan Miller
>Assignee: Ashish Jain
> Fix For: 2.1.5, 3.0, Wish List
>
> Attachments: JavaAgent.jar, JvmOpts.java
>
>
> To my knowledge, it is not possible to run a Geronimo command (e.g. deploy.sh 
> deploy or gsh geronimo/stop-server) to a server with a secure JMX Connector 
> (running SSL, without specifying the following Java system properties on the 
> command line:
>javax.net.ssl.keyStore and javax.net.ssl.keyStorePassword
> For example:
> {code}
> export GERONIMO_HOME=~/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
> export 
> JAVA_OPTS="-Djavax.net.ssl.keyStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
>  -Djavax.net.ssl.keyStorePassword=secret 
> -Djavax.net.ssl.trustStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
>  -Djavax.net.ssl.trustStorePassword=secret"
> $GERONIMO_HOME/bin/deploy.sh -u system -p manager --secure list-modules 
> --stopped
> {code}
> javax.net.ssl.keyStorePassword causes a problem, since this means the 
> keyStorePassword is available, in-the-clear, to someone inspecting executing 
> processes. For example while a deploy command was active, someone could run 
> 'ps auxww | grep deployer.jar' and discover the keyStorePassword for the 
> KeyStore.
> Geronimo should provide a mechanism, whereby users can specify the 
> keyStorePassword without making that secret available to anyone inspecting 
> processes running on the current system. Ideally, the password could be 
> encrypted/obfuscated within a file (just as passwords can be 
> encrypted/obfuscated in var/config/config.xml).

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

[jira] Updated: (GERONIMO-4896) Commands to a Secure JMX Connector require the SSL keyStorePassword to be specified on command line

[Ashish Jain (JIRA)]

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

Ashish Jain updated GERONIMO-4896:
--

Attachment: 4896.patch

> Commands to a Secure JMX Connector require the SSL keyStorePassword to be 
> specified on command line
> ---
>
> Key: GERONIMO-4896
> URL: https://issues.apache.org/jira/browse/GERONIMO-4896
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.5, 2.2, 3.0
>Reporter: Kevan Miller
>Assignee: Ashish Jain
> Fix For: 2.1.5, 3.0, Wish List
>
> Attachments: 4896.patch, JavaAgent.jar, JvmOpts.java
>
>
> To my knowledge, it is not possible to run a Geronimo command (e.g. deploy.sh 
> deploy or gsh geronimo/stop-server) to a server with a secure JMX Connector 
> (running SSL, without specifying the following Java system properties on the 
> command line:
>javax.net.ssl.keyStore and javax.net.ssl.keyStorePassword
> For example:
> {code}
> export GERONIMO_HOME=~/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
> export 
> JAVA_OPTS="-Djavax.net.ssl.keyStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
>  -Djavax.net.ssl.keyStorePassword=secret 
> -Djavax.net.ssl.trustStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
>  -Djavax.net.ssl.trustStorePassword=secret"
> $GERONIMO_HOME/bin/deploy.sh -u system -p manager --secure list-modules 
> --stopped
> {code}
> javax.net.ssl.keyStorePassword causes a problem, since this means the 
> keyStorePassword is available, in-the-clear, to someone inspecting executing 
> processes. For example while a deploy command was active, someone could run 
> 'ps auxww | grep deployer.jar' and discover the keyStorePassword for the 
> KeyStore.
> Geronimo should provide a mechanism, whereby users can specify the 
> keyStorePassword without making that secret available to anyone inspecting 
> processes running on the current system. Ideally, the password could be 
> encrypted/obfuscated within a file (just as passwords can be 
> encrypted/obfuscated in var/config/config.xml).

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

[jira] Assigned: (GERONIMO-5006) Documentation: Tomcat native clustering for geronimo 2.1

[Ashish Jain (JIRA)]

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

Ashish Jain reassigned GERONIMO-5006:
-

Assignee: Ashish Jain

> Documentation: Tomcat native clustering for geronimo 2.1
> 
>
> Key: GERONIMO-5006
> URL: https://issues.apache.org/jira/browse/GERONIMO-5006
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5
>Reporter: Ashish Jain
>Assignee: Ashish Jain
>
> No documentation for tomcat native clustering for geronimo 2.1.x

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

[jira] Closed: (GERONIMO-5006) Documentation: Tomcat native clustering for geronimo 2.1

[Ashish Jain (JIRA)]

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

Ashish Jain closed GERONIMO-5006.
-

Resolution: Fixed

> Documentation: Tomcat native clustering for geronimo 2.1
> 
>
> Key: GERONIMO-5006
> URL: https://issues.apache.org/jira/browse/GERONIMO-5006
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: documentation
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5
>Reporter: Ashish Jain
>Assignee: Ashish Jain
>
> No documentation for tomcat native clustering for geronimo 2.1.x

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

Re: [VOTE] GEP 2.2 release - RC1

[Kevan Miller]

I scanned the source with RAT and found a number of issues. They must be fixed 
prior to a release. So, here's my -1.

The following files are missing apache source license headers. Most of them 
will require a header.

 !? ./plugins/about.html
 !? ./plugins/org.apache.geronimo.st.core/schema/JAXBUtilsProvider.exsd
 !? 
./plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/jaxb/IJAXBUtilsProvider.java
 !? 
./plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/operations/GeronimoAccountManager.java
 !? 
./plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/refactoring/DeploymentPlanEditHelper.java
 !? 
./plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/refactoring/DeploymentPlanHandler.java
 !? 
./plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/refactoring/DeploymentPlanTextNode.java
 !? 
./plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/refactoring/GeronimoProjectRenameParticipant.java
 !? 
./plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/refactoring/MovedTextFileChange.java
 !? 
./plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/wizards/ManageAccountWizard.java
 !? 
./plugins/org.apache.geronimo.st.v21.ui/src/main/java/org/apache/geronimo/st/v21/ui/sections/DBPoolSection.java
 !? 
./plugins/org.apache.geronimo.st.v21.ui/src/main/java/org/apache/geronimo/st/v21/ui/sections/SecurityRealmSection.java
 !? 
./plugins/org.apache.geronimo.st.v21.ui/src/main/java/org/apache/geronimo/st/v21/ui/wizards/DBPoolWizard.java
 !? 
./plugins/org.apache.geronimo.st.v21.ui/src/main/java/org/apache/geronimo/st/v21/ui/wizards/SecurityRealmWizard.java
 !? 
./testsuite/plugins/org.apache.geronimo.testsuite.v22/schema/testCases.exsd

It looks like a number of new files do not have the svn property 
eol-style=native. They show up on my system with DOS CR/LF chars. Please see 
http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html for 
information about configuring your svn client. Fixing these files is not 
mandatory, but is a good idea. 

I'm running a test build, now. Will also test installation.

--kevan

On Jan 4, 2010, at 9:00 AM, Delos wrote:

> Hi everyone, Please review and vote on the release of the Geronimo Eclipse 
> Plugin 2.2 RC1.
> 
> The deployable zip file is here:
> 
> >http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
> 
> The update site zip file is here:
> 
> > 
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
> 
> The current svn location is here (revision number 894784):
> 
> > 
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
> 
> The future svn location will be here (when approved):
> 
> > 
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
> 
> If you would like to review and/or comment on the release notes, they are 
> here:
> 
> > 
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
> 
> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
> 
> Finally, I've created a Staging Site that can be used to test the update 
> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for 
> downloading the GEP itself. This is also documented in the instructions, but 
> you must use the staging site created for this vote at:
> 
> > 
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
> 
> Please let me know if there are any questions and/or problems. The vote is 
> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM ET.
> 
> [ ] +1  Release Geronimo Eclipse Plugin 2.2
> [ ] +0  No opinion
> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
> 
> Thanks in advance!
> 
> -- 
> Best Regards,
> 
> Delos

Versioning of geronimo-annotation spec jar

[Rick McGuire]

The Geronimo version of the common-annotations spec jar carries a 
geronimo-annotation_1.0-MR1_spec version name.  I'm assuming this is 
really the 1.1 annotations spec based on the internal name defined in 
the POM.  In the JEE 6 specifications, this version is properly 
identified as Common annotations 1.1.  I'm guessing that if I'm feeling 
some confusion on whether this was the correct jar that others should as 
well.  Shouldn't this be renamed?


I notice that the trunk version is still using 
geronimo-annotation_1.0-1.1.1.  I'd like to uplevel this to the JEE6 
version, but think I'd like to get a consensus on the naming issue first.


Rick

[BUILD] trunk: Failed for Revision: 895628

[gawor]

Geronimo Revision: 895628 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100106/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100106/unit-test-reports
 
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 97 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/target/classes
[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelMBeanServer.java:[401,29]
 [deprecation] deserialize(java.lang.String,javax.management.ObjectName,byte[]) 
in javax.management.MBeanServer has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelMBeanServer.java:[405,29]
 [deprecation] deserialize(java.lang.String,byte[]) in 
javax.management.MBeanServer has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelMBeanServer.java:[409,29]
 [deprecation] deserialize(javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[534,18]
 [deprecation] 
invoke(javax.management.ObjectName,java.lang.String,java.lang.Object[],java.lang.String[])
 in org.apache.geronimo.kernel.Kernel has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[514,18]
 [deprecation] invoke(javax.management.ObjectName,java.lang.String) in 
org.apache.geronimo.kernel.Kernel has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[478,18]
 [deprecation] getAttribute(javax.management.ObjectName,java.lang.String) in 
org.apache.geronimo.kernel.Kernel has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[664,29]
 [deprecation] listGBeans(javax.management.ObjectName) in 
org.apache.geronimo.kernel.Kernel has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[604,21]
 [deprecation] getGBeanInfo(javax.management.ObjectName) in 
org.apache.geronimo.kernel.Kernel has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[370,15]
 [deprecation] getGBeanState(javax.management.ObjectName) in 
org.apache.geronimo.kernel.Kernel has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/jmx/KernelDelegate.java:[69,18]
 [deprecation] getGBean(javax.management.ObjectName) in 
org.apache.geronimo.kernel.Kernel has been deprecated

[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 13 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@4ff04ff0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@4ff04ff0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@43f643f6
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-system/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.system.serverinfo.ServerInfoTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.689 sec
Running 
org.apache.geronimo.system.configuration.condition.JexlExpressionParserTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.085 sec
Running 
org.apache.geronimo.system.configuration.condition.JexlConditionParserTest
Tests

Re: [VOTE] GEP 2.2 release - RC1

[Kevan Miller]

Built fine. I also downloaded update site. Installed ok and simple tests looked 
fine. So, other than problems already noted, looks ok to me...

--kevan
On Jan 4, 2010, at 9:00 AM, Delos wrote:

> Hi everyone, Please review and vote on the release of the Geronimo Eclipse 
> Plugin 2.2 RC1.
> 
> The deployable zip file is here:
> 
> >http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
> 
> The update site zip file is here:
> 
> > 
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
> 
> The current svn location is here (revision number 894784):
> 
> > 
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
> 
> The future svn location will be here (when approved):
> 
> > 
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
> 
> If you would like to review and/or comment on the release notes, they are 
> here:
> 
> > 
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
> 
> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
> 
> Finally, I've created a Staging Site that can be used to test the update 
> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for 
> downloading the GEP itself. This is also documented in the instructions, but 
> you must use the staging site created for this vote at:
> 
> > 
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
> 
> Please let me know if there are any questions and/or problems. The vote is 
> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM ET.
> 
> [ ] +1  Release Geronimo Eclipse Plugin 2.2
> [ ] +0  No opinion
> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
> 
> Thanks in advance!
> 
> -- 
> Best Regards,
> 
> Delos

Re: Versioning of geronimo-annotation spec jar

[David Jencks]

On Jan 6, 2010, at 7:23 AM, Rick McGuire wrote:

The Geronimo version of the common-annotations spec jar carries a  
geronimo-annotation_1.0-MR1_spec version name.  I'm assuming this is  
really the 1.1 annotations spec based on the internal name defined  
in the POM.  In the JEE 6 specifications, this version is properly  
identified as Common annotations 1.1.  I'm guessing that if I'm  
feeling some confusion on whether this was the correct jar that  
others should as well.  Shouldn't this be renamed?


I notice that the trunk version is still using geronimo- 
annotation_1.0-1.1.1.  I'd like to uplevel this to the JEE6 version,  
but think I'd like to get a consensus on the naming issue first.


I think you'd have to do some svn research to try to figure out what  
is actually in the current project, but if the ee6 spec calls it 1.1  
then we should copy the specs/trunk project to geronimo- 
annotation_1.1_spec and probably start over with the versions at 1.0- 
SNAPSHOT.


Thanks for keeping track of the spec versions :-)  There are probably  
others that need to be updated for ee6, if you find more please ping  
the dev list and update the names.


david jencks


Rick

Re: [Discussion] How about upgrade Dojo version to 1.4.0 for Geronimo 3.0?

[Jay D. McHugh]

I asked on the Dojo mailing list to see if someone was going to deploy a
current version (1.4.0) out to a public repo - but since 12/15/09 there
has not been any response.

Maybe if someone else asked too...

Jay

Rex Wang wrote:
> So far I can not find dojo 1.4.x in any public repo? However, i am agree
> for this update in 3.0 once it done.
> 
> In G2.2, the portlets using dojo1.3.2 are ejb portlet and debug view
> portlets, some portlets may need rewrite or remove in G3.0, such as
> classloaders, ldap... So it is OK to make these changes and lib update
> all in one step.
> 
> -Rex
> 
> 
> 
> 2010/1/6 Delos mailto:dait...@gmail.com>>
> 
> As I know, some new widgets are added and most of the widgets from
> old version are kept.
> 
> I agree with Shawn, we can verify the pages once admin console in G
> 3.0 is ready.
> 
> Thanks!
> 
> 2010/1/6 Shawn Jiang mailto:genspr...@gmail.com>>
> 
> Agree , we should test the functions that were using old dojo to
> see if they are still working after upgrading to dojo 1.4.0. 
> 
> On Wed, Jan 6, 2010 at 2:54 PM, Ivan  > wrote:
> 
> Is the new version compatable with the old one ? If yes, I
> think we could upgrade it.
> 
> 2010/1/6 Delos mailto:dait...@gmail.com>>
> 
> Hi,
> 
> Dojo 1.4.0 has released on Dec.15.  How about upgrade
> Dojo version to 1.4.0 for Geronimo 3.0?
> 
> Some new Widgets are provided, such as EnhancedDataGrid;
> meanswhile a lot of refactoring work makes it faster
> than before.
> 
> BTW, for you to feel the improvement of Dojo 1.4.0, I
> have uploaded a demo of pluto 2.0 and Dojo 1.4.0 here
> 
> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/portlet+dojo/portlet-dojo1.4.0-demo.zip.
> 
> 
> Steps to run demo
> 1. Extract the zip
> 2. launch "bin/startup.sh" or bin/startup.bat"
> 3. visit
> "http://localhost:8080/pluto/portal/BundlePage“, you
> will see a portlet showing OSGI bundles with dojo 1.4.0
> widgets
> 
> Upgrade to Dojo 1.4.0, any comments?
> 
> Thanks!
> -- 
> Best Regards,
> 
> Delos
> 
> 
> 
> 
> -- 
> Ivan
> 
> 
> 
> 
> -- 
> Shawn
> 
> 
> 
> 
> -- 
> Best Regards,
> 
> Delos
> 
> 
> 
> 
> -- 
> Lei Wang (Rex)
> rwonly AT apache.org 

Re: -EA- in the jee6 spec versions.

[Donald Woods]

Already updated the jpa2 and bean validation spec APIs to 
version=1.0-SNAPSHOT.  Just waiting on our JPA 2.0 TCK testing with 
OpenJPA to progress a little more before creating a release candidate 
for the JPA spec.



-Donald


Rick McGuire wrote:
I believe the JEE6 specs have finally gone final.  When would be the 
appropriate time to remove the -EA- indicator from the Geronimo spec jar 
versions?


Rick

[BUILD] trunk: Failed for Revision: 896648

[gawor]

Geronimo Revision: 896648 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100106/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100106/unit-test-reports
 
for artifact: 
  org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo2.maven.org/maven2)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo2.maven.org/maven2)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo2.maven.org/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360)
at

Re: [VOTE] GEP 2.2 release - RC1

[Delos]

Thanks for your comments!

I will correct the URL and add the missing headers for some files. Then, I
will raise a vote for RC2.

2010/1/7 Kevan Miller 

> Built fine. I also downloaded update site. Installed ok and simple tests
> looked fine. So, other than problems already noted, looks ok to me...
>
> --kevan
>
> On Jan 4, 2010, at 9:00 AM, Delos wrote:
>
> Hi everyone, Please review and vote on the release of the Geronimo Eclipse
> Plugin 2.2 RC1.
>
> The deployable zip file is here:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
>
> The update site zip file is here:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
>
> The current svn location is here (revision number 894784):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
>
> The future svn location will be here (when approved):
>
> >
> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
>
> If you would like to review and/or comment on the release notes, they are
> here:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
>
> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>
> Finally, I've created a Staging Site that can be used to test the update
> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for
> downloading the GEP itself. This is also documented in the instructions, but
> you must use the staging site created for this vote at:
>
> >
> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
>
> Please let me know if there are any questions and/or problems. The vote is
> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM ET.
>
> [ ] +1  Release Geronimo Eclipse Plugin 2.2
> [ ] +0  No opinion
> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
>
> Thanks in advance!
>
> --
> Best Regards,
>
> Delos
>
>
>


-- 
Best Regards,

Delos

Re: [VOTE] GEP 2.2 release - RC1

[Shawn Jiang]

If it's possible, I would like the format of the JIRA list in release notes
get cleaned up before the RC2.

On Thu, Jan 7, 2010 at 8:22 AM, Delos  wrote:

> Thanks for your comments!
>
> I will correct the URL and add the missing headers for some files. Then, I
> will raise a vote for RC2.
>
> 2010/1/7 Kevan Miller 
>
> Built fine. I also downloaded update site. Installed ok and simple tests
>> looked fine. So, other than problems already noted, looks ok to me...
>>
>> --kevan
>>
>> On Jan 4, 2010, at 9:00 AM, Delos wrote:
>>
>> Hi everyone, Please review and vote on the release of the Geronimo
>> Eclipse Plugin 2.2 RC1.
>>
>> The deployable zip file is here:
>>
>> >
>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
>>
>> The update site zip file is here:
>>
>> >
>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
>>
>> The current svn location is here (revision number 894784):
>>
>> >
>> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
>>
>> The future svn location will be here (when approved):
>>
>> >
>> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
>>
>> If you would like to review and/or comment on the release notes, they are
>> here:
>>
>> >
>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
>>
>> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>>
>> Finally, I've created a Staging Site that can be used to test the update
>> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for
>> downloading the GEP itself. This is also documented in the instructions, but
>> you must use the staging site created for this vote at:
>>
>> >
>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
>>
>> Please let me know if there are any questions and/or problems. The voteis 
>> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM
>> ET.
>>
>> [ ] +1  Release Geronimo Eclipse Plugin 2.2
>> [ ] +0  No opinion
>> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
>>
>> Thanks in advance!
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>>
>>
>
>
> --
> Best Regards,
>
> Delos
>



-- 
Shawn

[jira] Reopened: (GERONIMODEVTOOLS-496) GEP 2.1.2 cannot be uninstalled through P2 in Ganymede

[Delos Dai (JIRA)]

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

Delos Dai reopened GERONIMODEVTOOLS-496:


  Assignee: Delos Dai  (was: Tim McConnell)

> GEP 2.1.2 cannot be uninstalled through P2 in Ganymede
> --
>
> Key: GERONIMODEVTOOLS-496
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-496
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
> Environment: Windows XP SP2
> Eclipse Ganymede
> GEP 2.1.2
>Reporter: Forrest Xia
>Assignee: Delos Dai
>Priority: Minor
> Fix For: 2.2.0
>
>
> Steps:
> 1. Install GEP 2.1.2 through "Software Updates..."
> 2. Restart Ganymede to confirm installation is ok, and try to define a server 
> runtime to launch server from eclipse, it's ok as well
> 3. Remove server runtime and uninstall GEP 2.1.2, then restart Ganymede
> 4. Check available server adapters, no Geronimo server adapter found, check 
> feature list in "Software Update...", not found. At here, seems the GEP is 
> uninstalled successfully
> 5. Check Ganymede directory, however found some GEP plugins jar files are 
> still there
> So the uninstall function does not work for GEP 2.1.2 in Ganymede.

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

[jira] Closed: (GERONIMODEVTOOLS-496) GEP 2.1.2 cannot be uninstalled through P2 in Ganymede

[Delos Dai (JIRA)]

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

Delos Dai closed GERONIMODEVTOOLS-496.
--

Resolution: Won't Fix

> GEP 2.1.2 cannot be uninstalled through P2 in Ganymede
> --
>
> Key: GERONIMODEVTOOLS-496
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-496
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
> Environment: Windows XP SP2
> Eclipse Ganymede
> GEP 2.1.2
>Reporter: Forrest Xia
>Assignee: Delos Dai
>Priority: Minor
> Fix For: 2.2.0
>
>
> Steps:
> 1. Install GEP 2.1.2 through "Software Updates..."
> 2. Restart Ganymede to confirm installation is ok, and try to define a server 
> runtime to launch server from eclipse, it's ok as well
> 3. Remove server runtime and uninstall GEP 2.1.2, then restart Ganymede
> 4. Check available server adapters, no Geronimo server adapter found, check 
> feature list in "Software Update...", not found. At here, seems the GEP is 
> uninstalled successfully
> 5. Check Ganymede directory, however found some GEP plugins jar files are 
> still there
> So the uninstall function does not work for GEP 2.1.2 in Ganymede.

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

[jira] Reopened: (GERONIMODEVTOOLS-497) GEP 2.1.2 installed through "Download additional server adapters" should be uninstallable through Ganymede P2

[Delos Dai (JIRA)]

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

Delos Dai reopened GERONIMODEVTOOLS-497:


  Assignee: Delos Dai  (was: Tim McConnell)

> GEP 2.1.2 installed through "Download additional server adapters" should be 
> uninstallable through Ganymede P2
> -
>
> Key: GERONIMODEVTOOLS-497
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-497
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
> Environment: OS: Windows XP SP2
> Eclipse: Ganymede JEE package
> SDK: IBM SDK 5 SR6b
> GEP: 2.1.2
>Reporter: Forrest Xia
>Assignee: Delos Dai
>Priority: Minor
> Fix For: 2.2.0
>
>
> Steps:
> 1. Start a clean ganymede, click "Windows->Preferences->Runtime 
> environments->Add...->Download additional server adapters" to install GEP 
> 2.1.2
> 2. After installed, try to uninstall through "Software Updates..."
> Symptom:
> Uninstall button is grayed for GEP 2.1.2, so no way to uninstall it.

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

[jira] Closed: (GERONIMODEVTOOLS-497) GEP 2.1.2 installed through "Download additional server adapters" should be uninstallable through Ganymede P2

[Delos Dai (JIRA)]

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

Delos Dai closed GERONIMODEVTOOLS-497.
--

Resolution: Won't Fix

> GEP 2.1.2 installed through "Download additional server adapters" should be 
> uninstallable through Ganymede P2
> -
>
> Key: GERONIMODEVTOOLS-497
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-497
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
> Environment: OS: Windows XP SP2
> Eclipse: Ganymede JEE package
> SDK: IBM SDK 5 SR6b
> GEP: 2.1.2
>Reporter: Forrest Xia
>Assignee: Delos Dai
>Priority: Minor
> Fix For: 2.2.0
>
>
> Steps:
> 1. Start a clean ganymede, click "Windows->Preferences->Runtime 
> environments->Add...->Download additional server adapters" to install GEP 
> 2.1.2
> 2. After installed, try to uninstall through "Software Updates..."
> Symptom:
> Uninstall button is grayed for GEP 2.1.2, so no way to uninstall it.

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

Re: [VOTE] GEP 2.2 release - RC1

[Delos]

The spaces cause format problem in browser.I will reformat the JIRA list.

2010/1/7 Shawn Jiang 

> If it's possible, I would like the format of the JIRA list in release notes
> get cleaned up before the RC2.
>
>
> On Thu, Jan 7, 2010 at 8:22 AM, Delos  wrote:
>
>> Thanks for your comments!
>>
>> I will correct the URL and add the missing headers for some files. Then, I
>> will raise a vote for RC2.
>>
>> 2010/1/7 Kevan Miller 
>>
>> Built fine. I also downloaded update site. Installed ok and simple tests
>>> looked fine. So, other than problems already noted, looks ok to me...
>>>
>>> --kevan
>>>
>>> On Jan 4, 2010, at 9:00 AM, Delos wrote:
>>>
>>> Hi everyone, Please review and vote on the release of the Geronimo
>>> Eclipse Plugin 2.2 RC1.
>>>
>>> The deployable zip file is here:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip
>>>
>>> The update site zip file is here:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip
>>>
>>> The current svn location is here (revision number 894784):
>>>
>>> >
>>> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2
>>>
>>> The future svn location will be here (when approved):
>>>
>>> >
>>> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2
>>>
>>> If you would like to review and/or comment on the release notes, they are
>>> here:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.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://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html
>>>
>>> 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/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html
>>>
>>> Finally, I've created a Staging Site that can be used to test the update
>>> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for
>>> downloading the GEP itself. This is also documented in the instructions, but
>>> you must use the staging site created for this vote at:
>>>
>>> >
>>> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/
>>>
>>> Please let me know if there are any questions and/or problems. The voteis 
>>> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM
>>> ET.
>>>
>>> [ ] +1  Release Geronimo Eclipse Plugin 2.2
>>> [ ] +0  No opinion
>>> [ ] -1  Don't release Geronimo Eclipse Plugin 2.2
>>>
>>> Thanks in advance!
>>>
>>> --
>>> Best Regards,
>>>
>>> Delos
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
>
> --
> Shawn
>



-- 
Best Regards,

Delos

[BUILD] trunk: Failed for Revision: 896733

[gawor]

Geronimo Revision: 896733 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100107/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100107/unit-test-reports
 
for artifact: 
  org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo2.maven.org/maven2),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo2.maven.org/maven2),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=axis -Dversion=1.4_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:axis:jar:1.4_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-webservices:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo2.maven.org/maven2),
  ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360)
at 
org.apach

Re: 22 branch testsuite does not work.

[Jarek Gawor]

Thanks Shawn for catching this! I wasn't aware of this change. Now we
have 3 different ways of running the tests in 4 different branches.
Anyway, I'll try to update the test scripts.

Thanks again,
Jarek

On Wed, Jan 6, 2010 at 4:56 AM, Shawn Jiang  wrote:
> The testsuite was turned off by default unless running the build with mvn
> -Pit   in [1],  But seems the build script in build system was not updated
> for this change.
>
> [1]https://svn.apache.org/repos/asf/geronimo/server/branches/2.2/testsuite/pom.xml
> (Rev.832538)
>
>
>
> On Wed, Jan 6, 2010 at 4:57 PM, Shawn Jiang  wrote:
>>
>> The testsuites did not get executed at all.  See:
>> http://people.apache.org/builds/geronimo/server/binaries/2.2/20100102/logs-2000-jetty/test.log
>>
>> [INFO] Scanning for projects...
>> [INFO]
>> 
>> [INFO] Building Geronimo TestSuite
>> [INFO]task-segment: [install]
>> [INFO]
>> 
>>
>>
>> [INFO] [genesis:validate-configuration {execution: default}]
>> [INFO] [enforcer:enforce {execution: default}]
>> [INFO] Setting property: classpath.resource.loader.class =>
>> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
>>
>>
>> [INFO] Setting property: velocimacro.messages.on => 'false'.
>> [INFO] Setting property: resource.loader => 'classpath'.
>> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>>
>>
>> [INFO] [remote-resources:process {execution: default}]
>> [INFO] [site:attach-descriptor]
>> [INFO] [ianal:verify-legal-files {execution: default}]
>> [INFO] [install:install]
>> [INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
>> /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom
>>
>>
>> [INFO]
>> 
>> [INFO] BUILD SUCCESSFUL
>> [INFO]
>> 
>> [INFO] Total time: 11 seconds
>>
>>
>> [INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
>> [INFO] Final Memory: 29M/565M
>> [INFO]
>> 
>>
>>
>> --
>> Shawn
>
>
>
> --
> Shawn
>

Re: 22 branch testsuite does not work.

[Shawn Jiang]

I'm afraid that we can't run the testsuites successfully even with the
correct script due to existing bugs of the updated pom.

I'm trying to fix the bugs with
https://issues.apache.org/jira/browse/GERONIMO-5015.

On Thu, Jan 7, 2010 at 2:52 PM, Jarek Gawor  wrote:

> Thanks Shawn for catching this! I wasn't aware of this change. Now we
> have 3 different ways of running the tests in 4 different branches.
> Anyway, I'll try to update the test scripts.
>
> Thanks again,
> Jarek
>
> On Wed, Jan 6, 2010 at 4:56 AM, Shawn Jiang  wrote:
> > The testsuite was turned off by default unless running the build with mvn
> > -Pit   in [1],  But seems the build script in build system was not
> updated
> > for this change.
> >
> > [1]
> https://svn.apache.org/repos/asf/geronimo/server/branches/2.2/testsuite/pom.xml
> > (Rev.832538)
> >
> >
> >
> > On Wed, Jan 6, 2010 at 4:57 PM, Shawn Jiang  wrote:
> >>
> >> The testsuites did not get executed at all.  See:
> >>
> http://people.apache.org/builds/geronimo/server/binaries/2.2/20100102/logs-2000-jetty/test.log
> >>
> >> [INFO] Scanning for projects...
> >> [INFO]
> >> 
> >> [INFO] Building Geronimo TestSuite
> >> [INFO]task-segment: [install]
> >> [INFO]
> >> 
> >>
> >>
> >> [INFO] [genesis:validate-configuration {execution: default}]
> >> [INFO] [enforcer:enforce {execution: default}]
> >> [INFO] Setting property: classpath.resource.loader.class =>
> >> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> >>
> >>
> >> [INFO] Setting property: velocimacro.messages.on => 'false'.
> >> [INFO] Setting property: resource.loader => 'classpath'.
> >> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> >>
> >>
> >> [INFO] [remote-resources:process {execution: default}]
> >> [INFO] [site:attach-descriptor]
> >> [INFO] [ianal:verify-legal-files {execution: default}]
> >> [INFO] [install:install]
> >> [INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
> >>
> /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom
> >>
> >>
> >> [INFO]
> >> 
> >> [INFO] BUILD SUCCESSFUL
> >> [INFO]
> >> 
> >> [INFO] Total time: 11 seconds
> >>
> >>
> >> [INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
> >> [INFO] Final Memory: 29M/565M
> >> [INFO]
> >> 
> >>
> >>
> >> --
> >> Shawn
> >
> >
> >
> > --
> > Shawn
> >
>



-- 
Shawn

[jira] Created: (GERONIMO-5015) The testsuite is not working.

[Shawn Jiang (JIRA)]

The testsuite is not working.
-

 Key: GERONIMO-5015
 URL: https://issues.apache.org/jira/browse/GERONIMO-5015
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2, 2.2.1
 Environment: windows XP + sun jdk 1.6.0
Reporter: Shawn Jiang


The testsuites did not get executed at all.  

[INFO] Scanning for projects...
[INFO] 
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO] 

[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class => 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.

[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.

[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom

[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 11 seconds

[INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
[INFO] Final Memory: 29M/565M
[INFO] 

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

[jira] Issue Comment Edited: (GERONIMO-5015) The testsuite is not working.

[Shawn Jiang (JIRA)]

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

Shawn Jiang edited comment on GERONIMO-5015 at 1/7/10 7:26 AM:
---

The correct execute command should be mvn -Pit,all-subprojects according to the 
comments in the testsute/pom.xml.but it does not work too with a error that 
selenium server is not started up.  

The previous default profile is not active after we specify the profile -Pit 
explicitly so that no selenium server is started up.

  was (Author: genspring):
The correct execute command should be mvn -Pit,all-subprojects according to 
the comments in the testsute/pom.xml.but it does not work too with a error 
that selenium server is not started up.  

The previous default profile is not active after we specify the profile -Pit 
explicitly so that on selenium server is started up.
  
> The testsuite is not working.
> -
>
> Key: GERONIMO-5015
> URL: https://issues.apache.org/jira/browse/GERONIMO-5015
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2, 2.2.1
> Environment: windows XP + sun jdk 1.6.0
>Reporter: Shawn Jiang
>
> The testsuites did not get executed at all.  
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Building Geronimo TestSuite
> [INFO]task-segment: [install]
> [INFO] 
> 
> [INFO] [genesis:validate-configuration {execution: default}]
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] Setting property: classpath.resource.loader.class => 
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [remote-resources:process {execution: default}]
> [INFO] [site:attach-descriptor]
> [INFO] [ianal:verify-legal-files {execution: default}]
> [INFO] [install:install]
> [INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to 
> /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 11 seconds
> [INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
> [INFO] Final Memory: 29M/565M
> [INFO] 
> 

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

[jira] Commented: (GERONIMO-5015) The testsuite is not working.

[Shawn Jiang (JIRA)]

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

Shawn Jiang commented on GERONIMO-5015:
---

The correct execute command should be mvn -Pit,all-subprojects according to the 
comments in the testsute/pom.xml.but it does not work too with a error that 
selenium server is not started up.  

The previous default profile is not active after we specify the profile -Pit 
explicitly so that on selenium server is started up.

> The testsuite is not working.
> -
>
> Key: GERONIMO-5015
> URL: https://issues.apache.org/jira/browse/GERONIMO-5015
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2, 2.2.1
> Environment: windows XP + sun jdk 1.6.0
>Reporter: Shawn Jiang
>
> The testsuites did not get executed at all.  
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Building Geronimo TestSuite
> [INFO]task-segment: [install]
> [INFO] 
> 
> [INFO] [genesis:validate-configuration {execution: default}]
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] Setting property: classpath.resource.loader.class => 
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [remote-resources:process {execution: default}]
> [INFO] [site:attach-descriptor]
> [INFO] [ianal:verify-legal-files {execution: default}]
> [INFO] [install:install]
> [INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to 
> /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.1-SNAPSHOT/testsuite-2.2.1-SNAPSHOT.pom
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 11 seconds
> [INFO] Finished at: Sat Jan 02 04:53:35 EST 2010
> [INFO] Final Memory: 29M/565M
> [INFO] 
> 

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