]
Nick Boldt commented on JBIDE-17838:
------------------------------------
{quote}it would probably be easier to maintain the discovery project{quote}
Please explain how moving this ant task into its own module makes it easier to maintain.
I'm not adverse to the idea of simplifying maintenance, but this seems like arbitrary
refactoring rather than a simplification.
Also, there are *TWO* discovery sites that can be generated for each jbosstools/ and
jbdevstudio/ folder: one for Core and one for Early Access. Your PR moves only the Core
one and forgets about the Early Access discovery sites:
Also affected would be not just the publish.sh [0] script, but the promote.sh [1] script
and we'd have to update all the doc [2]:
[0]
Make discovery-site a Maven module
----------------------------------
Key: JBIDE-17838
URL:
https://issues.jboss.org/browse/JBIDE-17838
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build, discovery
Affects Versions: 4.2.0.Beta3
Reporter: Mickael Istria
Assignee: Nick Boldt
Priority: Minor
Fix For: 4.2.0.CR1
Currently, the discovery-site is generated under on of the discovery plugin. Since
it's a real artifact that we copy, deploy and that depends on several modules, it
would probably be easier to maintain the discovery project if we create a dedicated module
for the discovery site.