[
https://issues.apache.org/jira/browse/UIMA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571601#action_12571601
]
Marshall Schor commented on UIMA-816:
-------------------------------------
The current approach is to have development edit manifest information in only
one place, and have that work for both maven and Eclipse building. That place
is the maven POM for the component.
The maven "build" operation will then generate the manifest needed by Eclipse,
and it will observe the line length restrictions, I think. When I look at the
"Export-Package" section generated by maven build, I do not see any long lines;
when the data is long, the maven build is splitting the line into multiple
lines.
Can you say how you are generating the manifest file with the long lines?
> 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.
