[Jboss-dev-forums] [Design of JBoss Build System] - Re: JBoss Third Party Build

[<rl...@jb...>]

The two issues raised, to reiterate some posts that didn't make it into the forum are:

1)  Eclipse classpath generation
2)  The download of dependencies to path structure with a version number

Eclipse classpath generation is a difficult concept for this "hybrid" build.  I use the word hybrid in terms that it is mostly buildmagic with a bit of jbossbuild.  The jbossbuild is the portion which is responsible for downloading the dependencies. 

Keep in mind that the jbossbuild at this point essentially only has a list of dependencies which it knows about, however it does not have any concept of modules or which dependencies are required by each module.   In order to properly generate an eclipse classpath file for each module we would need the information defined in the buildmagic system (e.g.   which modules, which depedencies).  

anonymous wrote : I would guess its not a big deal to simply drop the local repository version info. The generated get ouput location and local path checks would simply drop the version portion. The libraries.ent generation would also need to be updated.

Dropping the local version information shouldn't be tough.  I will begin work on it today.   If we are to drop the local version info from the paths, this will give us a very similiar thirdparty folder as to what was being checked out from cvs.   In this case, even if no eclipse classpath is generated, aren't we basically at the same point we are with the standard buildmagic build as far as classpath information is concerned?  

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886809#3886809

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886809