I would suspect some projects may require some of these for test
plugins (just a guess). For the integration platform, I've been considering creating
an additional TP that would be used for testing (i.e. one to build the distributables and
one to build the tests). The test TP would simply extend the core TP with those
additional plugins required for testing.
What kind of testing ? if just for viewing source for debugging then P2/Tycho already
support that "natively" for those bundles that follows the standard naming
convention with a .source postfix.
Thus nothing extra is needed for that case unless there is something else than source
needed (I don't know of any?) or for those (hopefully few ones) that does not follow
this now age old convention.
Do you have an usecase outside getting the source for debugging ?
/max
Just a thought.
----- Original Message -----
> I assume we can just do a basic test build with this before doing a
> full change in master ?! Or at least do a manual scan in the feature
> / manifest.mf files in a full install to see if there are any refs ?
>
> There can be projects that depend on sdk bundles but if that is the
> case that is a major bug.
>
> But we can't just remove this since what is important is if any users
> actually installed this from the released site and then we go ahead
> and remove the .sdk bundles and the updates will fail (assuming
> these sdk references might have been included in any build ?)
>
> /max
>
> On 07 Jan 2013, at 11:50, Mickael Istria <mistria(a)redhat.com> wrote:
>
>> Hi all,
>>
>> We noticed that the target-platforms contains explicit dependencies
>> to some source bundles and SDK features. It's a bad thing, since
>> the target-platform should contain the minimal set of dependencies
>> (and use the includeSource flag to get source in IDE magically).
>>
https://issues.jboss.org/browse/JBIDE-13329
>>
>> I'd like to remove all those ".source" and ".sdk" IUs
from
>> target-platforms. Before I do so (in a few days), please raise
>> your hand in case your project does require one of those
>> depedencies, or you'll see your build broken.
>>
>> Thanks in advance.
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat
>> My blog - My Tweets
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>