[jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-21012:
------------------------------------

That's true in theory as of this moment, it's currently impossible.

We need a way to ensure that there's an unpacked update site in nexus, such as:

https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/

Currently that folder exists but is empty.

Once it has content, we can start using it in parent pom [0] and composite*.xml [1] in place of what's currently there.

[0] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L102 
[1] http://download.jboss.org/jbosstools/neon/snapshots/builds/_composite_/core/master/compositeArtifacts.xml

Perhaps we need to add a *build-helper-maven-plugin::package::attach-artifact* build step to each update site pom, as we do for Locus [2]? 

[2] https://github.com/jbosstools/jbosstools-locus/blob/master/deployment/pom.xml#L35

Or for the sake of reuse, perhaps it's better in the parent pom. We could add it to the existing deploy-to-jboss.org profile, or create a new  *deploy-to-nexus-unzip* profile?

[~mickael_istria] WDYT?



> 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)