6:52 p.m.
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
10:19 a.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:30 a.m.
I have successfully imported the Forge related projects.
have you also successfully built them with tycho/maven ?
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.
You must be missing the base repo - that is where all the common tests infrastructure is.
SWTBot is something that is in our targetplatform and can/should be installed when doing
swtbot tests. You do have tests for forge plugin - right ? :)
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).
You mean like this: https://github.com/jbosstools/temp-jbosstools-integration-tests
They are being moved out - but not because of the reasons above since those dependencies
are ok to use to do tests.
They are being moved out because it turns out the bot tests are 100% driven/developed by
QE and they change these *after* our code release thus their release/update cycle is
opposite to what the components do/need.
Once we've migrated to the gitrepos I or QE will submit pullrequests to the various
projects to delete the at that time redundant plugins.
/max
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(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
10:57 a.m.
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_set...
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(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
11:17 a.m.
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_set...
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 <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
11:32 a.m.
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.
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 ;-)
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_set...
>
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
11:35 a.m.
On 11 Oct 2012, at 11:32, Koen Aers <koen.aers(a)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_set...
>>
>>
>>
> 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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4:51 p.m.
New subject: Fwd: [gitmigration] IMPORTANT: Plan for Git migration - SVN will be disabled next friday!
Hey,
Just a reminder this plan is still on.
SVN is king until Friday.
On Friday SVN will be marked readonly while the gitmigration cocurs.
Further details (on when svn will be writable again etc. is in below outline.)
/max
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4215
days inactive
4222
days old
jbosstools-dev@lists.jboss.org
7 comments
4 participants
participants (4)
-
Koen Aers -
Max Rydahl Andersen -
Mickael Istria -
Snjezana Peco