[ 
https://issues.apache.org/jira/browse/UIMA-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878848#comment-13878848
 ] 

Marshall Schor commented on UIMA-3575:
--------------------------------------

I asked on Jan 16 2013 on Apache's infrastructure list if build tooling used by 
our project (but which is not part of what we consider out distributed 
artifacts) needed to be put on the Apache mirroring system.  I got an answer 
which said no, it just had to be in the SVN under the Apache License V2; they 
are not themselves part of the "product".

There was one other reply which said that person also concurred.

So, for build tooling for our project, which are not considered part of the 
products we release, but are just things used to build them, these don't need 
to be mirrored onto the apache mirror system; they are just put up at Maven 
Central.

That's why you don't find the uima-wide parent-pom appearing as a source.zip on 
the apache mirror system.

I think there is no need for any Fedora packaging of uimaj and uima-addons to 
include the parent-pom artifact; build tooling artifacts needed by Maven are 
automatically fetched by Maven as needed when running the Maven build tooling 
to build-from-sources (of course, that would entail installing "Maven" on your 
target system - see http://uima.apache.org/one-time-setup.html#maven-setup ).  

Can you please see if you can do your packaging without including the 
parent-pom build tooling?

> parent-pom don't include the license file
> -----------------------------------------
>
>                 Key: UIMA-3575
>                 URL: https://issues.apache.org/jira/browse/UIMA-3575
>             Project: UIMA
>          Issue Type: Bug
>          Components: Build, Packaging and Test
>    Affects Versions: parent-pom-8
>         Environment: Fedora all
>            Reporter: gil cattaneo
>             Fix For: parent-pom-9
>
>
> Not available LICENSE file in source directory structure
> Please. Added license and copyright notice.
> the fedora pakaging guideline is very strictly precise about this problem
> https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text
> thanks
> regards



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to