Hallo
thanks for the input!
so if i use relative paths for the parent pom the maven release plugin
will fail?
so you need to create a subversion repository for every parent-pom?
i tried to 'steal' some ideas from the apache subversion repository. but
that pom structure is beyond what i can understand right now.
so when i want to work with releases and maintainance releases from
branches i need to keept the parent pom / subdis layout and cannot use
relatvive paths?
well. i think i need to get back to the experiments part :)
thanks for the feedback. anything still welcome
regards
ossi
Olivier Dehon schrieb:
I later had to change that layout and take the diskspace hit of moving
to the 1st layout you describe, because the release plugin will not
work otherwise.
the modules are stored in a subversion repository:
http://repos/trunk/module-1
http://repos/trunk/module-2
http://repos/trunk/module-3
currently the parent pom is at
http://repos/trunk/pom.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
