[JBoss JIRA] (JBIDE-24798) Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24798?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24798:
-------------------------------
Description:
After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata).
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*
Also need to update link on http://tools.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.html#zips to 3.8.100, not 3.8.4
was:
After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata).
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*
Also need to update link on http://tools.stage.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.ht... to 3.8.100, not 3.8.4
> Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24798
> URL: https://issues.jboss.org/browse/JBIDE-24798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, build, updatesite
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.5.1.AM2
>
>
> After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata).
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*
> Also need to update link on http://tools.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.html#zips to 3.8.100, not 3.8.4
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24798) Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24798?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24798:
-------------------------------
Description:
After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata).
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*
Also need to update link on http://tools.stage.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.ht... to 3.8.100, not 3.8.4
was:
After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata).
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*
> Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24798
> URL: https://issues.jboss.org/browse/JBIDE-24798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, build, updatesite
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.5.1.AM2
>
>
> After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata).
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*
> Also need to update link on http://tools.stage.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.ht... to 3.8.100, not 3.8.4
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4518) Installer creates multiple uninstallers for one location
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4518?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4518:
--------------------------------
Summary: Installer creates multiple uninstallers for one location (was: Installer create new DevSuite Instance in Windows control panel when installing over previous installation)
> Installer creates multiple uninstallers for one location
> --------------------------------------------------------
>
> Key: JBDS-4518
> URL: https://issues.jboss.org/browse/JBDS-4518
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.1.0.AM1
>
>
> Installer creates new control panel item every time it gets to install page. In case of installing in the same default location it creates another Red Hat Development Suite' item in control panel. In case. In case uninstall is called only one item is going to be deleted and all others will fail for uninstall attempt.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4518) Installer create new DevSuite Instance in Windows control panel when installing over previous installation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4518?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4518:
--------------------------------
Fix Version/s: 11.1.0.AM1
Story Points: 5
Sprint: devex #136 August 2017
> Installer create new DevSuite Instance in Windows control panel when installing over previous installation
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4518
> URL: https://issues.jboss.org/browse/JBDS-4518
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.1.0.AM1
>
>
> Installer creates new control panel item every time it gets to install page. In case of installing in the same default location it creates another Red Hat Development Suite' item in control panel. In case. In case uninstall is called only one item is going to be deleted and all others will fail for uninstall attempt.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4518) Installer create new DevSuite Instance in Windows control panel when installing over previous installation
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4518:
-----------------------------------
Summary: Installer create new DevSuite Instance in Windows control panel when installing over previous installation
Key: JBDS-4518
URL: https://issues.jboss.org/browse/JBDS-4518
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 11.1.0.AM1
Reporter: Denis Golovin
Installer creates new control panel item every time it gets to install page. In case of installing in the same default location it creates another Red Hat Development Suite' item in control panel. In case. In case uninstall is called only one item is going to be deleted and all others will fail for uninstall attempt.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months