[jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
Nick Boldt (JIRA)
issues at jboss.org
Mon Oct 26 14:02:00 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122075#comment-13122075 ]
Nick Boldt commented on JBIDE-21012:
------------------------------------
Here's a way we can build the update site zip, attach it to deployment, and still use the fully-qualified suffix.
https://github.com/jbosstools/jbosstools-freemarker/pull/54
Next I need to see if this works in Jenkins/Nexus...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker_master >=308
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list