db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5272) Stop building Eclipse plugins as Derby release artifacts
Date Fri, 01 Jun 2012 16:12:23 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-5272:

    Attachment: derby-5272-02-aa-removeFromReleaseScript.diff

Attaching derby-5272-02-aa-removeFromReleaseScript.diff. This patch removes the generation
of eclipse plugins from the top level release script.

I did not remove the target which actually generates the plugin. I don't think we should remove
that target unless we are sure that it's useless to the eclipse community.

We agreed that 10.8.2 was the last release which would carry eclipse plugins. I ported the
patch to 10.8 because we may vet a 10.8.3 release later this year. I do not intend to port
this fix to any other branches. No-one builds releases from the 10.7 branch and the top-level
release script is only useful from that release forward.

Committed to the trunk at subversion revision 1345254.

Ported to 10.9 branch at subversion revision 1345261.

Ported to 10.8 branch at subversion revision 1345264.

Touches the following file:

M       build.xml

> Stop building Eclipse plugins as Derby release artifacts
> --------------------------------------------------------
>                 Key: DERBY-5272
>                 URL: https://issues.apache.org/jira/browse/DERBY-5272
>             Project: Derby
>          Issue Type: Task
>          Components: Eclipse Plug-in
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: derby-5272-01-aa-blurbOnDownloadPage.diff, derby-5272-02-aa-removeFromReleaseScript.diff
> A consensus has developed that we should stop building the Eclipse plugins as part of
Derby releases. 10.8.2 will be the last release which includes these artifacts. After that,
people who depend on these plugins will need to build them themselves and, if possible, find
a place to publish the plugins. This topic has been discussed on the following email threads:
> http://old.nabble.com/Eclipse-plugins-to31524444.html#a31524444
> http://old.nabble.com/draft-of-message-to-derby-user-concerning-the-future-of-the-Eclipse-plugins-to31691740.html#a31691740
> http://old.nabble.com/future-of-the-Derby-Eclipse-plugins-to31708734.html#a31708734
> This issue tracks tasks needed to accomplish this goal.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message