12:57 a.m.
Add NOT_DROPINS + readme or similar into our updatesite zips
------------------------------------------------------------
Key: JBIDE-6985
URL: https://jira.jboss.org/browse/JBIDE-6985
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 3.2.x
Reporter: Max Andersen
Assignee: Nick Boldt
Fix For: 3.2.x
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:09 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://jira.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6985:
-----------------------------------
I had thought that the fact that these files are called "Update" would be clear
enough that they're not "runnables" for dropins; clearly this is not the
case.
So... where would you put this text?
Would calling the zips "p2 repo" help? Or could we JUST STOP PROVIDING them?
Do we really need more than these four things?
a) an update site (all-in-one)
b) an update site zip (all-in-one)
c) sources zip
d) p2.director script for scripted installation
(http://voxel.dl.sourceforge.net/project/jboss/JBossTools/installJBossTool...)
I guess the problem here is the installation instructions page?
https://www.jboss.org/tools/download/installation
and
https://www.jboss.org/tools/download/installation/update_3_2.html#fromzip
Add NOT_DROPINS + readme or similar into our updatesite zips
------------------------------------------------------------
Key: JBIDE-6985
URL: https://jira.jboss.org/browse/JBIDE-6985
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 3.2.x
Reporter: Max Andersen
Assignee: Nick Boldt
Fix For: 3.2.x
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick updated JBIDE-6985:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 3.2.2
3.3.0.M3
(was: 3.2.x)
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: Max Rydahl Andersen
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
11 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-6985:
------------------------------------------
Max/Nick, is this resolvable for both 3.2.2 and 3.3.M?
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: Max Rydahl Andersen
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
2:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6985:
--------------------------------------------
Nick, users dont see that page when using the zip.
Hence why I suggest we put a README.TXT in the root outlining this is not for dropins.
im ok awaiting 3.3.x for this if its not trivial to add in the parent pom.
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: Max Rydahl Andersen
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
5:41 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-6985:
---------------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
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
5:41 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6985:
--------------------------------------------
for you to look at while im away - not sure if there is a magic wand for this one beyond
only doing it in 3.3.x?
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
12:47 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
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
4:52 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-6985:
-----------------------------------
New README.installation.txt files added to 32x [1] and 33x [2,3] streams' aggregate
update sites for JBT. Not bothering for JBDS for now.
Also updated the installation page [4] to mark "Runnable" zips as no longer
provided/supported, and only available up to JBT 3.1.
--
[1]
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/build...
[2]
http://svn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/README.i...
[3]
http://svn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/READ...
[4] https://www.jboss.org/tools/download/installation
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
4:52 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-6985:
------------------------------
Comment: was deleted
(was: 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
4:23 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Nick Boldt resolved JBIDE-6985.
-------------------------------
Resolution: Done
Builds locally so should be fine in Hudson too.
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
7:44 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-6985) Add NOT_DROPINS + readme or similar into our updatesite zips
[
https://issues.jboss.org/browse/JBIDE-6985?page=com.atlassian.jira.plugin...
]
Jiri Peterka closed JBIDE-6985.
-------------------------------
Links and docs verified.
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.M1, 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
5339
days inactive
5713
days old
jbosstools-issues@lists.jboss.org
11 comments
5 participants
participants (5)
-
Brian Fitzpatrick (JIRA) -
Jiri Peterka (JIRA)
-
Max Andersen (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)