[jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
[
https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-21012 at 10/26/15 2:02 PM:
--------------------------------------------------------------
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
Run locally:
{code}
mvn clean install -DBUILD_NUMBER=1234 && ll site/target/*.zip
site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_*
[INFO] freemarker.site .................................... SUCCESS [ 4.587 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
{code}
Results:
*
site/target/repository/features/org.jboss.ide.eclipse.freemarker.feature_1.5.100.Alpha1-v20151026-1703-B1234.jar
* site/target/freemarker.site-1.5.100.Alpha1-v20151026-1703-B1234.zip
Next I need to see if this works in Jenkins/Nexus...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-freemarker... >=308
was (Author: nickboldt):
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... >=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)