maven-scala-plugin scala and java mixture problem with scaladoc

I'd love to help! 

Unfortunately, I'm not planning on supporting anything major (in the maven-scala-plugin) with scaladoc until there is a scaladoc maintainer.   I'm unsure of whether scaladoc was ever updated to handle mixed java/scala projects, but I'm skeptical.

In the meantime, If you can run scaladoc locally (not inside maven), are you seeing the same error?

There's a known issue with scaladoc on windows (and many bugs in the scala trac database).  I would make sure you're not running into one of those.

Also, you may want to try vscaladoc as I believe it's still being maintained by David Bernard.


-Josh



On Thu, Feb 26, 2009 at 10:06 AM, rossputin <rossajmcd@yahoo.co.uk> wrote:

Hi.

My setup is something like:

src/main/java
   com/company/mypackage
       MyClass.java
   com/company/mypackage/utility
       SomeUtility.java

src/main/scala
   com/company/mypackage
       MyClass.scala

While my scala classes can make use of my java classes at compile time
because of my 'executions' setup in the pom under the maven-scala-plugin
within my build element, reporting is a problem for me.

If my Scala class tries to import anything from
'com.company.mypackage.utility' which lives in the java source tree calling
'mvn ... scala:doc' yields:

...
error: value utility is not a member of package com.company.mypackage
...

Can anyone help with configuring scala:doc to cope with this ?

Thanks in advance for your help.

Regards,

Ross.
--
View this message in context: http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22226047.html
Sent from the Scala - Tools mailing list archive at Nabble.com.

Hi Josh.

I dropped scaladoc and plugged in vscaladoc like you suggested, using:

1.0

in my reporting plugin.

It seems I get the same result. Perhaps I missed something out ?

Thanks for your help.

Regards,

Ross.

Josh Suereth wrote:
>
> I'd love to help!
>
> Unfortunately, I'm not planning on supporting anything major (in the
> maven-scala-plugin) with scaladoc until there is a scaladoc maintainer.
> I'm unsure of whether scaladoc was ever updated to handle mixed java/scala
> projects, but I'm skeptical.
>
> In the meantime, If you can run scaladoc locally (not inside maven), are
> you
> seeing the same error?
>
> There's a known issue with scaladoc on windows (and many bugs in the scala
> trac database). I would make sure you're not running into one of those.
>
> Also, you may want to try vscaladoc as I believe it's still being
> maintained
> by David Bernard.
>
>
> -Josh
>
>
>
> On Thu, Feb 26, 2009 at 10:06 AM, rossputin wrote:
>
>>
>> Hi.
>>
>> My setup is something like:
>>
>> src/main/java
>> com/company/mypackage
>> MyClass.java
>> com/company/mypackage/utility
>> SomeUtility.java
>>
>> src/main/scala
>> com/company/mypackage
>> MyClass.scala
>>
>> While my scala classes can make use of my java classes at compile time
>> because of my 'executions' setup in the pom under the maven-scala-plugin
>> within my build element, reporting is a problem for me.
>>
>> If my Scala class tries to import anything from
>> 'com.company.mypackage.utility' which lives in the java source tree
>> calling
>> 'mvn ... scala:doc' yields:
>>
>> ...
>> error: value utility is not a member of package com.company.mypackage
>> ...
>>
>> Can anyone help with configuring scala:doc to cope with this ?
>>
>> Thanks in advance for your help.
>>
>> Regards,
>>
>> Ross.
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

Hi,

scaladoc and vscaladoc delegate a big part of the job (creating the Data Model) to scalac (from where your issue seems to come).
could you provide a sample test project with your "execution" setup.
Or at least your pom.xml and the full log.

/davidB

On Fri, Feb 27, 2009 at 10:39, rossputin <rossajmcd@yahoo.co.uk> wrote:

Hi Josh.

I dropped scaladoc and plugged in vscaladoc like you suggested, using:

<configuration>
 <vscalaVersion>1.0</vscalaVersion>
</configuration>

in my reporting plugin.

It seems I get the same result.  Perhaps I missed something out ?

Thanks for your help.

Regards,

Ross.




Josh Suereth wrote:
>
> I'd love to help!
>
> Unfortunately, I'm not planning on supporting anything major (in the
> maven-scala-plugin) with scaladoc until there is a scaladoc maintainer.
> I'm unsure of whether scaladoc was ever updated to handle mixed java/scala
> projects, but I'm skeptical.
>
> In the meantime, If you can run scaladoc locally (not inside maven), are
> you
> seeing the same error?
>
> There's a known issue with scaladoc on windows (and many bugs in the scala
> trac database).  I would make sure you're not running into one of those.
>
> Also, you may want to try vscaladoc as I believe it's still being
> maintained
> by David Bernard.
>
>
> -Josh
>
>
>
> On Thu, Feb 26, 2009 at 10:06 AM, rossputin <rossajmcd@yahoo.co.uk> wrote:
>
>>
>> Hi.
>>
>> My setup is something like:
>>
>> src/main/java
>>    com/company/mypackage
>>        MyClass.java
>>    com/company/mypackage/utility
>>        SomeUtility.java
>>
>> src/main/scala
>>    com/company/mypackage
>>        MyClass.scala
>>
>> While my scala classes can make use of my java classes at compile time
>> because of my 'executions' setup in the pom under the maven-scala-plugin
>> within my build element, reporting is a problem for me.
>>
>> If my Scala class tries to import anything from
>> 'com.company.mypackage.utility' which lives in the java source tree
>> calling
>> 'mvn ... scala:doc' yields:
>>
>> ...
>> error: value utility is not a member of package com.company.mypackage
>> ...
>>
>> Can anyone help with configuring scala:doc to cope with this ?
>>
>> Thanks in advance for your help.
>>
>> Regards,
>>
>> Ross.
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22226047.html
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

--
View this message in context: http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22242407.html
Sent from the Scala - Tools mailing list archive at Nabble.com.

Hi David.

Here is a small sample project which compiles, but fails on 'scala:doc'.

Thanks.

Ross.
http://www.nabble.com/file/p22243449/scala_java_maven.tgz
scala_java_maven.tgz

David Bernard-3 wrote:
>
> Hi,
>
> scaladoc and vscaladoc delegate a big part of the job (creating the Data
> Model) to scalac (from where your issue seems to come).
> could you provide a sample test project with your "execution" setup.
> Or at least your pom.xml and the full log.
>
> /davidB
>
> On Fri, Feb 27, 2009 at 10:39, rossputin wrote:
>
>>
>> Hi Josh.
>>
>> I dropped scaladoc and plugged in vscaladoc like you suggested, using:
>>
>>
>> 1.0
>>
>>
>> in my reporting plugin.
>>
>> It seems I get the same result. Perhaps I missed something out ?
>>
>> Thanks for your help.
>>
>> Regards,
>>
>> Ross.
>>
>>
>>
>>
>> Josh Suereth wrote:
>> >
>> > I'd love to help!
>> >
>> > Unfortunately, I'm not planning on supporting anything major (in the
>> > maven-scala-plugin) with scaladoc until there is a scaladoc maintainer.
>> > I'm unsure of whether scaladoc was ever updated to handle mixed
>> java/scala
>> > projects, but I'm skeptical.
>> >
>> > In the meantime, If you can run scaladoc locally (not inside maven),
>> are
>> > you
>> > seeing the same error?
>> >
>> > There's a known issue with scaladoc on windows (and many bugs in the
>> scala
>> > trac database). I would make sure you're not running into one of
>> those.
>> >
>> > Also, you may want to try vscaladoc as I believe it's still being
>> > maintained
>> > by David Bernard.
>> >
>> >
>> > -Josh
>> >
>> >
>> >
>> > On Thu, Feb 26, 2009 at 10:06 AM, rossputin
>> wrote:
>> >
>> >>
>> >> Hi.
>> >>
>> >> My setup is something like:
>> >>
>> >> src/main/java
>> >> com/company/mypackage
>> >> MyClass.java
>> >> com/company/mypackage/utility
>> >> SomeUtility.java
>> >>
>> >> src/main/scala
>> >> com/company/mypackage
>> >> MyClass.scala
>> >>
>> >> While my scala classes can make use of my java classes at compile time
>> >> because of my 'executions' setup in the pom under the
>> maven-scala-plugin
>> >> within my build element, reporting is a problem for me.
>> >>
>> >> If my Scala class tries to import anything from
>> >> 'com.company.mypackage.utility' which lives in the java source tree
>> >> calling
>> >> 'mvn ... scala:doc' yields:
>> >>
>> >> ...
>> >> error: value utility is not a member of package com.company.mypackage
>> >> ...
>> >>
>> >> Can anyone help with configuring scala:doc to cope with this ?
>> >>
>> >> Thanks in advance for your help.
>> >>
>> >> Regards,
>> >>
>> >> Ross.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

Thanks, I'll try to find/fix the issue  for the next release of vscaladoc.

On Fri, Feb 27, 2009 at 11:49, rossputin <rossajmcd@yahoo.co.uk> wrote:

Hi David.

Here is a small sample project which compiles, but fails on 'scala:doc'.

Thanks.

Ross.
http://www.nabble.com/file/p22243449/scala_java_maven.tgz
scala_java_maven.tgz


David Bernard-3 wrote:
>
> Hi,
>
> scaladoc and vscaladoc delegate a big part of the job (creating the Data
> Model) to scalac (from where your issue seems to come).
> could you provide a sample test project with your "execution" setup.
> Or at least your pom.xml and the full log.
>
> /davidB
>
> On Fri, Feb 27, 2009 at 10:39, rossputin <rossajmcd@yahoo.co.uk> wrote:
>
>>
>> Hi Josh.
>>
>> I dropped scaladoc and plugged in vscaladoc like you suggested, using:
>>
>> <configuration>
>>  <vscalaVersion>1.0</vscalaVersion>
>> </configuration>
>>
>> in my reporting plugin.
>>
>> It seems I get the same result.  Perhaps I missed something out ?
>>
>> Thanks for your help.
>>
>> Regards,
>>
>> Ross.
>>
>>
>>
>>
>> Josh Suereth wrote:
>> >
>> > I'd love to help!
>> >
>> > Unfortunately, I'm not planning on supporting anything major (in the
>> > maven-scala-plugin) with scaladoc until there is a scaladoc maintainer.
>> > I'm unsure of whether scaladoc was ever updated to handle mixed
>> java/scala
>> > projects, but I'm skeptical.
>> >
>> > In the meantime, If you can run scaladoc locally (not inside maven),
>> are
>> > you
>> > seeing the same error?
>> >
>> > There's a known issue with scaladoc on windows (and many bugs in the
>> scala
>> > trac database).  I would make sure you're not running into one of
>> those.
>> >
>> > Also, you may want to try vscaladoc as I believe it's still being
>> > maintained
>> > by David Bernard.
>> >
>> >
>> > -Josh
>> >
>> >
>> >
>> > On Thu, Feb 26, 2009 at 10:06 AM, rossputin <rossajmcd@yahoo.co.uk>
>> wrote:
>> >
>> >>
>> >> Hi.
>> >>
>> >> My setup is something like:
>> >>
>> >> src/main/java
>> >>    com/company/mypackage
>> >>        MyClass.java
>> >>    com/company/mypackage/utility
>> >>        SomeUtility.java
>> >>
>> >> src/main/scala
>> >>    com/company/mypackage
>> >>        MyClass.scala
>> >>
>> >> While my scala classes can make use of my java classes at compile time
>> >> because of my 'executions' setup in the pom under the
>> maven-scala-plugin
>> >> within my build element, reporting is a problem for me.
>> >>
>> >> If my Scala class tries to import anything from
>> >> 'com.company.mypackage.utility' which lives in the java source tree
>> >> calling
>> >> 'mvn ... scala:doc' yields:
>> >>
>> >> ...
>> >> error: value utility is not a member of package com.company.mypackage
>> >> ...
>> >>
>> >> Can anyone help with configuring scala:doc to cope with this ?
>> >>
>> >> Thanks in advance for your help.
>> >>
>> >> Regards,
>> >>
>> >> Ross.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22226047.html
>> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22242407.html
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

--
View this message in context: http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22243449.html
Sent from the Scala - Tools mailing list archive at Nabble.com.

Hi David.

I also sent the sample project to your personal email.

Regards,

Ross.

David Bernard-3 wrote:
>
> Thanks, I'll try to find/fix the issue for the next release of vscaladoc.
>
> On Fri, Feb 27, 2009 at 11:49, rossputin wrote:
>
>>
>> Hi David.
>>
>> Here is a small sample project which compiles, but fails on 'scala:doc'.
>>
>> Thanks.
>>
>> Ross.
>> http://www.nabble.com/file/p22243449/scala_java_maven.tgz
>> scala_java_maven.tgz
>>
>>
>> David Bernard-3 wrote:
>> >
>> > Hi,
>> >
>> > scaladoc and vscaladoc delegate a big part of the job (creating the
>> Data
>> > Model) to scalac (from where your issue seems to come).
>> > could you provide a sample test project with your "execution" setup.
>> > Or at least your pom.xml and the full log.
>> >
>> > /davidB
>> >
>> > On Fri, Feb 27, 2009 at 10:39, rossputin wrote:
>> >
>> >>
>> >> Hi Josh.
>> >>
>> >> I dropped scaladoc and plugged in vscaladoc like you suggested, using:
>> >>
>> >>
>> >> 1.0
>> >>
>> >>
>> >> in my reporting plugin.
>> >>
>> >> It seems I get the same result. Perhaps I missed something out ?
>> >>
>> >> Thanks for your help.
>> >>
>> >> Regards,
>> >>
>> >> Ross.
>> >>
>> >>
>> >>
>> >>
>> >> Josh Suereth wrote:
>> >> >
>> >> > I'd love to help!
>> >> >
>> >> > Unfortunately, I'm not planning on supporting anything major (in the
>> >> > maven-scala-plugin) with scaladoc until there is a scaladoc
>> maintainer.
>> >> > I'm unsure of whether scaladoc was ever updated to handle mixed
>> >> java/scala
>> >> > projects, but I'm skeptical.
>> >> >
>> >> > In the meantime, If you can run scaladoc locally (not inside maven),
>> >> are
>> >> > you
>> >> > seeing the same error?
>> >> >
>> >> > There's a known issue with scaladoc on windows (and many bugs in the
>> >> scala
>> >> > trac database). I would make sure you're not running into one of
>> >> those.
>> >> >
>> >> > Also, you may want to try vscaladoc as I believe it's still being
>> >> > maintained
>> >> > by David Bernard.
>> >> >
>> >> >
>> >> > -Josh
>> >> >
>> >> >
>> >> >
>> >> > On Thu, Feb 26, 2009 at 10:06 AM, rossputin
>> >> wrote:
>> >> >
>> >> >>
>> >> >> Hi.
>> >> >>
>> >> >> My setup is something like:
>> >> >>
>> >> >> src/main/java
>> >> >> com/company/mypackage
>> >> >> MyClass.java
>> >> >> com/company/mypackage/utility
>> >> >> SomeUtility.java
>> >> >>
>> >> >> src/main/scala
>> >> >> com/company/mypackage
>> >> >> MyClass.scala
>> >> >>
>> >> >> While my scala classes can make use of my java classes at compile
>> time
>> >> >> because of my 'executions' setup in the pom under the
>> >> maven-scala-plugin
>> >> >> within my build element, reporting is a problem for me.
>> >> >>
>> >> >> If my Scala class tries to import anything from
>> >> >> 'com.company.mypackage.utility' which lives in the java source tree
>> >> >> calling
>> >> >> 'mvn ... scala:doc' yields:
>> >> >>
>> >> >> ...
>> >> >> error: value utility is not a member of package
>> com.company.mypackage
>> >> >> ...
>> >> >>
>> >> >> Can anyone help with configuring scala:doc to cope with this ?
>> >> >>
>> >> >> Thanks in advance for your help.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Ross.
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> >> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

Hi,

I can reproduce your problem if I did a clean before running scala:doc. But If you run "mvn compile" before then java classes are in target/classes and available for the run of scala:doc
So try

"mvn compile scala:doc" and you will have scaladoc (or vscaladoc) under target/site/scaladocs

/davidB

On Fri, Feb 27, 2009 at 15:23, rossputin <rossajmcd@yahoo.co.uk> wrote:

Hi David.

I also sent the sample project to your personal email.

Regards,

Ross.



David Bernard-3 wrote:
>
> Thanks, I'll try to find/fix the issue  for the next release of vscaladoc.
>
> On Fri, Feb 27, 2009 at 11:49, rossputin <rossajmcd@yahoo.co.uk> wrote:
>
>>
>> Hi David.
>>
>> Here is a small sample project which compiles, but fails on 'scala:doc'.
>>
>> Thanks.
>>
>> Ross.
>> http://www.nabble.com/file/p22243449/scala_java_maven.tgz
>> scala_java_maven.tgz
>>
>>
>> David Bernard-3 wrote:
>> >
>> > Hi,
>> >
>> > scaladoc and vscaladoc delegate a big part of the job (creating the
>> Data
>> > Model) to scalac (from where your issue seems to come).
>> > could you provide a sample test project with your "execution" setup.
>> > Or at least your pom.xml and the full log.
>> >
>> > /davidB
>> >
>> > On Fri, Feb 27, 2009 at 10:39, rossputin <rossajmcd@yahoo.co.uk> wrote:
>> >
>> >>
>> >> Hi Josh.
>> >>
>> >> I dropped scaladoc and plugged in vscaladoc like you suggested, using:
>> >>
>> >> <configuration>
>> >>  <vscalaVersion>1.0</vscalaVersion>
>> >> </configuration>
>> >>
>> >> in my reporting plugin.
>> >>
>> >> It seems I get the same result.  Perhaps I missed something out ?
>> >>
>> >> Thanks for your help.
>> >>
>> >> Regards,
>> >>
>> >> Ross.
>> >>
>> >>
>> >>
>> >>
>> >> Josh Suereth wrote:
>> >> >
>> >> > I'd love to help!
>> >> >
>> >> > Unfortunately, I'm not planning on supporting anything major (in the
>> >> > maven-scala-plugin) with scaladoc until there is a scaladoc
>> maintainer.
>> >> > I'm unsure of whether scaladoc was ever updated to handle mixed
>> >> java/scala
>> >> > projects, but I'm skeptical.
>> >> >
>> >> > In the meantime, If you can run scaladoc locally (not inside maven),
>> >> are
>> >> > you
>> >> > seeing the same error?
>> >> >
>> >> > There's a known issue with scaladoc on windows (and many bugs in the
>> >> scala
>> >> > trac database).  I would make sure you're not running into one of
>> >> those.
>> >> >
>> >> > Also, you may want to try vscaladoc as I believe it's still being
>> >> > maintained
>> >> > by David Bernard.
>> >> >
>> >> >
>> >> > -Josh
>> >> >
>> >> >
>> >> >
>> >> > On Thu, Feb 26, 2009 at 10:06 AM, rossputin <rossajmcd@yahoo.co.uk>
>> >> wrote:
>> >> >
>> >> >>
>> >> >> Hi.
>> >> >>
>> >> >> My setup is something like:
>> >> >>
>> >> >> src/main/java
>> >> >>    com/company/mypackage
>> >> >>        MyClass.java
>> >> >>    com/company/mypackage/utility
>> >> >>        SomeUtility.java
>> >> >>
>> >> >> src/main/scala
>> >> >>    com/company/mypackage
>> >> >>        MyClass.scala
>> >> >>
>> >> >> While my scala classes can make use of my java classes at compile
>> time
>> >> >> because of my 'executions' setup in the pom under the
>> >> maven-scala-plugin
>> >> >> within my build element, reporting is a problem for me.
>> >> >>
>> >> >> If my Scala class tries to import anything from
>> >> >> 'com.company.mypackage.utility' which lives in the java source tree
>> >> >> calling
>> >> >> 'mvn ... scala:doc' yields:
>> >> >>
>> >> >> ...
>> >> >> error: value utility is not a member of package
>> com.company.mypackage
>> >> >> ...
>> >> >>
>> >> >> Can anyone help with configuring scala:doc to cope with this ?
>> >> >>
>> >> >> Thanks in advance for your help.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Ross.
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22226047.html
>> >> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22242407.html
>> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22243449.html
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

--
View this message in context: http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22246841.html
Sent from the Scala - Tools mailing list archive at Nabble.com.

Hi David.

Thanks. I wonder, is it possible to get that rolled in automatically? I
suppose we could in some way ensure the java was compiled and available in
target/classes in order for scala:doc to be called successfully?

Also, running 'mvn site' gives me:

.....

INFO] Generating "ScalaDocs" report.
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at java.util.regex.Matcher.getTextLength(Matcher.java:1127)
at java.util.regex.Matcher.reset(Matcher.java:284)
at java.util.regex.Matcher.(Matcher.java:205)
at java.util.regex.Pattern.matcher(Pattern.java:879)
at org.scala_tools.maven.VersionNumber.(VersionNumber.java:20)
at
org.scala_tools.maven.ScalaDocMojo.getScalaCommand(ScalaDocMojo.java:231)
at org.scala_tools.maven.ScalaDocMojo.generate(ScalaDocMojo.java:268)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)

.....

Thanks,

Ross.

David Bernard-3 wrote:
>
> Hi,
>
> I can reproduce your problem if I did a clean before running scala:doc.
> But
> If you run "mvn compile" before then java classes are in target/classes
> and
> available for the run of scala:doc
> So try
>
> "mvn compile scala:doc" and you will have scaladoc (or vscaladoc) under
> target/site/scaladocs
>
> /davidB
>
> On Fri, Feb 27, 2009 at 15:23, rossputin wrote:
>
>>
>> Hi David.
>>
>> I also sent the sample project to your personal email.
>>
>> Regards,
>>
>> Ross.
>>
>>
>>
>> David Bernard-3 wrote:
>> >
>> > Thanks, I'll try to find/fix the issue for the next release of
>> vscaladoc.
>> >
>> > On Fri, Feb 27, 2009 at 11:49, rossputin wrote:
>> >
>> >>
>> >> Hi David.
>> >>
>> >> Here is a small sample project which compiles, but fails on
>> 'scala:doc'.
>> >>
>> >> Thanks.
>> >>
>> >> Ross.
>> >> http://www.nabble.com/file/p22243449/scala_java_maven.tgz
>> >> scala_java_maven.tgz
>> >>
>> >>
>> >> David Bernard-3 wrote:
>> >> >
>> >> > Hi,
>> >> >
>> >> > scaladoc and vscaladoc delegate a big part of the job (creating the
>> >> Data
>> >> > Model) to scalac (from where your issue seems to come).
>> >> > could you provide a sample test project with your "execution" setup.
>> >> > Or at least your pom.xml and the full log.
>> >> >
>> >> > /davidB
>> >> >
>> >> > On Fri, Feb 27, 2009 at 10:39, rossputin
>> wrote:
>> >> >
>> >> >>
>> >> >> Hi Josh.
>> >> >>
>> >> >> I dropped scaladoc and plugged in vscaladoc like you suggested,
>> using:
>> >> >>
>> >> >>
>> >> >> 1.0
>> >> >>
>> >> >>
>> >> >> in my reporting plugin.
>> >> >>
>> >> >> It seems I get the same result. Perhaps I missed something out ?
>> >> >>
>> >> >> Thanks for your help.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Ross.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Josh Suereth wrote:
>> >> >> >
>> >> >> > I'd love to help!
>> >> >> >
>> >> >> > Unfortunately, I'm not planning on supporting anything major (in
>> the
>> >> >> > maven-scala-plugin) with scaladoc until there is a scaladoc
>> >> maintainer.
>> >> >> > I'm unsure of whether scaladoc was ever updated to handle mixed
>> >> >> java/scala
>> >> >> > projects, but I'm skeptical.
>> >> >> >
>> >> >> > In the meantime, If you can run scaladoc locally (not inside
>> maven),
>> >> >> are
>> >> >> > you
>> >> >> > seeing the same error?
>> >> >> >
>> >> >> > There's a known issue with scaladoc on windows (and many bugs in
>> the
>> >> >> scala
>> >> >> > trac database). I would make sure you're not running into one of
>> >> >> those.
>> >> >> >
>> >> >> > Also, you may want to try vscaladoc as I believe it's still being
>> >> >> > maintained
>> >> >> > by David Bernard.
>> >> >> >
>> >> >> >
>> >> >> > -Josh
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Thu, Feb 26, 2009 at 10:06 AM, rossputin
>> > >
>> >> >> wrote:
>> >> >> >
>> >> >> >>
>> >> >> >> Hi.
>> >> >> >>
>> >> >> >> My setup is something like:
>> >> >> >>
>> >> >> >> src/main/java
>> >> >> >> com/company/mypackage
>> >> >> >> MyClass.java
>> >> >> >> com/company/mypackage/utility
>> >> >> >> SomeUtility.java
>> >> >> >>
>> >> >> >> src/main/scala
>> >> >> >> com/company/mypackage
>> >> >> >> MyClass.scala
>> >> >> >>
>> >> >> >> While my scala classes can make use of my java classes at
>> compile
>> >> time
>> >> >> >> because of my 'executions' setup in the pom under the
>> >> >> maven-scala-plugin
>> >> >> >> within my build element, reporting is a problem for me.
>> >> >> >>
>> >> >> >> If my Scala class tries to import anything from
>> >> >> >> 'com.company.mypackage.utility' which lives in the java source
>> tree
>> >> >> >> calling
>> >> >> >> 'mvn ... scala:doc' yields:
>> >> >> >>
>> >> >> >> ...
>> >> >> >> error: value utility is not a member of package
>> >> com.company.mypackage
>> >> >> >> ...
>> >> >> >>
>> >> >> >> Can anyone help with configuring scala:doc to cope with this ?
>> >> >> >>
>> >> >> >> Thanks in advance for your help.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >>
>> >> >> >> Ross.
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> >> >> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> >> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-...
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

It's a bug in maven-scala-plugin (thanks to report it), I'll fix it later.
workaround : set scalaVersion explicitly

            <plugin>
                <groupId>org.scala-tools</groupId>
                <artifactId>maven-scala-plugin</artifactId>
                <configuration>
                    <scalaVersion>2.7.3</scalaVersion>
                    <vscalaVersion>1.0</vscalaVersion>
                </configuration>
            </plugin>

/davidB

On Fri, Feb 27, 2009 at 15:45, rossputin <rossajmcd@yahoo.co.uk> wrote:

Hi David.

Thanks.  I wonder, is it possible to get that rolled in automatically?  I
suppose we could in some way ensure the java was compiled and available in
target/classes in order for scala:doc to be called successfully?

Also, running 'mvn site' gives me:

.....

INFO] Generating "ScalaDocs" report.
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
       at java.util.regex.Matcher.getTextLength(Matcher.java:1127)
       at java.util.regex.Matcher.reset(Matcher.java:284)
       at java.util.regex.Matcher.<init>(Matcher.java:205)
       at java.util.regex.Pattern.matcher(Pattern.java:879)
       at org.scala_tools.maven.VersionNumber.<init>(VersionNumber.java:20)
       at
org.scala_tools.maven.ScalaDocMojo.getScalaCommand(ScalaDocMojo.java:231)
       at org.scala_tools.maven.ScalaDocMojo.generate(ScalaDocMojo.java:268)
       at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
       at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
       at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)


.....

Thanks,

Ross.



David Bernard-3 wrote:
>
> Hi,
>
> I can reproduce your problem if I did a clean before running scala:doc.
> But
> If you run "mvn compile" before then java classes are in target/classes
> and
> available for the run of scala:doc
> So try
>
> "mvn compile scala:doc" and you will have scaladoc (or vscaladoc) under
> target/site/scaladocs
>
> /davidB
>
> On Fri, Feb 27, 2009 at 15:23, rossputin <rossajmcd@yahoo.co.uk> wrote:
>
>>
>> Hi David.
>>
>> I also sent the sample project to your personal email.
>>
>> Regards,
>>
>> Ross.
>>
>>
>>
>> David Bernard-3 wrote:
>> >
>> > Thanks, I'll try to find/fix the issue  for the next release of
>> vscaladoc.
>> >
>> > On Fri, Feb 27, 2009 at 11:49, rossputin <rossajmcd@yahoo.co.uk> wrote:
>> >
>> >>
>> >> Hi David.
>> >>
>> >> Here is a small sample project which compiles, but fails on
>> 'scala:doc'.
>> >>
>> >> Thanks.
>> >>
>> >> Ross.
>> >> http://www.nabble.com/file/p22243449/scala_java_maven.tgz
>> >> scala_java_maven.tgz
>> >>
>> >>
>> >> David Bernard-3 wrote:
>> >> >
>> >> > Hi,
>> >> >
>> >> > scaladoc and vscaladoc delegate a big part of the job (creating the
>> >> Data
>> >> > Model) to scalac (from where your issue seems to come).
>> >> > could you provide a sample test project with your "execution" setup.
>> >> > Or at least your pom.xml and the full log.
>> >> >
>> >> > /davidB
>> >> >
>> >> > On Fri, Feb 27, 2009 at 10:39, rossputin <rossajmcd@yahoo.co.uk>
>> wrote:
>> >> >
>> >> >>
>> >> >> Hi Josh.
>> >> >>
>> >> >> I dropped scaladoc and plugged in vscaladoc like you suggested,
>> using:
>> >> >>
>> >> >> <configuration>
>> >> >>  <vscalaVersion>1.0</vscalaVersion>
>> >> >> </configuration>
>> >> >>
>> >> >> in my reporting plugin.
>> >> >>
>> >> >> It seems I get the same result.  Perhaps I missed something out ?
>> >> >>
>> >> >> Thanks for your help.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Ross.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Josh Suereth wrote:
>> >> >> >
>> >> >> > I'd love to help!
>> >> >> >
>> >> >> > Unfortunately, I'm not planning on supporting anything major (in
>> the
>> >> >> > maven-scala-plugin) with scaladoc until there is a scaladoc
>> >> maintainer.
>> >> >> > I'm unsure of whether scaladoc was ever updated to handle mixed
>> >> >> java/scala
>> >> >> > projects, but I'm skeptical.
>> >> >> >
>> >> >> > In the meantime, If you can run scaladoc locally (not inside
>> maven),
>> >> >> are
>> >> >> > you
>> >> >> > seeing the same error?
>> >> >> >
>> >> >> > There's a known issue with scaladoc on windows (and many bugs in
>> the
>> >> >> scala
>> >> >> > trac database).  I would make sure you're not running into one of
>> >> >> those.
>> >> >> >
>> >> >> > Also, you may want to try vscaladoc as I believe it's still being
>> >> >> > maintained
>> >> >> > by David Bernard.
>> >> >> >
>> >> >> >
>> >> >> > -Josh
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Thu, Feb 26, 2009 at 10:06 AM, rossputin
>> <rossajmcd@yahoo.co.uk
>> >
>> >> >> wrote:
>> >> >> >
>> >> >> >>
>> >> >> >> Hi.
>> >> >> >>
>> >> >> >> My setup is something like:
>> >> >> >>
>> >> >> >> src/main/java
>> >> >> >>    com/company/mypackage
>> >> >> >>        MyClass.java
>> >> >> >>    com/company/mypackage/utility
>> >> >> >>        SomeUtility.java
>> >> >> >>
>> >> >> >> src/main/scala
>> >> >> >>    com/company/mypackage
>> >> >> >>        MyClass.scala
>> >> >> >>
>> >> >> >> While my scala classes can make use of my java classes at
>> compile
>> >> time
>> >> >> >> because of my 'executions' setup in the pom under the
>> >> >> maven-scala-plugin
>> >> >> >> within my build element, reporting is a problem for me.
>> >> >> >>
>> >> >> >> If my Scala class tries to import anything from
>> >> >> >> 'com.company.mypackage.utility' which lives in the java source
>> tree
>> >> >> >> calling
>> >> >> >> 'mvn ... scala:doc' yields:
>> >> >> >>
>> >> >> >> ...
>> >> >> >> error: value utility is not a member of package
>> >> com.company.mypackage
>> >> >> >> ...
>> >> >> >>
>> >> >> >> Can anyone help with configuring scala:doc to cope with this ?
>> >> >> >>
>> >> >> >> Thanks in advance for your help.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >>
>> >> >> >> Ross.
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22226047.html
>> >> >> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22242407.html
>> >> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22243449.html
>> >> Sent from the Scala - Tools mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22246841.html
>> Sent from the Scala - Tools mailing list archive at Nabble.com.
>>
>>
>
>

--
View this message in context: http://www.nabble.com/maven-scala-plugin-scala-and-java-mixture-problem-with-scaladoc-tp22226047p22247247.html
Sent from the Scala - Tools mailing list archive at Nabble.com.