[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ] 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. -- This message was sent by Atlassian JIRA (v6.2.6#6264)