[
https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-19756:
---------------------------------------------
Why is devstudio not done exactly the same way as with jbosstools ?
reponame-sha1 ?
so
jbdevstudio-product-234l23jk2423424j2l ?
And where are the build-info.json files to provide the info you were initially partially
encoding into the file names ?
And why does devstudio zip have a jbosstools/sources folder instead of jbosstools as done
for jbosstools ?
Seems like this is done by different logic than what used for jbosstools ?
And if folder is needed, then I would put that in jbdevstudio to mimick jbosstools
approach.
So you would have:
jbdevstudio
jbosstools
as roots - mimicking the github organization it is coming from.
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, jbide19756_jbds-sources-zip.png,
jbide19756_new_subfolders_and_zipfile_name.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)