myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Dudney <bdud...@mac.com>
Subject Re: faces-config.xml is missing in myfaces-all.jar in the 1.1.0 release.
Date Thu, 22 Sep 2005 19:25:25 GMT
No I've not checked it in yet because I'm waiting for discussion on  
the idea of making a 1_1_0 branch that we could do the emergency  
release from.

TTNF,

-bd-

On Sep 22, 2005, at 1:20 PM, Mike Kienenberger wrote:

> Is this supposed to be fixed in svn?
>
> I just did a complete checkout about an hour ago, and built it with
> "ant dist-all" and I'm getting the error below if I use myfaces-all,
> but not if I use myfaces.api, myfaces.impl, and tomahawk separately.
>
> java.lang.NoClassDefFoundError: org/apache/myfaces/config/ 
> FacesConfigurator
>     at  
> org.apache.myfaces.webapp.StartupServletContextListener.initFaces 
> (StartupServletContextListener.java:63)
>     at  
> org.apache.myfaces.webapp.StartupServletContextListener.contextInitial 
> ized(StartupServletContextListener.java:46)
>
> Or is this a case of the cure being worse than the disease?
>
> -Mike
>
> On 9/22/05, Bill Dudney <bdudney@mac.com> wrote:
>
>> Since this is simply a build problem perhaps we could copy the tag
>> 1_1_0 to a branch and update only the build.xml file then build a new
>> release.
>>
>> This would be simple, quick and more or less safe.
>>
>> Would we have to rerun the TCK? As long as we trust our tag it should
>> be fine. Correct?
>>
>> TTFN,
>>
>> -bd-
>>
>> On Sep 22, 2005, at 12:08 PM, Werner Punz wrote:
>>
>>
>>> Bruno Aranda wrote:
>>>
>>>
>>>> This is causing many troubles to users now as we can see from
>>>> questions in the list.
>>>> faces-config.xml is not included in the build because of
>>>> MYFACES-598,
>>>> when passing -Dskip.sandbox to the build process the file is not
>>>> included. I think this is important enough and we should do  
>>>> something
>>>> about this. I don't know if it is possible to include the file  
>>>> in the
>>>> current release but I don't think it is good to development to  
>>>> touch
>>>> an already released thing.
>>>>
>>>> My opinion here is that we should release a maintenance release  
>>>> 1.1.1
>>>> as soon as possible. Waiting for thoughts on this.
>>>>
>>>> Regards,
>>>>
>>>> Bruno
>>>>
>>>>
>>>>
>>> I cannot vote yet, but due to the fact that many newbys probably
>>> will try to use the
>>> new release, due to the non beta status and TCK status,  and this
>>> is really a showstopper for many, I´d say get the fix
>>> out ASAP!
>>>
>>>
>>>
>>>
>>
>>
>


Mime
View raw message