waaay to many jars in junittests
by Max Rydahl Andersen
Hi guys,
Why are we adding *tons* of duplicated jars and complete JSF/Seam projects just to unittests a few pages with templates?!
I can't beleive all of those files are really necessary to check if a myfaces template page will render correctly.
Could we please make sure our tests just include what is needed and not add tons of unused things. Thanks!
/max
17 years
Re: [jbosstools-dev] Support of ADF components in VPE survey
by Sergey Vasilyev
Pete Muir wrote:
> Assuming we are really talking about Trinidad, not ADF (ADF is the non
> opensource varient).
>
> Coexist with Seam (very) well.
>
> Coexist with RichFaces ok (there is an integration package). Alex can
> comment better.
>
> No extra issues when you use Seam+RF+Trinidad. You can see the
> seamdiscs example for it in operation.
>
> On 21 Jan 2008, at 16:51, Max Rydahl Andersen wrote:
>
>> On Mon, 21 Jan 2008 17:50:27 +0100, Pete Muir <pete.muir(a)jboss.org>
>> wrote:
>>
>>> Technically good, visually appalling.
>>
>> any known issues/recommendations in context of Seam/richfaces ? Do
>> they coexist well/bad?
>>
>> /max
>>
>>>
>>> On 21 Jan 2008, at 16:40, Max Rydahl Andersen wrote:
>>>
>>>> Do we have any coverage of it today ?
>>>>
>>>> I've cc'ed Pete and Gavin to hear about their experience/feedback
>>>> on ADF.
>>>>
>>>> /max
>>>>
>>>>> Hi!
>>>>>
>>>>> I would like to ask all of you about supporting ADF Faces Components
>>>>> (http://www.oracle.com/technology/products/adf/adffaces/
>>>>> index.html) in
>>>>> our Visual Page Editor. Set of ADF components consists of over 100
>>>>> components. Does the support of ADF components still relevant for us?
>>>>>
>>>>> Sergey
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>>>
>>>
>>
>>
>>
>> --
>> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>
Unfortunately we are supporting the ADF Faces Components (old versions
from uri="http://xmlns.oracle.com/adf/faces/EA10" till
uri="http://xmlns.oracle.com/adf/faces/EA13").right now. It is a legacy
from Exadel Studio. And I'm speaking about supporting of ADF (not
opensource) and Trinidad (http://myfaces.apache.org/trinidad).
Sergey
17 years
Compilation errors in WTP3 / Eclipse 3.4 aka Ganymede compatibility
by Marshall Culpepper
Hey everyone..
I just imported our codebase into Eclipse 3.4 milestone 4 w/ WTP 3.0 M4
to take a look at our compatibility. Currently we have a number of
compilation problems, most of them seem to be internal API
dependencies.. but I didn't go over every single one.For reference, I
downloaded all the Eclipse 3.4/WTP 3.0 stuff from the following URL:
http://download.eclipse.org/webtools/downloads/drops/R3.0/S-3.0M4-2008010...
To summarize the errors, it looks they are pretty much all over the
board. I'm seeing deprecated and changed internal APIs being used in all
of our components from Hibernate Tools, JBossAS Tools, VPE, Common, to
even the older JBossIDE core.
*Most* of the errors I'm seeing look to be relatively trivial to fix,
but again I haven't gone over every single one. Usually it's a change of
a method / class name, or a field that isn't visible anymore. Also keep
in mind that getting stuff compiling doesn't mean it actually works, so
there might be some bad methods / workarounds we used in old code that
won't work with new libraries.
As Max said today, I think it would be prudent if we branched now so we
can make sure that we have enough time to file bugs and get everything
working before the WTP3.0 / Ganymede freeze date which is coming up in a
few months.
17 years
