[jbosstools-dev] [gitmigration] IMPORTANT: Plan for Git migration - SVN will be disabled next friday!

[Max Rydahl Andersen]

On 11 Oct 2012, at 11:32, Koen Aers <koen.aers at jboss.com> wrote:

> I know importing these dependencies or setting up a specific target platform solves the problem but I was trying to avoid that because for normal development on the Forge plugins it's not really needed.

does that imply forge plugin does not need tests and is perfect? :)

> I was actually specifically talking about the bot tests that are being developed by the QE team and that I don't know a lot about, so Max's answer has addressed my concerns :-)

:)

> As for the Tycho/Maven build, this runs like a breeze ;-)

Great - thanks for verifying.

/max

> 
> Cheers,
> Koen
> 
> Op 11-okt.-2012, om 11:17 heeft Mickael Istria het volgende geschreven:
> 
>> On 10/11/2012 10:57 AM, Snjezana Peco wrote:
>>> You can try to use
>>> mvn clean install -P unified.target -Pjbosstools-nightly-staging-composite
>>> 
>>> The settings.xml must be set as described in 
>>> 
>>> https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#Maven_settings
>>> 
>>> 
>>> 
>> I think Koen is talking about build from his workspace.
>> @Koen: you'll need to provide Eclipse those dependencies, either import projects you depend on in your workspace, or set up a target-platform specific to your use-case (derive unified.target and add reference to the sites/bundles you depend on)
>> -- 
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat
>> My blog - My Tweets
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>