Jason van Zyl ha scritto:
>
> On 14 Jun 07, at 9:37 AM 14 Jun 07, Stefano Bagnara wrote:
>
>> Wendy Smoak ha scritto:
>>> On 6/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>>
>>>> Took me a few minutes so it doesn't hurt, I just exported the tag,
>>>> zipped it up, signed, and checksummed it:
>>>>
>>>> http://people.apache.org/~jvanzyl/maven-2.0.7/
>>>
>>> Thanks. Almost there... it needs LICENSE and NOTICE added. :)
>>>
>>> I have a note to add those files at the 'top' of each subproject so
>>> they're present when someone checks the source out from svn. The
>>> remote resources plugin can still do its thing for the jars.
>>
>> For Apache mime4j we use the assembly plugin to generate a source
>> package including NOTICE/LICENSE generated by the remote resources
>> plugin:
>> http://svn.apache.org/viewvc/james/mime4j/trunk/src/assemble/src.xml?revision=536368&view=markup
>>
>>
>
> Yes, I'm aware of how the assembly plugin works.
>
> Did you use the tag you used to create the release? Otherwise you're not
> using what what used to create the release. If you're running this from
> the release plugin then that's fine, otherwise it's not.
This question is interesting:
we run release:perform and we let maven do everything else: how do I
know if "I run this from the release plugin" or not ?
my assembly plugin is configured as follows:
----------------
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-1</version>
<configuration>
<descriptorSourceDirectory>${basedir}/src/assemble/</descriptorSourceDirectory>
</configuration>
<executions>
<execution>
<id>make-assembly</id> <!-- this is used for inheritance
merges -->
<phase>package</phase> <!-- append to the packaging phase. -->
<goals>
<goal>attached</goal> <!-- goals == mojos -->
</goals>
</execution>
</executions>
</plugin>
------------------
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
