[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621159#comment-12621159 ] 

Nick Boldt commented on JBIDE-6985:
-----------------------------------

Dumping a new file into the aggregate zips is doable - already doing something along those lines for adding index.html to site/ folder before zipping. Can do in both branches.

> Add NOT_DROPINS + readme or similar into our updatesite zips
> ------------------------------------------------------------
>
>                 Key: JBIDE-6985
>                 URL: https://issues.jboss.org/browse/JBIDE-6985
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Build/Releng
>    Affects Versions: 3.2.x
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>             Fix For: 3.2.2, 3.3.0.M3
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Just an idea that occurred to that since updatesite zips and our old dropin compatible zips has same layout users keep trying to put them into dropins folder.
> Could would add a "NOT_FOR_DROPINS" with text explaining this an updatesite and (or at least) a readme or instructions file outlining:
> "This file is an Eclipse update zip to be used from within an Eclipse installations update manager.
> Do *not* unzip this zip into Eclipse directly nor into its dropins folder - it will *not* work.
> Use the Eclipse P2 Update Manager UI to perform the installation."
> Just a thought after seeing multiple users asking why their installation does not work anymore.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira