fyi, I solved the cause of this - worst is I already knew it ;)
Root cause: google eclipse site are old style updatesites, not p2.
multiple builds fine because the mirroring works (it mirrors the updatesite with its
The generated site contains the adt bundles, but not the right metadata.
it is only when you actually try and use the adt plugins that you get an error
saying they cannot be found - but as far as .targt, repo content etc. goes
everything looks fine.
End result: at eclipsecon with Jan and Tobias from SAP we got a bug open and
soon fix to get tycho to report warnings for this target file situation so
others won't have to second-guess p2/tycho behavior.
On Thu, Mar 28, 2013 at 12:27:48PM -0400, Nick Boldt wrote:
On 03/28/2013 10:03 AM, Max Rydahl Andersen wrote:
>On Wed, Mar 27, 2013 at 11:21:01PM -0400, Nick Boldt wrote:
>>On 03/27/2013 09:08 PM, Max Andersen wrote:
>>>Were you able to run mvn install on my repo without any errors ?
>>Yes - which is why I said I could not reproduce your error.
Are you using Tycho 0.16 or 0.17?
>Thats fine but this is not something that should be run blindly since
>you might inadvertenly update
>dependency versions you did not expect.
That's why the generated changes go into a different file:
jbosstools-multiple.target, so you can compare them.
>>"Massive overkill" only takes a few seconds. But if you know for sure
>>that the list of URLs and IUs in your target file are current and up
>>to date, then yes, it's an unnecessary step. You would therefore need
>>only steps 2 and 3:
>$ cd jbosstools
>$ mvn install
>That should produce the same should it not ?
Yes, that is simpler. I've updated the doc .
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio