[jbosstools-dev] How old is ESB project?
Rob Stryker
rob.stryker at redhat.com
Mon Jul 27 15:38:35 EDT 2009
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.
And no I did not receive an answer.
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
More information about the jbosstools-dev
mailing list