Hi Ulrich,
We have moved some projects to Maven 2. We�re using WebObjects Library
present on WOLips to deal with WebObjects dependencies and Maven to
manage other dependencies. This solution works with the WOLips->Install
option, but doesn�t work for maven builds since the WO classes are missing.
If I understood, you proposed to rebuild the WO frameworks as JARs and
put them into maven repository as any other dependency. Then is just a
matter of setup WO dependencies like any other dependency. Those new
JARs include the classes, eomodels, components and whatever a WO
framework could possibly have. And after a complete maven build of a WO
Application, i.e., we will have an application JAR that can be unzipped
as a WOA at last. Is that right?
Best Regards,
Henrique
Ulrich K�ster wrote:
>
> Am 19.08.2006 um 20:52 schrieb RedBugz Software:
>
>> On 8/18/06, Henrique Prange <hprang..mail.com> wrote:
>>> I've also realized that.
>>>
>>> We're moving all our projects (not WO) to Maven 2. We want to migrate WO
>>> projects too, but (for a complete support of maven features) we need a
>>> plug-in for Maven that define an archetype for WO Applications and
>>> Frameworks and a specific way to build, deploy and manage WO
>>> dependencies using that tool.
>>>
>>> We have to develop this kind of plug-in for Maven 2. Is the rest of the
>>> community interested in this matter? Should we collaborate if already
>>> exists any effort in this field?
>>
>> We're also looking at moving our non-WO projects to Maven 2, and one
>> of our guys started looking at what it would take to get Maven2 to
>> play nice with WO frameworks as dependencies, but we didn't get very
>> far.
>
> The trick is to treat them as jars. :-)
>>
>> I think it would be great to collaborate on something like this.
>
>
> For sure. We have the stuff working for maven 1.0.2.
>
>>
>> Logan
>
>
This archive was generated by hypermail 2.0.0 : Mon Aug 21 2006 - 23:06:52 EDT