Another option could be create a reactor pom.xml that can be used to 'mvn install' first scala-scripting and then parent.
2011/2/15 Reto Bachmann-Gmuer <[email protected]> > An idea might be to add it as a module to the parent, but not changing the > parent in scala-scripting. That way (I think) it would be compiled when > clerezza as a whole is compiled but also be compiled independently on the > clerezza-parent. > > Reto > > On Tue, Feb 15, 2011 at 1:12 PM, Hasan Hasan <[email protected]> wrote: > > > Hi all, > > > > I tend to leave it outside of parent. Although the folder hierarchy > > contains > > the name clerezza, it is something general. > > We just need to state clearly in the documentation that one has to > compile > > the scala-scripting first. > > Or maybe we can provide a simple shell script which compiles in correct > > sequence. > > > > Regards > > hasan > > > > On Tue, Feb 15, 2011 at 11:58 AM, Tommaso Teofili < > > [email protected] > > > wrote: > > > > > Hi Reto, > > > I also tested it and I managed to have a working launcher. > > > I think that in the future it could make sense to have scala-scripting > as > > a > > > separate package as it seems to me it is quite a general service (that > > > could > > > eventually be added to Felix Commons [1]). > > > It also depends if we want to release them as a whole or separately; so > > at > > > this stage I think that it'd be better to release them as a whole and > > > therefore put it inside parent to help users/devs build Clerezza easily > > as > > > that it's an important point for us to attract new people. > > > What do you think? > > > Cheers, > > > Tommaso > > > > > > > > > [1] : http://felix.apache.org/site/apache-felix-commons.html > > > > > > 2011/2/15 Reto Bachmann-Gmuer <[email protected]> > > > > > > > Hi Tommaso > > > > > > > > I could now successfully compile a working launcher after removing > the > > > .m2 > > > > directory. The thing to remember is to compile scala-scripting before > > > > parent. Should we move this into parent and make it a module there? > > > > > > > > Cheers, > > > > Reto > > > > > > > > On Mon, Feb 7, 2011 at 11:23 AM, Reto Bachmann-Gmuer < > > > > [email protected]> wrote: > > > > > > > > > It seems tools.offline was using the wrong parent, changed it to > use > > > the > > > > > default parent. > > > > > > > > > > Cheers, > > > > > Reto > > > > > > > > > > > > > > > On Mon, Jan 31, 2011 at 9:49 PM, Tommaso Teofili < > > > > > [email protected]> wrote: > > > > > > > > > >> Hi all, > > > > >> trying to do the first dryRuns to check release stuff I got the > > > > following: > > > > >> > > > > >> [ERROR] The build could not read 1 project -> [Help 1] > > > > >> [ERROR] > > > > >> [ERROR] The project > > > > >> org.apache.clerezza:tools.offline:0.1-incubating-SNAPSHOT > > > > >> > > > > >> > > > > > > > > > > (/Users/tommaso/Documents/workspaces/clerezza/trunk/parent/tools.offline/pom.xml) > > > > >> has 1 error > > > > >> [ERROR] Non-resolvable parent POM: Could not find artifact > > > > >> org.apache.clerezza:rdf.web:pom:0.8-incubating-SNAPSHOT and > > > > >> 'parent.relativePath' points at wrong local POM @ line 3, column > 10 > > -> > > > > >> [Help > > > > >> 2] > > > > >> > > > > >> I ran the command 'mvn clean install -Dmaven.repo.local=/tmp/cl1' > to > > > use > > > > >> an > > > > >> empty repo and be sure everyone can build Clerezza. > > > > >> Any ideas? > > > > >> Regards, > > > > >> Tommaso > > > > >> > > > > > > > > > > > > > > > > > > > >
