Why do I need to import the whole &tools module?

[ovidiu.feodorov]

It seems that all I need in order to use jbossbuild with my project is tools/etc/jbossbuild/tasks.xml and toold/lib/jbossbuild.jar (and tools/etc/buildmagic/aliases.ent, it is required by jbossbuild but they it is useless to me, so it's just sitting there to make jbossbuild happy).

I copied all these files over and imported in SVN and everything works fine.

However, http://wiki.jboss.org/wiki/Wiki.jsp?page=ExampleBuildThirdparty advises to import the whole "tools" module, which contains a lot of useless buildmagic junk and then some.

Is there any reason I should import the whole "tools" module instead of just copying jbossbuild.jar?

How active do you predict jbossbuild will be in the future? Do you foresee the need of a lot of jbossbuild.jar updates?

[starksm64]

jbossbuild will be deprecated in favor of maven2.

[ovidiu.feodorov]

When should we expect a migration?

[ryan.campbell]

How about now?

[ovidiu.feodorov]

Ummmm, ok, I've just went through one from buildmagic to jbossbuild about a day ago ... But what the heck.

[ryan.campbell]

Well, it is up to you. I was being a bit whimsical, but it might make sense if you are at the beginning of a dev cycle.

It will probably require a restructuring of your source code, but this should not be a problem now that you are in SVN.

Scott/Ruel, what do you think about making messaging our next conversion?

[ruel.loehr]

I'm comfortable with doing that.

[starksm64]

Has the common project migration to maven2 been done? We should do that first if not.

[ryan.campbell]

Agreed, once common is done. This should be done sometime next week.