you could package the build.properties that your dealing with into an artifact and pull it down into the local projects that need it with the remote-resources maven plugin?
maven convention is that each subproject is an entity onto itself and that anything it needs from external sources is pulled from a repository... jesse On 8/1/07, DCVer <[EMAIL PROTECTED]> wrote: > > > Still noone? %-| > > > DCVer wrote: > > > > Hi all > > > > I am thinking about such a problem: > > > > I add a multi-level project to Continuum by choosing path to main (root) > > project pom.xml file on the svn. Continuum automatically adds all > > subprojects of the main project. > > > > I would like to build any of the subproject individually, but Continuum > > destroys the hierarchy of the projects and the parent project is no > longer > > parent for any of the subproject. This cause such an annoying problem: > > > > Few of the subprojects point on the file (build.properties), which is > > global to the whole project and is stored in one of the parent project's > > directories. But in Continuum all projects are in separate directories > > named with numbers. This heads to the error: > > > > Error loading property file > > > '/opt/xxx/continuum-working-directory/74/../src/filters/build.properties' > > > > I changed the arguments of the root project (deleted --non-recursive) > and > > then it's quite fine, but I would like to build single subproject > without > > compiling the whole, global project. Imagine that the global project is > > compiling let's say 10 minutes and you only want to check if you small > > package is done wright (which compiles in few seconds) > > > > Thanks in advance for any help. > > > > -- > View this message in context: > http://www.nabble.com/Multi-level-project-directories-hierarchy-tf4111727.html#a11944353 > Sent from the Continuum - Users mailing list archive at Nabble.com. > > -- jesse mcconnell [EMAIL PROTECTED]
