db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5272) Stop building Eclipse plugins as Derby release artifacts
Date Tue, 02 Oct 2012 18:17:07 GMT

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

Myrna van Lunteren updated DERBY-5272:
--------------------------------------

    Attachment: DERBY-5272_site.stat2
                DERBY-5272_site.diff2

Attaching a new version of the patch.

When I looked closer at the release pages, I noticed there were references to the plugin_help
documentation in the web site on the release pages for releases that had a plugin, and my
removing those details would cause broken links. 

As far as I can see, the plugin_help directory on the web site is a copy of the topics under
http://svn.apache.org/viewvc/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/.
It's a pity we have this duplication of information, but it isn't much out of date - the only
difference being the changes resulting from DERBY-2376 (revision 531595: http://svn.apache.org/viewvc?view=revision&revision=531595).

So this second patch doesn't actually remove the old files, instead, it adds a new page, derby_plugin_info,
which is referenced in the new updated menu. This way, when going into the Downloads tab and
picking one of the releases that had a plugin available, users can still go to the help, and
then get the same information as before via the menu, which is still expanded for those pages.

I also forgot to svn revert a couple of png files in the first patch. 

Re the cgi vs. html for 10.9.1 and 10.8.2.2 - I looked at the release publication page where
the creation of these files is described, and I think it's ok that I don't get changes to
the .cgi files, and that the mirrorring doesn't work when I'm just opening the files on my
machine in the browser.
                
> 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: 10.9.1.0
>            Reporter: Rick Hillegas
>         Attachments: derby-5272-01-aa-blurbOnDownloadPage.diff, derby-5272-02-aa-removeFromReleaseScript.diff,
DERBY-5272_site.diff, DERBY-5272_site.diff2, DERBY-5272_site.stat, DERBY-5272_site.stat2,
derby_plugin.html
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message