[jbosstools-issues] [JBoss JIRA] (LOCUS-45) Do not deploy Locus artifacts to dl.jboss.org; only use nexus

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on LOCUS-45:
------------------------------------------

unless my memory is of locus was created before mars streams so not sure why we would ever have had a mars/locus content ? 

I really don't think we would want our download.jboss.org urls that is about builds and not just updatesite to automtically redirect to nexus snapshots.

Thus unless you point me to when we ever had content in mars related locus on download.jboss.org then deleting these seems perfectly valid.

> Do not deploy Locus artifacts to dl.jboss.org; only use nexus
> -------------------------------------------------------------
>
>                 Key: LOCUS-45
>                 URL: https://issues.jboss.org/browse/LOCUS-45
>             Project: JBoss Tools Locus
>          Issue Type: Feature Request
>    Affects Versions: 1.3.0
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 1.3.0
>
>
> Nick said:
> {quote}
> We can now publish to Nexus as well as to dl.jb.org. I can disable the
> publishing to dl.jb.org again if we no longer need that, and JUST use
> the Nexus deployment. {quote}
> Max said:
> {quote}
> I would disable all unnecessary publishing - it will just be forgotten
> and someone someday will rely on the dl.jb.org bits when we wouldn't
> want them to. Lets keep it as just one and locus for now is nexus bound. {quote}
> So... I've updated the job again [0] to disable the deploy-to-jboss.org part. Not sure if I should also remove the profile entirely from the Locus site/pom.xml [1].
> [0] https://github.com/jbdevstudio/jbdevstudio-ci/commit/d29e92afdc5f93adfbf10ee056b44d82b039748f
> [1] https://github.com/jbosstools/jbosstools-locus/blob/master/site/pom.xml#L184-L270



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)