[
https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3364:
----------------------------------
First fresh bits:
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma...
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8....
(BTW, I realized this used to work in JBDS 6, too, but broke when we refactored the old
"grab some zips" into "grab sources from github SHAs", but no one
noticed the downstream impact until now. If anyone can suggest a good test to avoid
missing this rather important detail in future, that we can implement as a maven enforcer
rule, I'm happy to codify that.)
Include JBT sources in JBDS source zip
--------------------------------------
Key: JBDS-3364
URL:
https://issues.jboss.org/browse/JBDS-3364
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: build
Affects Versions: 8.0.2.GA
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 8.1.0.Beta1, 9.0.0.Alpha2
1. Include the contents of the JBT source zip inside the JBDS one so all the sources for
everything in JBDS (except third party stuff) can be seen in a single artifact.
2. Ensure that the release guide has a step for pushing this zip to the FTP site, even
for service releases.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)