Yes, see the inline response
On Tue, Jan 13, 2009 at 2:55 PM, Meredith Gregory
<[email protected]>wrote:
> Josh,
>
> Thanks for the response. Just to be clear, is the plugin in question the
> one listed below? What is the configuration that gets me the 2.8 version?
>
> Best wishes,
>
> --greg
>
> <plugin>
> <groupId>org.scala-tools</groupId>
> <artifactId>maven-scala-plugin</artifactId>
<version>2.8</version>
>
> <executions>
> <execution>
> <goals>
> <goal>compile</goal>
> <goal>testCompile</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <scalaVersion>${scala.version}</scalaVersion>
> </configuration>
> </plugin>
>
>
> On Tue, Jan 13, 2009 at 11:42 AM, Josh Suereth
> <[email protected]>wrote:
>
>> Use an older version of the maven plugin (like 2.8) *or* wait till I have
>> the free time to make the option.
>>
>> -Josh
>>
>>
>> On Tue, Jan 13, 2009 at 2:34 PM, Meredith Gregory <
>> [email protected]> wrote:
>>
>>> Scalads and lasses,
>>>
>>> i believe i've hit a bug in the scalac java compilation. i'm not 100%
>>> certain. To verify i need a way to tell scalac *not* to compile java files
>>> in the mvn build process for a lift app.
>>>
>>> i will briefly describe a portion of my build process. i'm building
>>> several DSLs. i use BNFC to rapid prototype the grammars the build the java
>>> parsers. Then i use the parsers in scala+lift applications. The reason i
>>> mention this is because BNFC squirts out a makefile to build the java. So,
>>> i've got a standalone build using gnu make just for the java parser. i can
>>> compare this to mvn build. The parser is included in the model part of a
>>> lift app and built using the mvn build system.
>>>
>>> i just made a change to a parser and verified it builds and works as a
>>> java parser. Then i essentially copied the working code into the lift app.
>>> Note, when i build my app with mvn i've got the javac compilation line
>>> configured to show the command line. So, when i hit the following error, i'm
>>> pretty sure this is coming from the scalac compiler. Since the file in
>>> question compiles just fine, i'm fairly certain this is a bug in scalac.
>>>
>>> i can make all the code available, but i really, really don't have the
>>> cycles just now to reduce this to a smallest test case. i don't have to be
>>> blocked it i can just stop scalac from compiling the java files.
>>>
>>> Best wishes,
>>>
>>> --greg
>>>
>>> --
>>> L.G. Meredith
>>> Managing Partner
>>> Biosimilarity LLC
>>> 806 55th St NE
>>> Seattle, WA 98105
>>>
>>> +1 206.650.3740
>>>
>>> http://biosimilarity.blogspot.com
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> L.G. Meredith
> Managing Partner
> Biosimilarity LLC
> 806 55th St NE
> Seattle, WA 98105
>
> +1 206.650.3740
>
> http://biosimilarity.blogspot.com
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---