[jbosstools-issues] [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)

Nick Boldt (JIRA) issues at jboss.org
Thu Aug 24 15:58:00 EDT 2017


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

Nick Boldt commented on JBIDE-24798:
------------------------------------

Last time Browsersim got an actual code change was on Feb 27, 2017 so this is hardly an urgent requirement. 

However, the last time Browsersim 3.8.4 snapshot was pushed to Nexus [1] was on Aug 2, 2017, which suggests we're missing two more commits [2] in August. 

[1] https://repository.jboss.org/nexus/#nexus-search;gav~~browsersim~~~
[2] https://github.com/jbosstools/jbosstools-browsersim/commits/master

And I don't see recent browsersim zips here, either:

http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-browsersim_master/



> 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: Critical
>             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/Devstudio/view/devstudio_master/job/jbosstools-browsersim_master/
> Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...*



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list