[JBoss JIRA] Created: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
5:35 p.m.
Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip
files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.M4
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/jira/browse/JBDS-857?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBDS-857:
----------------------------
Attachment: jbds-857part1.patch
first pass. cleaning up refs to obsolete stuff.
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.M4
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:54 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/jira/browse/JBDS-857?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBDS-857:
-------------------------------------
Fix Version/s: 3.0.0.CR2
(was: 3.0.0.M4)
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 3.0.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.CR2
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:09 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/jira/browse/JBDS-857?page=com.atlassian.jira.plugi...
]
Denis Golovin updated JBDS-857:
-------------------------------
Component/s: Build
installer
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build, installer
Affects Versions: 3.0.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.CR2
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:19 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/jira/browse/JBDS-857?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBDS-857:
----------------------------
Fix Version/s: LATER
(was: 3.0.0.CR2)
Priority: Optional (was: Major)
This is not urgent.
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build, installer
Affects Versions: 3.0.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/jira/browse/JBDS-857?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBDS-857:
----------------------------
Issue Type: Feature Request (was: Bug)
Affects Version/s: 3.0.0.CR1
(was: 3.0.0.M4)
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:54 a.m.
New subject: [JBoss JIRA] Work started: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/browse/JBDS-857?page=com.atlassian.jira.plugin.sys...
]
Work on JBDS-857 started by Nick Boldt.
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
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
12:56 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/browse/JBDS-857?page=com.atlassian.jira.plugin.sys...
]
Nick Boldt commented on JBDS-857:
---------------------------------
First step here is to get the build to use JBT update site as upstream aggregateRepo
dependency. In progress here:
http://svn.jboss.org/repos/devstudio/workspace/nickboldt/
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-4....
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
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
12:58 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/browse/JBDS-857?page=com.atlassian.jira.plugin.sys...
]
Nick Boldt edited comment on JBDS-857 at 10/27/10 1:58 AM:
-----------------------------------------------------------
First step here is to get the build to use JBT update site as upstream aggregateRepo
dependency. In progress here:
http://svn.jboss.org/repos/devstudio/workspace/nickboldt/
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-4....
If this works, then there are two TODOs left to complete the migration from 'build all
the components in JBDS' to 'reuse select components':
devstudio-workspace-nickboldt/devstudio-installer/build.xml:262:
exclude JBT components not in JBDS
devstudio-workspace-nickboldt/releng/org.jboss.ide.eclipse.releng/builders/common/aggregateRepos.jbds.properties:59:
add more features here for the rest of JBT inclusions
was (Author: nickboldt):
First step here is to get the build to use JBT update site as upstream aggregateRepo
dependency. In progress here:
http://svn.jboss.org/repos/devstudio/workspace/nickboldt/
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-4....
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
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
1 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/browse/JBDS-857?page=com.atlassian.jira.plugin.sys...
]
Nick Boldt edited comment on JBDS-857 at 10/27/10 1:59 AM:
-----------------------------------------------------------
First step here is to get the build to use JBT update site as upstream aggregateRepo
dependency. In progress here:
http://svn.jboss.org/repos/devstudio/workspace/nickboldt/
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-4....
If this works, then there are two TODOs left to complete the migration from 'build all
the components in JBDS' to 'reuse select components. Look for "TODO:
JBDS-857":
devstudio-workspace-nickboldt/devstudio-installer/build.xml:262:
exclude JBT components not in JBDS
devstudio-workspace-nickboldt/releng/org.jboss.ide.eclipse.releng/builders/common/aggregateRepos.jbds.properties:59:
add more features here for the rest of JBT inclusions
was (Author: nickboldt):
First step here is to get the build to use JBT update site as upstream aggregateRepo
dependency. In progress here:
http://svn.jboss.org/repos/devstudio/workspace/nickboldt/
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-4....
If this works, then there are two TODOs left to complete the migration from 'build all
the components in JBDS' to 'reuse select components':
devstudio-workspace-nickboldt/devstudio-installer/build.xml:262:
exclude JBT components not in JBDS
devstudio-workspace-nickboldt/releng/org.jboss.ide.eclipse.releng/builders/common/aggregateRepos.jbds.properties:59:
add more features here for the rest of JBT inclusions
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
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
9:44 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/browse/JBDS-857?page=com.atlassian.jira.plugin.sys...
]
Nick Boldt resolved JBDS-857.
-----------------------------
Resolution: Won't Fix
Obsoleted by https://jira.jboss.org/browse/JBDS-1351
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
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
9:44 p.m.
New subject: [JBoss JIRA] Work stopped: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
[
https://jira.jboss.org/browse/JBDS-857?page=com.atlassian.jira.plugin.sys...
]
Work on JBDS-857 stopped by Nick Boldt.
Installer build should not depend on bundle.eclipse step or on
creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/browse/JBDS-857
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Build, installer
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: LATER
Attachments: jbds-857part1.patch
bundle.eclipse is basically and empty method call, but there's a lot of leftover
properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted
while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a
from the update zip" . If done correctly, we may even end up with ONE installer
instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
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
5106
days inactive
5518
days old
jbosstools-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Denis Golovin (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)