You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2009/12/01 21:29:20 UTC
[jira] Created: (UIMA-1689) fix some miscompares between svn export
and source-distribution
fix some miscompares between svn export and source-distribution
---------------------------------------------------------------
Key: UIMA-1689
URL: https://issues.apache.org/jira/browse/UIMA-1689
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout, Core Java Framework, Sandbox
Reporter: Marshall Schor
Assignee: Marshall Schor
Priority: Minor
Fix For: 2.3S, 2.3, 2.3AS
It was noted in reviewing our release candidate that a diff between our source distribution and the export of the svn tag are somewhat different. Some of these are due to the source distribution copying things like licenses, disclaimers, readmes, etc., to the top level of the source distribution - so these are fine. Others are due to things we use in development, which are not used to build the distributions. (example: some build scripts like signEclipseUpdateSite, or the project uimaj-jet-expander - only used when changing the jcas gen templates and regenerating the corresponding java code, or the project uimaj-internal-tools - I think not currently used).
Others are left-overs. For instance, the docs for the PearPackagingMavenPlugin - these were merged into the main tools doc; however the old docs are still in SVN (but are not put into the source distribution). I think I want to leave them there, because I think in the future we may be breaking out that project as a separately released item, and maybe adding to the maven tooling even...
Finally, there are some things that should be fixed. For instance, the docbook tooling downloads the FOP version. but it also seems that we've checked into SVN some older levels of the FOP jar. These should be removed.
Check the differences for uimaj, uima-as, and the Sandbox, and reduce the discrepancies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1689) fix some miscompares between svn export
and source-distribution
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1689.
--------------------------------
Resolution: Fixed
> fix some miscompares between svn export and source-distribution
> ---------------------------------------------------------------
>
> Key: UIMA-1689
> URL: https://issues.apache.org/jira/browse/UIMA-1689
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout, Core Java Framework, Sandbox
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.3S, 2.3, 2.3AS
>
>
> It was noted in reviewing our release candidate that a diff between our source distribution and the export of the svn tag are somewhat different. Some of these are due to the source distribution copying things like licenses, disclaimers, readmes, etc., to the top level of the source distribution - so these are fine. Others are due to things we use in development, which are not used to build the distributions. (example: some build scripts like signEclipseUpdateSite, or the project uimaj-jet-expander - only used when changing the jcas gen templates and regenerating the corresponding java code, or the project uimaj-internal-tools - I think not currently used).
> Others are left-overs. For instance, the docs for the PearPackagingMavenPlugin - these were merged into the main tools doc; however the old docs are still in SVN (but are not put into the source distribution). I think I want to leave them there, because I think in the future we may be breaking out that project as a separately released item, and maybe adding to the maven tooling even...
> Finally, there are some things that should be fixed. For instance, the docbook tooling downloads the FOP version. but it also seems that we've checked into SVN some older levels of the FOP jar. These should be removed.
> Check the differences for uimaj, uima-as, and the Sandbox, and reduce the discrepancies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.