Re: [jbosstools-dev] How old is ESB project?
The age of the project type is relevant because if it's a young
project and has not made it into JBDS yet, then we can change this
project structure without worrying about converting old users to the
new structure. If the structure is old and has made it into JBDS than
such conversion would be necessary.
That has nothing to do with age - no matter if
it was in JBDS or just
jbt it was released into a GA release long time ago (both JBT and JBDS).
But isn't this about *new* esb projects ? the module factory would still
just have to do its thing it is told based on the components file, is it
not ?
And no I did not receive an answer.
You received my answer, and you didn't
answer my questions ..? :)
/max
Max Rydahl Andersen wrote:
>> I'd like to make changes to an ESB project's structure and I want to
>> see
>> if everyone here is on the same page.
> Did you get any answers to this ?
>
> btw. I don't understand what the age of ESB projects has to do with
> your question ?
>
> Your suggestion is how it should work even for components.xml in old
> versions of WTP, right ?
>
>> <wb-resource deploy-path="/"
source-path="/build/classes"/>
>>
>> I want to see if anyone feels one way or the other about this. It would
>> make our module factories cleaner and less error prone. Thoughts?
>
> But isn't this opposite to how everything else works in WTP
> currently, right ? Or?
>
> /max