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)" <de...@uima.apache.org> on 2010/10/22 22:44:20 UTC
[jira] Created: (UIMA-1907) drop distr source release, use instead
the standard source zip release
drop distr source release, use instead the standard source zip release
-----------------------------------------------------------------------
Key: UIMA-1907
URL: https://issues.apache.org/jira/browse/UIMA-1907
Project: UIMA
Issue Type: Improvement
Components: Build, Packaging and Test
Reporter: Marshall Schor
Assignee: Marshall Schor
Priority: Minor
Fix For: 2.3.1AS, 2.3.1SDK
The release process currently builds two "source release"s. One is ours, the other is the standard,
maven-built one, which is more-or-less guaranteed to match an svn checkout.
Our source release does some special things:
1) it sets executable bits. One might argue this is needed only in the /bin distr.
2) it copies stuff in uimaj-distr/src/main/readme to the "top level". Files copied include the LICENSE/NOTICE, RELEASE_NOTES, README, and some command scripts to manipulate the sources.
The custom src file adds a directory Eclipse, which has an Eclipse "launcher"
that runs the packageAllJavaSourcesIntoJar command. This might be droppable,
because our releases will now have the java sources for each project "attached"
in the maven sense, so if m2eclipse is being used, the sources should be fetched
automatically when needed.
The custom src file is also missing the DEPENDENCIES file, and is also missing 2
of the 3 aggregate- projects.
Do what is needed to make the standard source-release.zip build serve as the source distribution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1907) drop distr source release, use instead
the standard source zip release
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1907.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.3.1SDK)
(was: 2.3.1AS)
build-parent-pom-1
> drop distr source release, use instead the standard source zip release
> -----------------------------------------------------------------------
>
> Key: UIMA-1907
> URL: https://issues.apache.org/jira/browse/UIMA-1907
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: build-parent-pom-1
>
>
> The release process currently builds two "source release"s. One is ours, the other is the standard,
> maven-built one, which is more-or-less guaranteed to match an svn checkout.
> Our source release does some special things:
> 1) it sets executable bits. One might argue this is needed only in the /bin distr.
> 2) it copies stuff in uimaj-distr/src/main/readme to the "top level". Files copied include the LICENSE/NOTICE, RELEASE_NOTES, README, and some command scripts to manipulate the sources.
> The custom src file adds a directory Eclipse, which has an Eclipse "launcher"
> that runs the packageAllJavaSourcesIntoJar command. This might be droppable,
> because our releases will now have the java sources for each project "attached"
> in the maven sense, so if m2eclipse is being used, the sources should be fetched
> automatically when needed.
> The custom src file is also missing the DEPENDENCIES file, and is also missing 2
> of the 3 aggregate- projects.
> Do what is needed to make the standard source-release.zip build serve as the source distribution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.