You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stevo Slavić <ss...@gmail.com> on 2009/08/21 11:07:48 UTC
Seeing ghosts... & maven property expansions issue
Hello maven users,
A project with two modules M1 & M2 and their aggregating parent module A,
where A has itself a parent module P builds successfully if run without site
phase/goal (e.g. "mvn clean verify"), but mysteriously fails otherwise (e.g.
"mvn clean verify site"). M2 has dependency to M1, and maven prints good
build order, but somehow when it comes to build M2, M1 doesn't get resolved
although M1 should be present at least in build reactor. Maven used is
2.2.1, but same happened even if I revert to 2.1.0. Site plugin configured
in plugin management section of P's pom is 2.0.1, but build fails even with
2.0-beta-7. Neither of the pom's contains no assembly or artifact
(de)attaching mambo jumbo, in other words they are very simple ones. Any
advice is welcome.
One other topic bothering me is how does maven do property expansion,
especially in case if one has module hierarchy like described for previous
topic, and in module P one property X, and property Y referencing property X
value, and then in module M1 definition of the property with name X. Module
M1 doesn't have explicit definition of property Y, IMO it should be
inherited but I'm expecting in module M1 property Y to be expanded using
locally defined property X, thus overriding one defined in parent pom
hierarchy. This doesn't seem to happen.
Regards,
Stevo.
Re: Seeing ghosts... & maven property expansions issue
Posted by Stevo Slavić <ss...@gmail.com>.
If I specify maven-javadoc-plugin with something like [1] build doesn't fail
because of failure to resolve intermodule dependencies, instead it fails
because of this
<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6442982>long
standing bug in Java. Is there any workaround for this in maven? I've
tried adding annotations library as dependency of maven-javadoc-plugin in
build plugins section, but it didn't work.
Regards,
Stevo.
[1] maven-javadoc-plugin usage snippet
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.6</version>
<configuration>
<goals>
<goal>aggregate</goal>
</goals>
<links>
<link>http://java.sun.com/j2ee/1.4/docs/api/</link>
<link>http://java.sun.com/j2se/1.5.0/docs/api/
</link>
<link>http://java.sun.com/javase/6/docs/api/</link>
<link>http://logging.apache.org/log4j/docs/api/
</link>
<link>http://jakarta.apache.org/regexp/apidocs/
</link>
<link>
http://velocity.apache.org/engine/releases/velocity-1.5/apidocs/</link>
<link>
http://static.springframework.org/spring/docs/2.5.x/api/</link>
<link>http://www.castor.org/javadoc/</link>
</links>
<show>private</show>
</configuration>
<reportSets>
<reportSet>
<id>non-aggregate</id>
<reports>
<report>javadoc</report>
</reports>
</reportSet>
<reportSet>
<id>aggregate</id>
<reports>
<report>aggregate</report>
</reports>
</reportSet>
</reportSets>
</plugin>
On Mon, Aug 24, 2009 at 4:17 AM, Stevo Slavić <ss...@gmail.com> wrote:
> Second issue cause found: maven-javadoc-plugin. With it (tried with v2.6
> and v2.5) just listed in reporting plugins section with no additional
> configuration build fails to resolve intermodule dependencies. Without it,
> build is successful. Multiple maven plugins have reported issues of failure
> to resolve intermodule dependencies (
> http://jira.codehaus.org/browse/MDEP-195 ,
> http://jira.codehaus.org/browse/MNG-4233 , ... ) - maybe at least some of
> those people were using plain maven-javadoc-plugin.
>
> Regards,
> Stevo.
>
>
> On Fri, Aug 21, 2009 at 12:30 PM, Stevo Slavić <ss...@gmail.com> wrote:
>
>> For the second topic, I've found that maven-release-plugin was messing my
>> pom. scm section of a parent module references custom properties, and when
>> release plugin tags a release as well as when it prepares/commits for next
>> development iteration it saves scm section in expanded form which is not ok,
>> since modules inheriting parent module and thus it's scm section as well
>> were supposed to adjust parent defined scm just by specifying a child module
>> specific property value. I've found out that I'm not the only one
>> experiencing this issue <http://jira.codehaus.org/browse/MRELEASE-128>,
>> and it has quite some history, dating back from 2006.
>>
>> Regards,
>> Stevo.
>>
>>
>> On Fri, Aug 21, 2009 at 11:07 AM, Stevo Slavić <ss...@gmail.com> wrote:
>>
>>> Hello maven users,
>>>
>>> A project with two modules M1 & M2 and their aggregating parent module A,
>>> where A has itself a parent module P builds successfully if run without site
>>> phase/goal (e.g. "mvn clean verify"), but mysteriously fails otherwise (e.g.
>>> "mvn clean verify site"). M2 has dependency to M1, and maven prints good
>>> build order, but somehow when it comes to build M2, M1 doesn't get resolved
>>> although M1 should be present at least in build reactor. Maven used is
>>> 2.2.1, but same happened even if I revert to 2.1.0. Site plugin configured
>>> in plugin management section of P's pom is 2.0.1, but build fails even with
>>> 2.0-beta-7. Neither of the pom's contains no assembly or artifact
>>> (de)attaching mambo jumbo, in other words they are very simple ones. Any
>>> advice is welcome.
>>>
>>> One other topic bothering me is how does maven do property expansion,
>>> especially in case if one has module hierarchy like described for previous
>>> topic, and in module P one property X, and property Y referencing property X
>>> value, and then in module M1 definition of the property with name X. Module
>>> M1 doesn't have explicit definition of property Y, IMO it should be
>>> inherited but I'm expecting in module M1 property Y to be expanded using
>>> locally defined property X, thus overriding one defined in parent pom
>>> hierarchy. This doesn't seem to happen.
>>>
>>> Regards,
>>> Stevo.
>>>
>>
>>
>
Re: Seeing ghosts... & maven property expansions issue
Posted by Stevo Slavić <ss...@gmail.com>.
Second issue cause found: maven-javadoc-plugin. With it (tried with v2.6 and
v2.5) just listed in reporting plugins section with no additional
configuration build fails to resolve intermodule dependencies. Without it,
build is successful. Multiple maven plugins have reported issues of failure
to resolve intermodule dependencies (
http://jira.codehaus.org/browse/MDEP-195 ,
http://jira.codehaus.org/browse/MNG-4233 , ... ) - maybe at least some of
those people were using plain maven-javadoc-plugin.
Regards,
Stevo.
On Fri, Aug 21, 2009 at 12:30 PM, Stevo Slavić <ss...@gmail.com> wrote:
> For the second topic, I've found that maven-release-plugin was messing my
> pom. scm section of a parent module references custom properties, and when
> release plugin tags a release as well as when it prepares/commits for next
> development iteration it saves scm section in expanded form which is not ok,
> since modules inheriting parent module and thus it's scm section as well
> were supposed to adjust parent defined scm just by specifying a child module
> specific property value. I've found out that I'm not the only one
> experiencing this issue <http://jira.codehaus.org/browse/MRELEASE-128>,
> and it has quite some history, dating back from 2006.
>
> Regards,
> Stevo.
>
>
> On Fri, Aug 21, 2009 at 11:07 AM, Stevo Slavić <ss...@gmail.com> wrote:
>
>> Hello maven users,
>>
>> A project with two modules M1 & M2 and their aggregating parent module A,
>> where A has itself a parent module P builds successfully if run without site
>> phase/goal (e.g. "mvn clean verify"), but mysteriously fails otherwise (e.g.
>> "mvn clean verify site"). M2 has dependency to M1, and maven prints good
>> build order, but somehow when it comes to build M2, M1 doesn't get resolved
>> although M1 should be present at least in build reactor. Maven used is
>> 2.2.1, but same happened even if I revert to 2.1.0. Site plugin configured
>> in plugin management section of P's pom is 2.0.1, but build fails even with
>> 2.0-beta-7. Neither of the pom's contains no assembly or artifact
>> (de)attaching mambo jumbo, in other words they are very simple ones. Any
>> advice is welcome.
>>
>> One other topic bothering me is how does maven do property expansion,
>> especially in case if one has module hierarchy like described for previous
>> topic, and in module P one property X, and property Y referencing property X
>> value, and then in module M1 definition of the property with name X. Module
>> M1 doesn't have explicit definition of property Y, IMO it should be
>> inherited but I'm expecting in module M1 property Y to be expanded using
>> locally defined property X, thus overriding one defined in parent pom
>> hierarchy. This doesn't seem to happen.
>>
>> Regards,
>> Stevo.
>>
>
>
Re: Seeing ghosts... & maven property expansions issue
Posted by Stevo Slavić <ss...@gmail.com>.
For the second topic, I've found that maven-release-plugin was messing my
pom. scm section of a parent module references custom properties, and when
release plugin tags a release as well as when it prepares/commits for next
development iteration it saves scm section in expanded form which is not ok,
since modules inheriting parent module and thus it's scm section as well
were supposed to adjust parent defined scm just by specifying a child module
specific property value. I've found out that I'm not the only one
experiencing this issue <http://jira.codehaus.org/browse/MRELEASE-128>, and
it has quite some history, dating back from 2006.
Regards,
Stevo.
On Fri, Aug 21, 2009 at 11:07 AM, Stevo Slavić <ss...@gmail.com> wrote:
> Hello maven users,
>
> A project with two modules M1 & M2 and their aggregating parent module A,
> where A has itself a parent module P builds successfully if run without site
> phase/goal (e.g. "mvn clean verify"), but mysteriously fails otherwise (e.g.
> "mvn clean verify site"). M2 has dependency to M1, and maven prints good
> build order, but somehow when it comes to build M2, M1 doesn't get resolved
> although M1 should be present at least in build reactor. Maven used is
> 2.2.1, but same happened even if I revert to 2.1.0. Site plugin configured
> in plugin management section of P's pom is 2.0.1, but build fails even with
> 2.0-beta-7. Neither of the pom's contains no assembly or artifact
> (de)attaching mambo jumbo, in other words they are very simple ones. Any
> advice is welcome.
>
> One other topic bothering me is how does maven do property expansion,
> especially in case if one has module hierarchy like described for previous
> topic, and in module P one property X, and property Y referencing property X
> value, and then in module M1 definition of the property with name X. Module
> M1 doesn't have explicit definition of property Y, IMO it should be
> inherited but I'm expecting in module M1 property Y to be expanded using
> locally defined property X, thus overriding one defined in parent pom
> hierarchy. This doesn't seem to happen.
>
> Regards,
> Stevo.
>