Hi,
in need to revert my vote to -1 !
We should not use the version to distinguish the jsf-spec
compatiblity, but the artifactId!
The artifactId should something like myfaces-commons12 at the version
should be 1.0(.0 maybe).
see:
Hi,
+0
Regards,
Volker
2008/9/3 Leonardo Uribe [EMAIL PROTECTED]:
Hi,
I was running the needed tasks to get the 1.2.0 release of Apache
MyFaces Commons out.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.commons v1.2.0
+1
On Wed, Sep 3, 2008 at 1:02 AM, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
+0
Regards,
Volker
2008/9/3 Leonardo Uribe [EMAIL PROTECTED]:
Hi,
I was running the needed tasks to get the 1.2.0 release of Apache
MyFaces Commons out.
Please note that this vote concerns all of
If commons can be released without including the exporterActionListener then
+1
else -1 till I completed this task.
On Wed, Sep 3, 2008 at 5:24 AM, Leonardo Uribe [EMAIL PROTECTED] wrote:
On Tue, Sep 2, 2008 at 9:23 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the needed
On Wed, Sep 3, 2008 at 12:20 PM, Hazem Saleh [EMAIL PROTECTED] wrote:
If commons can be released without including the exporterActionListener
then +1
else -1 till I completed this task.
Actually there is no component module in commons, so it is not necessary to
include exporterActionListener
Then +1 :).
On Wed, Sep 3, 2008 at 10:09 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
On Wed, Sep 3, 2008 at 12:20 PM, Hazem Saleh [EMAIL PROTECTED] wrote:
If commons can be released without including the exporterActionListener
then +1
else -1 till I completed this task.
Actually there
On Tue, Sep 2, 2008 at 9:23 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.0 release of Apache
MyFaces Commons out.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.commons v1.2.0 [1]
