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

[Snjezana Peco]

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

Snjeza

On 11.10.2012 10:19, Koen Aers wrote:
> I have successfully imported the Forge related projects.
>
> I have however one remark that is probably applicable to a lot of other sub projects. The bundle 'org.jboss.tools.forge.ui.bot.test' which was created by the QE team to do bot tests is dependent on a number of bundles (afaics two bundles: 'org.eclipse.swtbot.go' and 'org.jboss.tools.ui.bot.ext') that are not available in the vanilla JBoss Tools installation. Hence this plugin does not compile. Not importing this particular project (or of course deleting id or have a working set without it) solves the problem. Still I ask myself the question whether it wouldn't be better to have these bot tests in their own dedicated repo(s).
>
> Thoughts?
>
> Cheers,
> Koen
>
> Op 10-okt.-2012, om 18:52 heeft Max Rydahl Andersen het volgende geschreven:
>
>> Hi,
>>
>> Once I got positive or negative feedback on the various repositories on github.com/jbosstools here is the plan for git migration:
>>
>> Please read and understand this plan - its *important* - speak up now or stay forever silent!:
>>
>> Wed 17/10: *last* day for everyone to give feedback/objections/doing corrections in SVN for the migration.
>>
>> Fri 19/10:  Max disables any writes to svn on trunk and 4.0.0.Beta1 branch (3.3.x will still be usable)
>>                    Max starts migration of what is svn to git
>>
>> Sat 20/10: Max populates Github populated with git content
>>
>> Mon 22/10: Nick/Mistria - setup builds for trunk to use the git content
>>                      Max opens 4.0.0.Beta1 for writes.
>>                      Max svn deletes compoenents in trunk wit ref to github (similar to what was done with modeshape)
>>
>>
>> If everything goes as planned this means we will have all content migrated to and built from Git on the 23rd.
>>
>> Exceptions to that is:
>> 3.3.x in will still use svn and continue do so (at least for now)
>> 4.0.0.Beta1 will still use svn - thus if you do a change in git you need to do it in svn too/vice versa.
>>
>>
>> thank you,
>> /max
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev