date:20130528

[jira] [Created] (GERONIMO-6470) Enable the tomcat feature to Modify Apache-Coyote/1.1 Banner

2013-05-28 Thread xiezhi (JIRA)

xiezhi created GERONIMO-6470:


 Summary: Enable the tomcat feature to Modify Apache-Coyote/1.1 
Banner
 Key: GERONIMO-6470
 URL: https://issues.apache.org/jira/browse/GERONIMO-6470
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Tomcat
Affects Versions: 1.x
Reporter: xiezhi
Priority: Minor


In Response Headers, it exposure the version number of the Apache Tomcat Web 
Server which runs on port 8080 by default.
We hope to modify the TomcatWebConnector'attribute server to protect this 
information.
I think the good pratice is below.

In \var\config\config.xml
  

  name=Geronimo
  





  0.0.0.0
  8080
  8443
  2048
  150
  100
  -1
  true
  25
  75
  8192
  false
  2
  false
  2097152
  4096
  false
  TestResponseHead



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

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Rex Wang

thanks and +1


2013/5/27 Forrest Xia 

> +1 myself
>
>
> On Mon, May 27, 2013 at 5:33 PM, Forrest Xia  wrote:
>
>> Hi Devs,
>>
>> Please vote Geronimo eclipse plugin(GEP) 3.0.1 release. This is a release
>> along with Geronimo server runtime release 3.0.1.
>>
>> For details, see
>> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.1.txt
>>
>> The GEP code up for vote is:
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.tar.gz
>>
>> https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.zip
>>
>>
>> The GEP staging update site is:
>> http://people.apache.org/builds/geronimo/eclipse/updates/
>>
>> The release staging site is:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-003
>>
>> The tag has created at:
>>
>> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.1/
>>
>> Vote will be at least open for 72 hours.
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>
>
>
> --
> Thanks!
>
> Regards, Forrest
>



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

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Forrest Xia

Thank you Rex for this vote.

Any more votes??


On Tue, May 28, 2013 at 5:08 PM, Rex Wang  wrote:

> thanks and +1
>
>
> 2013/5/27 Forrest Xia 
>
>> +1 myself
>>
>>
>> On Mon, May 27, 2013 at 5:33 PM, Forrest Xia  wrote:
>>
>>> Hi Devs,
>>>
>>> Please vote Geronimo eclipse plugin(GEP) 3.0.1 release. This is a
>>> release along with Geronimo server runtime release 3.0.1.
>>>
>>> For details, see
>>> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.1.txt
>>>
>>> The GEP code up for vote is:
>>>
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.tar.gz
>>>
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.zip
>>>
>>>
>>> The GEP staging update site is:
>>> http://people.apache.org/builds/geronimo/eclipse/updates/
>>>
>>> The release staging site is:
>>> https://repository.apache.org/content/repositories/orgapachegeronimo-003
>>>
>>> The tag has created at:
>>>
>>> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.1/
>>>
>>> Vote will be at least open for 72 hours.
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> --
>>> Thanks!
>>>
>>> Regards, Forrest
>>>
>>
>>
>>
>> --
>> Thanks!
>>
>> Regards, Forrest
>>
>
>
>
> --
> Lei Wang (Rex)
> rwonly AT apache.org
>



-- 
Thanks!

Regards, Forrest

[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0

2013-05-28 Thread Nayela Manzoor (JIRA)


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

Nayela Manzoor commented on GERONIMO-6469:
--

Hi Ivan,

Thanks for your response. I am going to mention two examples:
 
1. There is a simple ejb with descriptors and without ejb-jar.xml:
 
@Stateless
@TransactionAttribute(TransactionAttributeType.REQUIRED)
@TransactionManagement(TransactionManagementType.CONTAINER)
public class CRAEETimerBMO implements CRAEETimerBMOLocal,CRAEETimerBMORemote {
This ejb is working in Geronimo 2.0.1 but  was not loaded in geronimo 3.0.1, I 
created the following ejb-jar.xml and the ejb was loaded:
?xml version="1.0" encoding="UTF-8"?>
http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
  http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd";
version="3.0">


CRA EE Timer for BMO
CRAEETimerBMO
CRAEETimerBMO

com.symcor.pcbi.cra.timer.ee.CRAEETimerBMOLocal

com.symcor.pcbi.cra.timer.ee.CRAEETimerBMORemote

com.symcor.pcbi.cra.timer.ee.CRAEETimerBMO
Stateless
Container





2.  There is an ejb class which has following method

@AroundInvoke
public Object setEnv(InvocationContext ctx) throws Exception{
There is no interceptor. This code is working in Geronimo 2.0.1. However, this 
is not being triggered by Geronimo 3.0.

Thanks,
Nayela

> EJB annotations are not working in Geronimo 3.0
> ---
>
> Key: GERONIMO-6469
> URL: https://issues.apache.org/jira/browse/GERONIMO-6469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Nayela Manzoor
>
> EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in 
> Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I 
> deployed it on Geronimo 3.0 and got many issues due to EJB annotation 
> failures. I had to replace EJB annotations with descriptors in ejb-jar file.

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

[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0

2013-05-28 Thread Nayela Manzoor (JIRA)


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

Nayela Manzoor commented on GERONIMO-6469:
--

Hi Ivan,
 
Thanks for your response. I am going to mention two examples:
 
1. There is a simple ejb with descriptors and without ejb-jar.xml:
 
@Stateless
@TransactionAttribute(TransactionAttributeType.REQUIRED)
@TransactionManagement(TransactionManagementType.CONTAINER)
public class CRAEETimerBMO implements CRAEETimerBMOLocal,CRAEETimerBMORemote {
This ejb is working in Geronimo 2.0.1 but  was not loaded in geronimo 3.0.1, I 
created the following ejb-jar.xml and the ejb was loaded:
?xml version="1.0" encoding="UTF-8"?>
http://java.sun.com/xml/ns/javaee";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
  http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd";
  version="3.0">
  
    
  CRA EE Timer for BMO
  CRAEETimerBMO
  CRAEETimerBMO
  
com.symcor.pcbi.cra.timer.ee.CRAEETimerBMOLocal
  
com.symcor.pcbi.cra.timer.ee.CRAEETimerBMORemote
      
com.symcor.pcbi.cra.timer.ee.CRAEETimerBMO
  Stateless
  Container
    
    
  

 
2.  There is an ejb class which has following method
 
@AroundInvoke
public Object setEnv(InvocationContext ctx) throws Exception{
There is no interceptor. This code is working in Geronimo 2.0.1. However, this 
is not being triggered by Geronimo 3.0.
 Thanks,
Nayela

--- On Mon, 5/27/13, Ivan (JIRA)  wrote:


From: Ivan (JIRA) 
Subject: [jira] [Commented] (GERONIMO-6469) EJB annotations are not working in 
Geronimo 3.0
To: manzo...@rocketmail.com
Date: Monday, May 27, 2013, 8:38 PM



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

Ivan commented on GERONIMO-6469:


You may want to provide the sample for reproducing this issue, or is there any 
output in the log ? With the current description, it is hard to know what 
happened.
                

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


> EJB annotations are not working in Geronimo 3.0
> ---
>
> Key: GERONIMO-6469
> URL: https://issues.apache.org/jira/browse/GERONIMO-6469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Nayela Manzoor
>
> EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in 
> Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I 
> deployed it on Geronimo 3.0 and got many issues due to EJB annotation 
> failures. I had to replace EJB annotations with descriptors in ejb-jar file.

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

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Johannes Weberhofer


Dear Forrest,

it's compiling on my test system and I can build and deploy a large application 
to my Geronimo 2.2 server.

+1

A comment: GEP is still building with maven 2 only, builds with maven 3 fails;

Best regards and thank you!

Johannes



At 28.05.2013 13:51, Forrest Xia wrote:

Thank you Rex for this vote.

Any more votes??


On Tue, May 28, 2013 at 5:08 PM, Rex Wang mailto:rwo...@gmail.com>> wrote:

thanks and +1


2013/5/27 Forrest Xia mailto:forres...@gmail.com>>

+1 myself


On Mon, May 27, 2013 at 5:33 PM, Forrest Xia mailto:forres...@gmail.com>> wrote:

Hi Devs,

Please vote Geronimo eclipse plugin(GEP) 3.0.1 release. This is a 
release along with Geronimo server runtime release 3.0.1.

For details, see 
http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.1.txt

The GEP code up for vote is:

https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.tar.gz

https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.zip


The GEP staging update site is:
http://people.apache.org/builds/geronimo/eclipse/updates/

The release staging site is:

https://repository.apache.org/content/repositories/orgapachegeronimo-003

The tag has created at:

http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.1/

Vote will be at least open for 72 hours.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

--
Thanks!

Regards, Forrest




--
Thanks!

Regards, Forrest




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




--
Thanks!

Regards, Forrest


--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Kevan Miller

How are you building? I'm getting the following errors. Maybe a Mac OS issue?

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.681s
[INFO] Finished at: Tue May 28 09:26:29 EDT 2013
[INFO] Final Memory: 20M/83M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) 
on project org.apache.geronimo.runtime.common: Compilation failure: Compilation 
failure:
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[21,31]
 package org.eclipse.core.runtime does not exist
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[22,31]
 package org.eclipse.core.runtime does not exist
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[23,31]
 package org.eclipse.core.runtime does not exist
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[24,25]
 package org.osgi.framework does not exist
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[26,28]
 cannot find symbol
[ERROR] symbol: class Plugin
[ERROR] public class Logger extends Plugin{
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[27,16]
 cannot find symbol
[ERROR] symbol  : class ILog
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[44,19]
 cannot find symbol
[ERROR] symbol  : class BundleContext
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[52,18]
 cannot find symbol
[ERROR] symbol  : class BundleContext
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[33,9]
 cannot find symbol
[ERROR] symbol  : variable super
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[30,1]
 method does not override or implement a method from a supertype
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[39,2]
 cannot find symbol
[ERROR] symbol  : variable super
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[36,1]
 method does not override or implement a method from a supertype
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[46,2]
 cannot find symbol
[ERROR] symbol  : variable super
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[47,28]
 cannot find symbol
[ERROR] symbol  : method getLog()
[ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[43,1]
 method does not override or implement a method from a supertype
[ERROR] 
[ERROR] 
/Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[54,2

[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0

2013-05-28 Thread Ivan (JIRA)


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

Ivan commented on GERONIMO-6469:


The code fragment looks fine to me, where did you place the class CRAEETimerBMO 
? In a jar file or in the war ? Is there any output in the log file ?

> EJB annotations are not working in Geronimo 3.0
> ---
>
> Key: GERONIMO-6469
> URL: https://issues.apache.org/jira/browse/GERONIMO-6469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Nayela Manzoor
>
> EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in 
> Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I 
> deployed it on Geronimo 3.0 and got many issues due to EJB annotation 
> failures. I had to replace EJB annotations with descriptors in ejb-jar file.

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

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Forrest Xia

GEP only build with maven 2.2.1


On Tue, May 28, 2013 at 9:44 PM, Kevan Miller wrote:

> How are you building? I'm getting the following errors. Maybe a Mac OS
> issue?
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 14.681s
> [INFO] Finished at: Tue May 28 09:26:29 EDT 2013
> [INFO] Final Memory: 20M/83M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> (default-compile) on project org.apache.geronimo.runtime.common:
> Compilation failure: Compilation failure:
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[21,31]
> package org.eclipse.core.runtime does not exist
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[22,31]
> package org.eclipse.core.runtime does not exist
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[23,31]
> package org.eclipse.core.runtime does not exist
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[24,25]
> package org.osgi.framework does not exist
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[26,28]
> cannot find symbol
> [ERROR] symbol: class Plugin
> [ERROR] public class Logger extends Plugin{
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[27,16]
> cannot find symbol
> [ERROR] symbol  : class ILog
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[44,19]
> cannot find symbol
> [ERROR] symbol  : class BundleContext
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[52,18]
> cannot find symbol
> [ERROR] symbol  : class BundleContext
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[33,9]
> cannot find symbol
> [ERROR] symbol  : variable super
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[30,1]
> method does not override or implement a method from a supertype
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[39,2]
> cannot find symbol
> [ERROR] symbol  : variable super
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[36,1]
> method does not override or implement a method from a supertype
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[46,2]
> cannot find symbol
> [ERROR] symbol  : variable super
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[47,28]
> cannot find symbol
> [ERROR] symbol  : method getLog()
> [ERROR] location: class org.apache.geronimo.runtime.common.log.Logger
> [ERROR]
> [ERROR]
> /Users/kevan/tmp/release/geronimo-eclipse-plugin-3.0.1/plugins/org.apache.geronimo.runtime.common/src/main/java/org/apache/geronimo/runtime/common/log/Logger.java:[43,1]
> method does not override o

[jira] [Updated] (GERONIMO-6470) Enable the tomcat feature to Modify Apache-Coyote/1.1 Banner

2013-05-28 Thread xiezhi (JIRA)


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

xiezhi updated GERONIMO-6470:
-

Attachment: ModifyBanner.patch

Got a patch, Please check it. Thanks.

> Enable the tomcat feature to Modify Apache-Coyote/1.1 Banner
> 
>
> Key: GERONIMO-6470
> URL: https://issues.apache.org/jira/browse/GERONIMO-6470
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 1.x
>Reporter: xiezhi
>Priority: Minor
> Attachments: ModifyBanner.patch
>
>
> In Response Headers, it exposure the version number of the Apache Tomcat Web 
> Server which runs on port 8080 by default.
> We hope to modify the TomcatWebConnector'attribute server to protect this 
> information.
> I think the good pratice is below.
> In \var\config\config.xml
>   
> 
>   name=Geronimo
>   
> 
> 
> 
> 
> 
>   0.0.0.0
>   8080
>   8443
>   2048
>   150
>   100
>   -1
>   true
>   25
>   75
>   8192
>   false
>   2
>   false
>   2097152
>   4096
>   false
>   TestResponseHead
> 

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

[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0

2013-05-28 Thread Nayela Manzoor (JIRA)


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

Nayela Manzoor commented on GERONIMO-6469:
--

The CRAEETimerBMO is in a separate jar inside an EAR. There was no message in 
the log file regarding deployment or no deployment of the ejb. What do you 
think about the aroundInvoke annotation?

Thanks,
Nayela

> EJB annotations are not working in Geronimo 3.0
> ---
>
> Key: GERONIMO-6469
> URL: https://issues.apache.org/jira/browse/GERONIMO-6469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Nayela Manzoor
>
> EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in 
> Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I 
> deployed it on Geronimo 3.0 and got many issues due to EJB annotation 
> failures. I had to replace EJB annotations with descriptors in ejb-jar file.

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

EXTRA! EXTRA! Apache Geronimo v3.0.1 Released!

2013-05-28 Thread Forrest Xia

I'm pleased to announce that Apache Geronimo v3.0.1 is released today! This
is a bug fixing release of version 3.0. Besides the support of full profile
of Java EE 6 and enablement of running with Java 7 , a couple highlights
are:

   - Tomcat upgraded to 7.0.39
   - Tranql upgraded to 1.8 to support JDBC 4
   - MyFaces upgraded to 2.1.10 to support JSF 2.1
   - OpenJPA upgraded to 2.2.2
   - Yoko upgraded to 1.4
   - ActiveMQ upgraded to 5.4.3

The Geronimo home page shall be refreshed some time later to display the
release news. For those unpatient, please visit this confluence
URLto
try Geronimo v3.0.1 now!

-- 
Thanks!

Regards, Forrest

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Kevan Miller


On May 28, 2013, at 10:10 AM, Forrest Xia  wrote:

> GEP only build with maven 2.2.1

If so, can we put a BUILDING or README with build instructions? Won't require 
it for this release, but would be good to have clear instructions. 

I'm still having a build error:

[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

o GroupID: org.eclipse.plugins
o ArtifactID:  org.eclipse.swt.cocoa.macosx
o Version: <<< MISSING >>>
o Type:jar

[INFO] 
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact 
{org.eclipse.plugins:org.eclipse.swt.cocoa.macosx:null:jar}: The version cannot 
be empty.
at 
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
at 
org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
at 
org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
at 
org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:70)
at 
org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:439)
at 
org.apache.maven.project.MavenProject.createArtifacts(MavenProject.java:1651)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1489)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
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)


--kevan

[DISCUSSION] How to compile GEP

2013-05-28 Thread Forrest Xia

What's your configuration on Mac OS?

Java version? In what module does the problem happen?

-- Forwarded message --
From: Kevan Miller 
Date: Tue, May 28, 2013 at 10:52 PM
Subject: Re: [VOTE] Release Geronimo eclipse plugin 3.0.1
To: dev@geronimo.apache.org

On May 28, 2013, at 10:10 AM, Forrest Xia  wrote:

> GEP only build with maven 2.2.1

If so, can we put a BUILDING or README with build instructions? Won't
require it for this release, but would be good to have clear instructions.

I'm still having a build error:

[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been
included transitively during the resolution process. Here is the
information we do have for this artifact:

o GroupID: org.eclipse.plugins
o ArtifactID:  org.eclipse.swt.cocoa.macosx
o Version: <<< MISSING >>>
o Type:jar

[INFO]

[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.eclipse.plugins:org.eclipse.swt.cocoa.macosx:null:jar}: The version
cannot be empty.
at
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
at
org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
at
org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
at
org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:70)
at
org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:439)
at
org.apache.maven.project.MavenProject.createArtifacts(MavenProject.java:1651)
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1489)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
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)

--kevan

-- 
Thanks!

Regards, Forrest

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Kevan Miller

On May 28, 2013, at 11:05 AM, Forrest Xia  wrote:

> What's your configuration on Mac OS?
> 
> Java version? In what module does the problem happen?

I've tried both Java 6 and Java 7. 

Java 6 fails with:

[INFO] 
[INFO] Building org.apache.geronimo.st.ui
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean {execution: default-clean}]
[INFO] [eclipsepde:manifestbundles {execution: initialize}]
[INFO] [eclipsepde:install {execution: initialize}]
[INFO] org.eclipse.jface.text : 3.7.1-r371_v20110825-0800 already exists in 
local repository.
[INFO] org.eclipse.core.runtime : 3.7.0-v20110110 already exists in local 
repository.
[INFO] org.eclipse.jdt.debug.ui : 3.6.1-v20110803_r371 already exists in local 
repository.
[INFO] org.eclipse.ui.views : 3.6.0-I20110412-0800 already exists in local 
repository.
[INFO] org.eclipse.core.filebuffers : 3.5.200-v20110505-0800 already exists in 
local repository.
[INFO] org.eclipse.equinox.common : 3.6.0-v20110523 already exists in local 
repository.
[INFO] org.eclipse.wst.common.core : 1.2.0-v200908252030 already exists in 
local repository.
[INFO] org.eclipse.core.commands : 3.6.0-I20110111-0800 already exists in local 
repository.
[INFO] org.eclipse.wst.sse.ui : 1.3.1-v201108191312 already exists in local 
repository.
[INFO] org.eclipse.ui.forms : 3.5.100-v20110425 already exists in local 
repository.
[INFO] org.eclipse.ui.ide : 3.7.0-v20110809-1737 already exists in local 
repository.
[INFO] org.eclipse.ui.workbench.texteditor : 3.7.0-v20110505-0800 already 
exists in local repository.
[INFO] org.eclipse.core.contenttype : 3.4.100-v20110423-0524 already exists in 
local repository.
[INFO] org.eclipse.jface : 3.7.0-I20110522-1430 already exists in local 
repository.
[INFO] org.eclipse.wst.xml.ui : 1.1.201-v201108151912 already exists in local 
repository.
[INFO] org.eclipse.wst.common.project.facet.core : 1.4.200-v201103170332 
already exists in local repository.
[INFO] org.eclipse.core.resources : 3.7.100-v20110510-0712 already exists in 
local repository.
[INFO] org.eclipse.equinox.preferences : 3.4.1-R37x_v20110725 already exists in 
local repository.
[INFO] org.eclipse.ltk.core.refactoring : 3.5.201-r371_v20110824-0800 already 
exists in local repository.
[INFO] org.eclipse.jst.j2ee.web : 1.1.501-v201108231500 already exists in local 
repository.
[INFO] org.eclipse.jst.server.core : 1.2.202-v20110419 already exists in local 
repository.
[INFO] org.eclipse.debug.core : 3.7.0-v20110518 already exists in local 
repository.
[INFO] org.eclipse.jst.j2ee : 1.1.501-v201108231845 already exists in local 
repository.
[INFO] org.eclipse.debug.ui : 3.7.101-v20110817_r371 already exists in local 
repository.
[INFO] org.eclipse.wst.common.frameworks : 1.2.101-v201107192200 already exists 
in local repository.
[INFO] org.eclipse.equinox.registry : 3.5.101-R37x_v20110810-1611 already 
exists in local repository.
[INFO] org.eclipse.wst.server.ui : 1.1.306-v20110823_1704 already exists in 
local repository.
[INFO] SWTFragment:  Dependency {groupId=org.eclipse.plugins, 
artifactId=org.eclipse.swt.cocoa.macosx, version=null, type=jar}
[ERROR] Bundle for dependency not found: org.eclipse.swt.cocoa.macosx
[INFO] org.eclipse.swt : 3.7.1-v3738a already exists in local repository.
[INFO] org.eclipse.osgi : 3.7.1-R37x_v20110808-1106 already exists in local 
repository.
[INFO] org.eclipse.ui.editors : 3.7.0-v20110517-0800 already exists in local 
repository.
[INFO] org.eclipse.ui : 3.7.0-I20110602-0100 already exists in local repository.
[INFO] org.eclipse.wst.common.modulecore : 1.2.101-v201108231700 already exists 
in local repository.
[INFO] org.eclipse.ui.workbench : 3.7.0-I20110519-0100 already exists in local 
repository.
[INFO] org.eclipse.core.jobs : 3.5.100-v20110404 already exists in local 
repository.
[INFO] org.eclipse.jdt.launching : 3.6.1-v20110803_r371 already exists in local 
repository.
[INFO] org.eclipse.jdt.core : 3.7.1-v_B76_R37x already exists in local 
repository.
[INFO] org.eclipse.text : 3.5.101-r371_v20110810-0800 already exists in local 
repository.
[INFO] org.eclipse.equinox.app : 1.3.100-v20110321 already exists in local 
repository.
[INFO] org.eclipse.wst.server.core : 1.1.303-v20110816_1717 already exists in 
local repository.
[INFO] org.eclipse.wst.common.project.facet.ui : 1.4.200-v201103311536 already 
exists in local repository.
[INFO] org.eclipse.jem.util : 2.1.100-v201103021400 already exists in local 
repository.
[INFO] [build-helper:parse-version {execution: parse-version}]
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resol

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

2013-05-28 Thread Shawn Jiang

Kevan,

Are you using Mac 64bit ?

-- Forwarded message --
From: Yi Xiao 
Date: Tue, Jul 17, 2012 at 2:29 PM
Subject: Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC1
To: dev@geronimo.apache.org


Hi Kevan,

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

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


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

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


-- 
Best regards!


 John Xiao




-- 
Shawn

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Kevan Miller


On May 28, 2013, at 11:21 AM, Shawn Jiang  wrote:

> Kevan,
> 
> Are you using Mac 64bit ?

Yes.

--kevan

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

2013-05-28 Thread Kevan Miller

On Jul 17, 2012, at 2:25 AM, Yi Xiao  wrote:

> Hi Jarek,
> 
> You are right.
>  I use mvn release:prepare -Pallsubproject and mvn release:perform 
> -Pallsubproject but there is no allsubproject profile...
> 
> Thank you for pointing it out.
> I will re-release it.

If we cannot build GEP on Mac OS and we must build using Mavan 2.2.1, can we 
please add a BUILDING or README that documents these requirements/restrictions? 

I have not built (or tested GEP), but license/notice, source, rat, etc all look 
good to me. I should be able to vote for the release once the SNAPSHOT issues 
are resolved.

--kevan

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

2013-05-28 Thread Forrest Xia

what you mean "I should be able to vote for the release once the SNAPSHOT
issues are resolved."??


On Tue, May 28, 2013 at 11:26 PM, Kevan Miller wrote:

>
> On Jul 17, 2012, at 2:25 AM, Yi Xiao  wrote:
>
> > Hi Jarek,
> >
> > You are right.
> >  I use mvn release:prepare -Pallsubproject and mvn release:perform
> -Pallsubproject but there is no allsubproject profile...
> >
> > Thank you for pointing it out.
> > I will re-release it.
>
> If we cannot build GEP on Mac OS and we must build using Mavan 2.2.1, can
> we please add a BUILDING or README that documents these
> requirements/restrictions?
>
> I have not built (or tested GEP), but license/notice, source, rat, etc all
> look good to me. I should be able to vote for the release once the SNAPSHOT
> issues are resolved.
>
> --kevan




-- 
Thanks!

Regards, Forrest

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Alan Cabrera

On May 28, 2013, at 7:10 AM, Forrest Xia  wrote:

> GEP only build with maven 2.2.1
> 

On Mac OS X 10.8.3:

[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

o GroupID: org.eclipse.plugins
o ArtifactID:  org.eclipse.swt.cocoa.macosx
o Version: <<< MISSING >>>
o Type:jar

[INFO] 
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact 
{org.eclipse.plugins:org.eclipse.swt.cocoa.macosx:null:jar}: The version cannot 
be empty.
at 
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
at 
org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
at 
org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
at 
org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:70)
at 
org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:439)
at 
org.apache.maven.project.MavenProject.createArtifacts(MavenProject.java:1651)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1489)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
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)
[INFO]

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Alan Cabrera


On May 28, 2013, at 8:14 AM, Kevan Miller  wrote:

> 
> On May 28, 2013, at 11:05 AM, Forrest Xia  wrote:
> 
>> What's your configuration on Mac OS?
>> 
>> Java version? In what module does the problem happen?
> 
> I've tried both Java 6 and Java 7. 
> 
> Java 6 fails with:
> 
> 
> [INFO] 
> 
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] An invalid artifact was detected.
> 
> This artifact might be in your project's POM, or it might have been included 
> transitively during the resolution process. Here is the information we do 
> have for this artifact:
> 
>o GroupID: org.eclipse.plugins
>o ArtifactID:  org.eclipse.swt.cocoa.macosx
>o Version: <<< MISSING >>>
>o Type:jar
> 

I get the same error, Java 6.


Regards,
Alan

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Forrest Xia

Some known issues there fyi.
> [Known issue]
> 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be
built successfully on 64bit win7 and 64bit macos. See following JIRAs for
details.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
build GEP3.0 under win7-64bit
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
build GEP3.0 under macos-64bit
> 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is
still open.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
build GEP with maven 3.0


On Tue, May 28, 2013 at 11:31 PM, Alan Cabrera  wrote:

>
> On May 28, 2013, at 7:10 AM, Forrest Xia  wrote:
>
> GEP only build with maven 2.2.1
>
>
> On Mac OS X 10.8.3:
>
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] An invalid artifact was detected.
>
> This artifact might be in your project's POM, or it might have been
> included transitively during the resolution process. Here is the
> information we do have for this artifact:
>
> o GroupID: org.eclipse.plugins
> o ArtifactID:  org.eclipse.swt.cocoa.macosx
> o Version: <<< MISSING >>>
> o Type:jar
>
> [INFO]
> 
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {org.eclipse.plugins:org.eclipse.swt.cocoa.macosx:null:jar}: The version
> cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
> at
> org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:70)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:439)
> at
> org.apache.maven.project.MavenProject.createArtifacts(MavenProject.java:1651)
> at
> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1489)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> 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)
> [INFO]
> 
>
>


-- 
Thanks!

Regards, Forrest

Re: [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Alan Cabrera

Known issues of the tool we use to build should percolate up to the known 
issues in our release notes, imo.


Regards,
Alan

On May 28, 2013, at 8:38 AM, Forrest Xia  wrote:

> Some known issues there fyi.
> > [Known issue]
> > 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be 
> > built successfully on 64bit win7 and 64bit macos. See following JIRAs for 
> > details.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not 
> > build GEP3.0 under win7-64bit
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not 
> > build GEP3.0 under macos-64bit
> > 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is 
> > still open.
> > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build 
> > GEP with maven 3.0
> 
> 
> On Tue, May 28, 2013 at 11:31 PM, Alan Cabrera  wrote:
> 
> On May 28, 2013, at 7:10 AM, Forrest Xia  wrote:
> 
>> GEP only build with maven 2.2.1
>> 
> 
> On Mac OS X 10.8.3:
> 
> [INFO] 
> 
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] An invalid artifact was detected.
> 
> This artifact might be in your project's POM, or it might have been included 
> transitively during the resolution process. Here is the information we do 
> have for this artifact:
> 
> o GroupID: org.eclipse.plugins
> o ArtifactID:  org.eclipse.swt.cocoa.macosx
> o Version: <<< MISSING >>>
> o Type:jar
> 
> [INFO] 
> 
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact 
> {org.eclipse.plugins:org.eclipse.swt.cocoa.macosx:null:jar}: The version 
> cannot be empty.
>   at 
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
>   at 
> org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
>   at 
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
>   at 
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:70)
>   at 
> org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:439)
>   at 
> org.apache.maven.project.MavenProject.createArtifacts(MavenProject.java:1651)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1489)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>   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)
> [INFO] 
> 
> 
> 
> 
> 
> -- 
> Thanks!
> 
> Regards, Forrest

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Jarek Gawor

Alan, Kevan, can you try changing the maven-eclipsepde-plugin version
dependency to 1.2-SNAPSHOT and see if the code at least compiles now?

If that works, then I think we should release the 1.2 version of
maven-eclipsepde-plugin and update GEP to use it.

Jarek


On Tue, May 28, 2013 at 11:32 AM, Alan Cabrera  wrote:
>
> On May 28, 2013, at 8:14 AM, Kevan Miller  wrote:
>
>>
>> On May 28, 2013, at 11:05 AM, Forrest Xia  wrote:
>>
>>> What's your configuration on Mac OS?
>>>
>>> Java version? In what module does the problem happen?
>>
>> I've tried both Java 6 and Java 7.
>>
>> Java 6 fails with:
>>
>> 
>> [INFO] 
>> 
>> [ERROR] FATAL ERROR
>> [INFO] 
>> 
>> [INFO] An invalid artifact was detected.
>>
>> This artifact might be in your project's POM, or it might have been included 
>> transitively during the resolution process. Here is the information we do 
>> have for this artifact:
>>
>>o GroupID: org.eclipse.plugins
>>o ArtifactID:  org.eclipse.swt.cocoa.macosx
>>o Version: <<< MISSING >>>
>>o Type:jar
>>
>
> I get the same error, Java 6.
>
>
> Regards,
> Alan
>
>

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Shawn Jiang

this is what we have in GEP 3.0 beta and 3.0 release.

[Known issue]
1. GEP 3.0-beta-1 uses maven-eclipsepde-plugin v1.1, which means it can not
be built successfully on 64bit win7 and 64bit macos. See following JIRAs
for details.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
build GEP3.0 under win7-64bit
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
build GEP3.0 under macos-64bit
2. Also, please use maven v2.2.1 to build GEP 3.0-beta-1 as following JIRA
is still open.
- https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build
GEP with maven 3.0


On Tue, May 28, 2013 at 11:23 PM, Kevan Miller wrote:

>
> On May 28, 2013, at 11:21 AM, Shawn Jiang  wrote:
>
> > Kevan,
> >
> > Are you using Mac 64bit ?
>
> Yes.
>
> --kevan
>



-- 
Shawn

Cancelled [VOTE] Release Geronimo eclipse plugin 3.0.1

2013-05-28 Thread Forrest Xia

need to release maven eclipsepde plugin 1.2 first, so that GEP 3.x can
build on Mac.


On Mon, May 27, 2013 at 5:33 PM, Forrest Xia  wrote:

> Hi Devs,
>
> Please vote Geronimo eclipse plugin(GEP) 3.0.1 release. This is a release
> along with Geronimo server runtime release 3.0.1.
>
> For details, see
> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.1.txt
>
> The GEP code up for vote is:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.tar.gz
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.zip
>
>
> The GEP staging update site is:
> http://people.apache.org/builds/geronimo/eclipse/updates/
>
> The release staging site is:
> https://repository.apache.org/content/repositories/orgapachegeronimo-003
>
> The tag has created at:
>
> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.1/
>
> Vote will be at least open for 72 hours.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> --
> Thanks!
>
> Regards, Forrest
>



-- 
Thanks!

Regards, Forrest

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Forrest Xia

will do pde plugin 1.2 release first.


On Tue, May 28, 2013 at 11:50 PM, Shawn Jiang  wrote:

> this is what we have in GEP 3.0 beta and 3.0 release.
>
> [Known issue]
> 1. GEP 3.0-beta-1 uses maven-eclipsepde-plugin v1.1, which means it can
> not be built successfully on 64bit win7 and 64bit macos. See following
> JIRAs for details.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not
> build GEP3.0 under win7-64bit
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not
> build GEP3.0 under macos-64bit
> 2. Also, please use maven v2.2.1 to build GEP 3.0-beta-1 as following
> JIRA is still open.
> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not
> build GEP with maven 3.0
>
>
> On Tue, May 28, 2013 at 11:23 PM, Kevan Miller wrote:
>
>>
>> On May 28, 2013, at 11:21 AM, Shawn Jiang  wrote:
>>
>> > Kevan,
>> >
>> > Are you using Mac 64bit ?
>>
>> Yes.
>>
>> --kevan
>>
>
>
>
> --
> Shawn
>



-- 
Thanks!

Regards, Forrest

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

2013-05-28 Thread Kevan Miller


On May 28, 2013, at 11:31 AM, Forrest Xia  wrote:

> what you mean "I should be able to vote for the release once the SNAPSHOT 
> issues are resolved."??


On Jul 17, 2012, at 2:25 AM, Yi Xiao  wrote:

> Hi Jarek,
> 
> You are right.
>  I use mvn release:prepare -Pallsubproject and mvn release:perform 
> -Pallsubproject but there is no allsubproject profile...
> 
> Thank you for pointing it out.
> I will re-release it.
> 
> On Mon, Jul 16, 2012 at 11:23 PM, Jarek Gawor  wrote:
> John,
> 
> Looks like the testsuite pom files still use SNAPSHOT versions.

--kevan

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

2013-05-28 Thread Kevan Miller

On May 28, 2013, at 11:31 AM, Forrest Xia  wrote:

> what you mean "I should be able to vote for the release once the SNAPSHOT 
> issues are resolved."??

Oops. Sorry for all the noise I generated. You can ignore… I was searching mail 
history and accidentally thought this was the current vote thread…

--kevan

Re: [DISCUSSION] How to compile GEP

2013-05-28 Thread Kevan Miller

On May 28, 2013, at 11:48 AM, Jarek Gawor  wrote:

> Alan, Kevan, can you try changing the maven-eclipsepde-plugin version
> dependency to 1.2-SNAPSHOT and see if the code at least compiles now?

Hi Jarek,
Using Java 6, Maven 2.2.1 and 1.2-SNAPSHOT of the maven-eclipsepde-plugin 
allows me to build on Mac OS.

--kevan

[VOTE] release xbean-3.14

2013-05-28 Thread Mark Struberg



Hi!

I'd like to call a VOTE for releasing xbean-3.14

The staging repo can be found here:
https://repository.apache.org/content/repositories/orgapachegeronimo-014/

The tag is https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.14/

And here comes the source.zip:

https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/xbean/xbean/3.14/xbean-3.14-source-release.zip

sha1: 

a3dffcaf6672db1543e46b0e7ffa0acf84cdf929

The VOTE is open for 72h

[+1] all fine, let's ship it
[+0] meh don't care
[-1] nope because it contains a ${blocker}


LieGrue,
strub

Re: [VOTE] release xbean-3.14

2013-05-28 Thread Kevan Miller

Hi Mark,
I'm seeing a few problems. Looks like I may have missed them in the last 
release. Anyway, I think they need to be fixed. My bad for not seeing sooner...

Missing an Apache source license header: 

xbean-finder/src/test/java/org/apache/xbean/finder/ClassAnnotationFinderTest.java
xbean-finder/src/test/java/org/acme/ClassAnnotatedClass.java
xbean-finder/src/test/java/org/acme/NotAnnotated.java (not absolutely 
necessary, but would be good to see the "Copyright (c) 2011 David Blevins" 
removed. will need his permission or for him to do that)

Everything else is looking pretty good. License/Notice, and build looks good. 
So, looks like I'd be +1, if the above were resolved.

--kevan

On May 28, 2013, at 1:33 PM, Mark Struberg  wrote:

> 
> 
> Hi!
> 
> I'd like to call a VOTE for releasing xbean-3.14
> 
> The staging repo can be found here:
> https://repository.apache.org/content/repositories/orgapachegeronimo-014/
> 
> The tag is https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.14/
> 
> And here comes the source.zip:
> 
> https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/xbean/xbean/3.14/xbean-3.14-source-release.zip
> 
> sha1: 
> 
> a3dffcaf6672db1543e46b0e7ffa0acf84cdf929
> 
> The VOTE is open for 72h
> 
> [+1] all fine, let's ship it
> [+0] meh don't care
> [-1] nope because it contains a ${blocker}
> 
> 
> LieGrue,
> strub

Re: [VOTE] [CANCELLED] release xbean-3.14

2013-05-28 Thread Mark Struberg

txs for the catch Kevan!

Is there no automatic RAT/creadur enabled in the build?

LieGrue,
strub



- Original Message -
> From: Kevan Miller 
> To: dev@geronimo.apache.org; Mark Struberg 
> Cc: 
> Sent: Tuesday, 28 May 2013, 20:58
> Subject: Re: [VOTE] release xbean-3.14
> 
> Hi Mark,
> I'm seeing a few problems. Looks like I may have missed them in the last 
> release. Anyway, I think they need to be fixed. My bad for not seeing 
> sooner...
> 
> Missing an Apache source license header: 
> 
> xbean-finder/src/test/java/org/apache/xbean/finder/ClassAnnotationFinderTest.java
> xbean-finder/src/test/java/org/acme/ClassAnnotatedClass.java
> xbean-finder/src/test/java/org/acme/NotAnnotated.java (not absolutely 
> necessary, 
> but would be good to see the "Copyright (c) 2011 David Blevins" 
> removed. will need his permission or for him to do that)
> 
> Everything else is looking pretty good. License/Notice, and build looks good. 
> So, looks like I'd be +1, if the above were resolved.
> 
> --kevan
> 
> On May 28, 2013, at 1:33 PM, Mark Struberg  wrote:
> 
>> 
>> 
>>  Hi!
>> 
>>  I'd like to call a VOTE for releasing xbean-3.14
>> 
>>  The staging repo can be found here:
>>  https://repository.apache.org/content/repositories/orgapachegeronimo-014/
>> 
>>  The tag is https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.14/
>> 
>>  And here comes the source.zip:
>> 
>> 
> https://repository.apache.org/content/repositories/orgapachegeronimo-014/org/apache/xbean/xbean/3.14/xbean-3.14-source-release.zip
>> 
>>  sha1: 
>> 
>>  a3dffcaf6672db1543e46b0e7ffa0acf84cdf929
>> 
>>  The VOTE is open for 72h
>> 
>>  [+1] all fine, let's ship it
>>  [+0] meh don't care
>>  [-1] nope because it contains a ${blocker}
>> 
>> 
>>  LieGrue,
>>  strub
>

[jira] [Commented] (GERONIMO-6469) EJB annotations are not working in Geronimo 3.0

2013-05-28 Thread Ivan (JIRA)


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

Ivan commented on GERONIMO-6469:


Hmm, is that seprate jar file kind of library (e.g. in the lib directory)? If 
not, did you configure it as an ejb in the application.xml file ?
As for annotation scanning, the library files will not be considered.

> EJB annotations are not working in Geronimo 3.0
> ---
>
> Key: GERONIMO-6469
> URL: https://issues.apache.org/jira/browse/GERONIMO-6469
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Nayela Manzoor
>
> EJB annotations, for exampe, EJB, Stateless, aroundinvoke are not working in 
> Geronimo 3.0. I have current application running well in Geronimo 2.0.1. I 
> deployed it on Geronimo 3.0 and got many issues due to EJB annotation 
> failures. I had to replace EJB annotations with descriptors in ejb-jar file.

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

[jira] [Updated] (GERONIMODEVTOOLS-737) Could not build GEP3.0 under win7-64bit

2013-05-28 Thread Forrest Xia (JIRA)


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

Forrest Xia updated GERONIMODEVTOOLS-737:
-

Fix Version/s: (was: 3.0)
   3.0.1

GEP 3.0.1 use maven-eclipsepde-plugin 1.2 release which fixed the compilation 
problem finally.

> Could not build GEP3.0 under win7-64bit
> ---
>
> Key: GERONIMODEVTOOLS-737
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: maven-eclipsepde-plugin
>Affects Versions: 3.0
> Environment: Windows7-64bit
>Reporter: Yi Xiao
>Assignee: Yi Xiao
> Fix For: 3.0.1
>
> Attachments: patch.patch
>
>
> The eclipse pde plugin could not handle the 64-bit correctly

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

[jira] [Updated] (GERONIMODEVTOOLS-649) Can't build GEP trunk on 32-bit Mac

2013-05-28 Thread Forrest Xia (JIRA)


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

Forrest Xia updated GERONIMODEVTOOLS-649:
-

Affects Version/s: 3.0_M1
   3.0
   3.0-beta-1
Fix Version/s: (was: 3.0_M1)
   (was: 3.0)
   3.0.1

GEP 3.0.1 build finally fixed this problem via upgrading 
maven-eclipsepde-plugin to 1.2 release.

> Can't build GEP trunk  on 32-bit Mac
> 
>
> Key: GERONIMODEVTOOLS-649
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 3.0_M1, 3.0, 3.0-beta-1
>Reporter: Delos Dai
>Assignee: Delos Dai
> Fix For: 3.0.1
>
> Attachments: maven-eclipsepde-plugin-2.0.jar
>
>
> Need to update  eclipse/build.xml to make GEP build successfully on 32-bit 
> Mac. Eclipse 3.6 has dropped support for Mac carbon. The script should change 
> to Mac cocoa.
> From Donald,
> Could not build on MacOSX, as the referenced file no longer exists -
> file=/technology/epp/downloads/release/helios/R/eclipse-jee-helios-macosx-carbon.tar.gz
> Looks like we need to use the following 32bit Mac download instead in
> eclipse/build.xml -
>value="eclipse-jee-helios-macosx-cocoa.tar"/>
>value="eclipse-jee-helios-macosx-cocoa-x86_64.tar"/>
> Also, I had to specify specific mirrors to use (like AWS) as the local
> mirror didn't have the Helios files on it yet

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

[VOTE] Geronimo devtools maven-eclipsepde-plugin 1.2 release

2013-05-28 Thread Forrest Xia

Hi all,

To make Geronimo eclipse plugin compiled on Mac OS, we need to release a
new maven-eclipsepde-plugin 1.2.

Here are artifacts for vote:
Source code:
https://repository.apache.org/content/repositories/orgapachegeronimo-030/org/apache/geronimo/devtools/maven-eclipsepde-plugin/1.2/maven-eclipsepde-plugin-1.2-sources.jar

svn tag:
http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/maven-plugins-1.2/

NOTE: please build it with maven 2.2.1 and Java 6.

Vote will be at most open for 72 hours.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


-- 
Thanks!

Regards, Forrest

37 matches

Mail list logo