[
https://issues.jboss.org/browse/JBIDE-17117?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-17117:
------------------------------------
I wish
sf.net was secondary, but we have a lot of zip downloads. I've tried to
convince Max to drop the need for the Hibernate Tools zip, but it continues to be a
popular download so we continue to provide it.
THAT SAID... now that we have Akamai caching, we could look at caching files in /static
instead of pushing files to
SF.net at all.
Might be worth doing some perf tests as both places provide geo-located mirroring to
improve dl speeds. If we didn't need to bother pushing bits to
sf.net, then ALL our
bits would live on
download.jboss.org (or
access.redhat.com, for JBDS) and that would
certainly make the publishing process simpler.
----
Re: renaming for
sf.net: That's so that the files are consistently named with the same
qualifiers
Re: doing something at the same time as the marketplace entry: yes, I usually kick off the
various scp/sftp/rsync processes in the background, then do the more manual steps in the
foreground. The older versions of the release guides even stated "while the above is
running..." to further drive home the difference between long-running background
tasks and hands-on foreground tasks. Wherever possible I've tried to document that in
the guide but there are other things we can do/simplify to allow even more parallel
steps.
Re: JBossTools-version.suffix/ folders vs. jbosstools-version/suffix/ folders, yes, we
could switch to that model (note the change to lowercase too, to make [~maxandersen] happy
re: JBIDE-16871).
---
Re: webtools site:
As I keep saying in other places, webtools CANNOT BE REFERENCED as a composite. It
doesn't work because the server adapter wizard uses Eclipse Update, not p2. So...
composite sites don't work. Or they didn't the last time I tried to change over to
a composite. Maybe that's fixed now in Luna. Feel free to open a JIRA on that, and if
it's NOT fixed in upstream, open a bugzilla to get it fixed there (most likely
won't be seen until Eclipse 4.5 ( Mars ) development starts in summer 2014.
Past JIRAs:
https://issues.jboss.org/browse/JBIDE-8460 - WTP 3.2 Helios
https://issues.jboss.org/browse/JBIDE-9851 - WTP 3.3 Indigo
https://issues.jboss.org/browse/JBIDE-10469 - WTP 3.4 Juno -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=373319 - Proof a composite didn't work:
https://issues.jboss.org/browse/JBIDE-10469?focusedCommentId=12672513&...
?? - WTP 3.5 Kepler *can't find the JIRA*
https://issues.jboss.org/browse/JBIDE-16311 - WTP 3.6 Luna
Simplify publish process
------------------------
Key: JBIDE-17117
URL:
https://issues.jboss.org/browse/JBIDE-17117
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Reporter: Mickael Istria
We could work on improving the publishing process. Some ideas:
* Why do we rename the files we pull on
sf.net. Also, renaming files could happen on
sf.net.
* Files from
sf.net could be fetch after (for example in parallel with creating
marketplace entry)
* webtools should be published in a similar way as other parts (moved to
tools/static/releases and then referenced in the composite file)
* Replace the .core, .webtools, .hibernatetools, .coretests suffix by actual URL
segments, so one would only have to move a single folder instead of 4 ones.
* Identify things that can be done in parallel.
* ...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)