?
Cem
--
View this message in context:
http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-tp4611798p4616145.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To
somewhere else?
>
> Thanks
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-tp4611798p4615533.html
> Sent from the Maven - User
-parent-directory-at-multi-module-maven-project-tp4611798p4615533.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail
; --
> View this message in context:
> http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-tp4611798p4614958.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
? What are your
opinions?
--
View this message in context:
http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-tp4611798p4614958.html
Sent from the Maven - Users mailing list archive at
I normally define a property called something like
'multiproject.basedir' in every POM - or at least in every POM that
needs to reference a path in the parent project dir.
Some examples:
- in 'parent/pom.xml' it's:
${basedir}
- in 'parent/sub1/pom.xml' it's:
${basedir}/..
- in 'par
On 19 July 2011 09:16, Stephen Connolly wrote:
> On 19 July 2011 16:44, Hilco Wijbenga wrote:
>
>> On 19 July 2011 03:01, Cem Koc wrote:
>> > I have 3 level multi module maven project. I want to utilize a common
>> plugin
>> > configuration at parent pom and the rest of the 2nd and 3rd level mo
On 19 July 2011 16:44, Hilco Wijbenga wrote:
> On 19 July 2011 03:01, Cem Koc wrote:
> > I have 3 level multi module maven project. I want to utilize a common
> plugin
> > configuration at parent pom and the rest of the 2nd and 3rd level modules
> > will utilize this configuration. The plugin c
On 19 July 2011 03:01, Cem Koc wrote:
> I have 3 level multi module maven project. I want to utilize a common plugin
> configuration at parent pom and the rest of the 2nd and 3rd level modules
> will utilize this configuration. The plugin configuration has a
> configuration file for 3rd level mod
configuration could not be used by 2rd level modules. They need
../conf/myplugin
What is the best way to use a common path for all modules in a project even
at root parent pom?
--
View this message in context:
http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module
10 matches
Mail list logo