On 2/2/2013 6:57 AM, Peter Klügl wrote:
> Hi,
>
>
> Am 01.02.2013 23:18, schrieb Marshall Schor:
>> On 2/1/2013 8:15 AM, Peter Klügl wrote:
>>> Hi,
>>>
>>> the third release candidate of the sandbox project Apache UIMA TextMarker is
>>> ready for voting. This vote also includes our new composite repository.
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapacheuima-192/
>>>
>>> SVN tag:
>>> https://svn.apache.org/repos/asf/uima/sandbox/textmarker/tags/textmarker-2.0.0-rc3
>>>
>>>
>>>
>>> Composite repository with three update sites: uimaj, uima-as and
>>> textmarker-2.0.0:
>>> http://people.apache.org/~pkluegl/uima-releases/textmarker-2.0.0-rc3/eclipse-update-site
>>>
>>>
>>>
>>> The issues fixed are in the RELEASE_NOTES.html in the src/bin packages.
>>> They can also be found here:
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.0.0TextMarker%22%20AND%20component%20%3D%20TextMarker%20AND%20status%20in%20(Resolved%2C%20Closed)%20ORDER%20BY%20priority%20DESC
>>>
>>>
>>>
>>>
>>> ONLY FOR REVIEWING:
>>>
>>> Documentation (pdf file):
>>> http://people.apache.org/~pkluegl/uima-releases/textmarker-2.0.0-rc3/tools.textmarker.book.pdf
>>>
>>>
>>>
>>> Archive with all sources (also present in the staging repository):
>>> http://people.apache.org/~pkluegl/uima-releases/textmarker-2.0.0-rc3/textmarker-2.0.0-source-release.zip
>>>
>>>
>> Note: the source-release.zip file belongs on the apache mirror distribution;
>> some recent discussions on the infra list say this is required. (Maven went 
>> to
>> the trouble to put all their source-release.zip files there.
>>
>> The source-release.zip file is not useful to upload to Maven Central, so it
>> should probably not routinely be put there (unless you have a need for
>> maven-style accessing of that, which I think is unlikely).  It will just 
>> take up
>> room there.
>>
>> The individual sources.jar files are useful to upload to Maven Central, 
>> though -
>> the m2e plugin support can automatically fetch those when Eclipse wants to 
>> look
>> at the source.
>
>
> Do you have an idea, how I can prevent the upload of the source-release.zip?

You can try configuring the assembly plugin with the additional parameter attach
set to false.

This will leave the assembly in the target dir of the top level project, but
won't "attach" it to the set of artifacts that the install and later steps use
to move those artifacts into maven repositories, I think.

-Marshall

>
> Best,
>
> Peter
>
>> -Marshall
>>>
>>> Please vote on release:
>>>
>>> [ ] +1 OK to release
>>> [ ]  0 Don't care
>>> [ ] -1 Not OK to release, because ...
>>>
>>> Thanks.
>>>
>>> Peter
>>>
>
>

Reply via email to