[
https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19756:
------------------------------------
{quote}Why do you want to have jbds use local sources and not same as jbosstools ?
{quote}
Because no github auth is therefore required and the JBDS sources are ALREADY on disk
(unlike for the JBT build, where they're all upstream in the 17 projects' builds).
Why fetch them from github when they're already available locally?
#performanceImprovement #simplerApproach
{quote} And why is it a problem to have you as user access jbdevstudio ? you can't run
these builds if you dont have the access.{quote}
The big reason we started providing a zip of JBDS sources was so that customers could
build it. If we make it buildable only for those with VPN (eg., to pull in EAP or upstream
files like devstudio-earlyacccess.properties) or github auth access (to fetch a copy of
the sources already on disk from the jbdevstudio-product repo, after authenticating), we
break that "API contract" we put in place for JBDS 7. Ref: JBDS-2456
Today you CAN build JBDS without having access to jbdevstudio-product. You just need the
installer-src.zip and you can build everything locally. Why would we break change that to
make it harder?
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)