[jbosstools-issues] [JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site

[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21233: --------------------------------------------- a) I ask if this this will mean the sites we *build* against (which are *not* the /development, /stable etc. top level sites) will now have forcefully included the Target platform. If yes, that is bad since that means consuming builds can no longer control which TP they build against. b) I simply do not understand why we are back at again discussing categorized vs non-categorized. We solved that issue 2-3 years ago by stop using associate sites and have aggregates that link via p2 metadata (instead of associated sites) to sites to contact for getting TP content. You even wrote about it back then in 2011 (https://dzone.com/articles/simplifying-p2-process-part-3) - Is that something you are completely forgetting/ignoring now ? It is called "required sites" - your own article about it reminded me. c) You are conflating failed attempts on simplifying things to mean noone wants things to be simplified. I'll not discuss this more in here. So back, to my original question - is this going to mean our sites used for building will now forcefully have the TP included or not ? And why don't we use p2 required sites as in past for our updatesites ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)