Hi Bill,
per our earlier discussion, we may split the code into extra modules,
so that we do not have to filter classes from a single module. It
will still require combining multiple modules though. I recall I was
able to do that somehow when I was investigating an assembly for the
plugin environment:
http://svn.apache.org/repos/asf/incubator/cayenne/main/branches/
PROTO-3.0/modeler/assembly.xml
Format can be set to "jar" and then a bunch of filesets can be used
to build the contents.
Not sure if multiple levels of assembly are possible (i.e. one being
jar, and another being tar.gz that includes jars).
Andrus
On Aug 7, 2006, at 7:48 AM, Bill Dudney wrote:
> Sorry All,
>
> I was not able to complete the assembly. I am not sure how to get
> the equivalent of the cayenne.jar and cayenne-client-nodeps.jar
> (exclude or include some other jar contents, filter etc). looks
> like I have to use the antrun plugin but I'm not sure how to do
> that via an assembly. I have a couple of ideas but I am going to
> have to do some more experimentation to get it right.
>
> I'll keep you posted.
>
> TTFN,
>
> -bd-
>
> On Aug 4, 2006, at 3:36 PM, Bill Dudney wrote:
>
>> Hi Andrus,
>>
>> Sorry I've been sucked into day job last couple of days so I'm on
>> it now.
>>
>> TTFN,
>>
>> -bd-
>> On Aug 4, 2006, at 1:44 PM, Andrus Adamchik wrote:
>>
>>> Bill,
>>>
>>> Any word on the M2 assembly support? Once we have that in some
>>> form, I can restore the nightly builds that have been down since
>>> the start of the Maven migration.
>>>
>>> Andrus
>>
>
>
This archive was generated by hypermail 2.0.0 : Mon Aug 07 2006 - 09:48:34 EDT