[jbosstools-issues] [JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure
[
https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19756:
------------------------------------
In the past it's been possible to build the aggregate as a CRx build (even using the
CR1 parent pom) and simply rename the zip: s/CRx/Final/g.
But with this change, we'll have to ensure we build the aggregate w/ the .Final parent
pom if it's for a 4.3.1.CRx we don't plan to release publically (and will thus
simply rename to Final 2 weeks later).
So... parent pom will have to move to Final during CR cycle sooner for 4.3.x.CR1 builds to
ensure that the sources contain the correct .Final label in them. Or, we just have one
more thing we have to respin (along with upstream components) between CRx and Final (as we
do for the upstream components). I guess losing the no-respin-required shortcut is a good
thing.
TL;DR, this is fine.
jbosstools-src.zip has incomplete/misleading version info in folder
names/structure
-----------------------------------------------------------------------------------
Key: JBIDE-19756
URL: https://issues.jboss.org/browse/JBIDE-19756
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.3.0.Beta1
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Fix For: 4.3.0.Beta1
Attachments: jbide19756.png
Downloading latest jbosstools-src.zip from
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
I see multiple files in root named:
<componentname>_<buildqualifier>_<sha1>
example:
jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad
A few issues with this:
a) it would have been nice unzipping would not create multiple root level folders. Maybe
have a jbosstools-source folder as root ?
b) the buildqualifier is there but the version string for the component is not. Either
put the full version string for that component (not overall jbosstools version) or just
leave it as <component>-<sha> and have the root folder state the full version
of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1
or 4.2.3.Beta1 (for example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)