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

Tong Fin commented on UIMA-816:
-------------------------------

Hi Marshall,
(Sorry, might be the wrong JIRA to add comment)

My understanding is that the manifest.mf of each plug-in is "generated" by 
maven.
The following is some observations after I try to create a new Eclipse 
workspace to work with Apache UIMA.
 - Each line of the manifest.mf file has a max 70 chars
 - Each package in the "Export -Package" section contains a "uses" directive 
and some lines are "very long" (more than 500 chars) which cause an error ("the 
line is too long") in Manifest editor.

Is it the expected behavior ?

If I need to edit the manifest.mf file, how to do that ? Edit pom.xml or edit 
manifest.mf as usual ?
The "the line is too long" error may prevent user to edit manidest.mf.

-- Tong

> maven build - Eclipse plugin build improvements
> -----------------------------------------------
>
>                 Key: UIMA-816
>                 URL: https://issues.apache.org/jira/browse/UIMA-816
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.2.2
>
>
> The current Eclipse plugins have complex maven poms - simplify by factoring 
> out common things to a common super pom for the eclipse plugins, which will, 
> in turn, inherit from the uimaj super pom.  
> Put this new pom in the uimaj project - no need for another project just for 
> this.  
> Add configuration info so the eclipse:eclipse plugin does the right class 
> path setup even when it is run from the top level.  This will allow cd to the 
> uimaj project, and running eclipse:eclipse there, and having it work, as well 
> as working in individual project directories.
> For POMs which inherit from our project poms, replace the <groupId> with a 
> comment saying it is inherited from the super pom, and replace the <version> 
> with a comment saying it's inherited from the super pom.
> Make the eclipse plugin super pom have the right form of the version (the one 
> with the "." instead of the "-" in front of the "incubator" token).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to