[jbosstools-issues] [JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983551#comment-12983551 ] 

Mickael Istria commented on JBIDE-17838:
----------------------------------------

The idea is that it's not trivial to find the output (discovery site) after a build. It is currently a kind of sub-artifact under the target/ folders of the plugins.
With this change, we have the plugins, that produce plugins, in their module; and a module dedicated to the site, which is an upstream artifact and that can consume multiple plugins.

You say there are 2 sites (one attached to Core plugin, and one attached to Early Access plugin), but in the end, do we really need 2 sites? Which one(s) do we consume and publish? The current situation seems similar to generating one p2 repository for every bundle. It doesn't seem to be what we want/need.
I will remove from the earlyaccess bundles invocation of the pom in favor of using the antrun from discovery-site modules.

That's why I see this as a simplification that would ease maintenance: easier to find what to run/tweak, and less things to run/tweak.

> 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.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)