a tried to keep it to have unique name for project but the same for
modules, but we have some problems in deployment with that.
ok - makes sense.
We need to consider fixing this in seam-gen; their application.xml could
list those three different key's.
/max
denis
Max Rydahl Andersen wrote:
> Another question:
>
> Why do we need to have our own copy of application.xml when seam-gen
> has one ?
>
> We need to get seam-gen fixed if this is broken somehow.
>
> /max
>
>> Hi Denis,
>>
>> I stepped over some code I don't understand why is needed in Seam
>> runtime management.
>>
>> SeamRuntimeListConverter1 (weird class name, why an 1 at the end ?),
>> seem to do some really weird conversion between maps and strings on
>> the form
>>
>> "name|some Name|version|1123123|homeDir|somedir|default|true"
>>
>> ...why are we storing such weird strings in preferences ?
>> (Is that normal for eclipse preferences ? That looks very
>> unmaintainable)
>>
>> Why isn't the info about what runtime is default a single named
>> preference instead of maintained on each runtime ?
>>
>> And why are these classes in a package called
>> org.seam.core.project.facet ? These things are and should be
>> independent of WTP facets (and SeamRuntimeListConverter1 sound like
>> something that should be inside the internal package)
>>
>> /max
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>