Re: Checkstyle report fails on release, not site

2007-07-11 Thread ossi petz

Hallo

well there is no fool-proof hint i saw.

the difference is the build-tools.jar include: the non working example 
does it using an extension (which creates that cycle)


the working example uses a dependency for the plugin to the build-tools.jar

only a small difference but an important one :)

the first link is easyier to find (maven page, plugins by category, 
checkstyle). the second was from google.





Dennis Lundberg schrieb:

ossi petz wrote:


did i post that link? :)
those instructions will create a cyclic reference for the mentioned 
'build-tools' project. better do it this way:


http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html


This is an old page that shouldn't be used any more. Is the info on this 
page not included on the multi-module example page?




works :)

ossi petz schrieb:

well after reading along in the docs:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Checkstyle report fails on release, not site

2007-07-10 Thread ossi petz

hallo

well parent poms and relative paths. a long story.

have you issued the site command from the sub-modules?
but the release is done from the parent pom?

it seems the checkstyle plugin is not aware of that difference and is 
looking at the wrong location.


i do both site and release from the the parent pom and it works this 
way. but single module builds fail in my case.





Jon Strayer schrieb:

I have a parent pom that all my projects inherent.   It configures the
checkstyle plugin like this:

   configuration
   configLocation
   ../theteam/checkstyle.xml
   /configLocation
   headerLocation
   ../theteam/header.txt
   /headerLocation
   /configuration

This works fine when I use mvn site, but when I use mvn release:prepare
I get this error


 Embedded error: Error rendering Maven report: Unable to find configuration
file location.
 Unable to find location '../theteam/checkstyle.xml' as URL, File or
Resource.


So, why can it find it for the first command but not the second?





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Checkstyle report fails on release, not site

2007-07-10 Thread Jon Strayer

On 7/10/07, ossi petz [EMAIL PROTECTED] wrote:


hallo

well parent poms and relative paths. a long story.

have you issued the site command from the sub-modules?
but the release is done from the parent pom?



Yes, the site is from the sub-modules, but the release is also from the sub
modules.


it seems the checkstyle plugin is not aware of that difference and is

looking at the wrong location.

i do both site and release from the the parent pom and it works this
way. but single module builds fail in my case.



Well, at least we are seeing the same thing.  :-)


Jon Strayer schrieb:

 I have a parent pom that all my projects inherent.   It configures the
 checkstyle plugin like this:

configuration
configLocation
../theteam/checkstyle.xml
/configLocation
headerLocation
../theteam/header.txt
/headerLocation
/configuration

 This works fine when I use mvn site, but when I use mvn
release:prepare
 I get this error


  Embedded error: Error rendering Maven report: Unable to find
configuration
 file location.
  Unable to find location '../theteam/checkstyle.xml' as URL, File or
 Resource.


 So, why can it find it for the first command but not the second?




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Esse Quam Videre
To Be, rather than to Seem


Re: Checkstyle report fails on release, not site

2007-07-10 Thread ossi petz

well after reading along in the docs:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html

kinda solves this issue :)

(havent tested it yet but it looks good)



Jon Strayer schrieb:

On 7/10/07, ossi petz [EMAIL PROTECTED] wrote:


hallo

well parent poms and relative paths. a long story.

have you issued the site command from the sub-modules?
but the release is done from the parent pom?



Yes, the site is from the sub-modules, but the release is also from the sub
modules.


it seems the checkstyle plugin is not aware of that difference and is

looking at the wrong location.

i do both site and release from the the parent pom and it works this
way. but single module builds fail in my case.



Well, at least we are seeing the same thing.  :-)


Jon Strayer schrieb:

 I have a parent pom that all my projects inherent.   It configures the
 checkstyle plugin like this:

configuration
configLocation
../theteam/checkstyle.xml
/configLocation
headerLocation
../theteam/header.txt
/headerLocation
/configuration

 This works fine when I use mvn site, but when I use mvn
release:prepare
 I get this error


  Embedded error: Error rendering Maven report: Unable to find
configuration
 file location.
  Unable to find location '../theteam/checkstyle.xml' as URL, File or
 Resource.


 So, why can it find it for the first command but not the second?




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Checkstyle report fails on release, not site

2007-07-10 Thread Jon Strayer

That should work for you, but it doesn't work for me.  My other projects
aren't modules of a parent project.  The just inherit the pom to standardize
things.

On 7/10/07, ossi petz [EMAIL PROTECTED] wrote:


well after reading along in the docs:

http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html

kinda solves this issue :)

(havent tested it yet but it looks good)



Jon Strayer schrieb:
 On 7/10/07, ossi petz [EMAIL PROTECTED] wrote:

 hallo

 well parent poms and relative paths. a long story.

 have you issued the site command from the sub-modules?
 but the release is done from the parent pom?


 Yes, the site is from the sub-modules, but the release is also from the
sub
 modules.


 it seems the checkstyle plugin is not aware of that difference and is
 looking at the wrong location.

 i do both site and release from the the parent pom and it works this
 way. but single module builds fail in my case.


 Well, at least we are seeing the same thing.  :-)


 Jon Strayer schrieb:
  I have a parent pom that all my projects inherent.   It configures
the
  checkstyle plugin like this:
 
 configuration
 configLocation
 ../theteam/checkstyle.xml
 /configLocation
 headerLocation
 ../theteam/header.txt
 /headerLocation
 /configuration
 
  This works fine when I use mvn site, but when I use mvn
 release:prepare
  I get this error
 
 
   Embedded error: Error rendering Maven report: Unable to find
 configuration
  file location.
   Unable to find location '../theteam/checkstyle.xml' as URL, File or
  Resource.
 
 
  So, why can it find it for the first command but not the second?
 
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Esse Quam Videre
To Be, rather than to Seem


Re: Checkstyle report fails on release, not site

2007-07-10 Thread ossi petz


did i post that link? :)
those instructions will create a cyclic reference for the mentioned 
'build-tools' project. better do it this way:


http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html

works :)

ossi petz schrieb:

well after reading along in the docs:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Checkstyle report fails on release, not site

2007-07-10 Thread ossi petz

hallo

well that should not matter. the checkstyle plugin dependency is 
resolved by its groupId/artifactId. as long as that jar is 'somewhere' 
it should be possible to include it as normal dependency without 
creating modules.


so the plugin section for the checkstyle plugin gets a dependencies 
section. that should do the job?




Jon Strayer schrieb:

That should work for you, but it doesn't work for me.  My other projects
aren't modules of a parent project.  The just inherit the pom to 
standardize

things.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Checkstyle report fails on release, not site

2007-07-10 Thread Dennis Lundberg

ossi petz wrote:


did i post that link? :)
those instructions will create a cyclic reference for the mentioned 
'build-tools' project. better do it this way:


http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html


This is an old page that shouldn't be used any more. Is the info on this 
page not included on the multi-module example page?




works :)

ossi petz schrieb:

well after reading along in the docs:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]