has this already been applied to the pom?
should it work now?
thanks alot,
kai
On Apr 22, 4:11 pm, Josh Suereth wrote:
> On Wed, Apr 22, 2009 at 8:53 AM, Miles Sabin wrote:
>
> > On Wed, Apr 22, 2009 at 1:16 PM, Josh Suereth
> > wrote:
> > > The maven-eclipse-plugin is currently "broken" in the sense that it won't
> > > pay attention to the source directories configured by the
> > maven-scala-plugin.
> > > The developers seem unwilling to try to integrate these two plugins, as
> > they
> > > have a "workaround".
>
> > Which developers are these? Where should I be applying pressure?
>
> The maven-eclipse-plugin. We've recently attracted the attention of Jason
> van-zyl so hoepfully that will encourage more support for scala :)
>
>
>
> > > The workaround is to configure the build-helper-plugin in your pom with
> > the
> > > correct source directories, and then when running maven eclispe:eclipse
> > you
> > > will see these show up. Very intuitive eh?
>
> > Can't that workaround be made the default behaviour for Maven Scala
> > modules? At least then things would work out of the box with Eclipse
> > (if I'm understanding the situation correctly).
>
> Perhaps lift should update it archetypes appropriately? I'll update the
> documentation for the maven-scala-plugin accordingly. I do not use the
> maven-eclipse-plugin personally, so it hasn't caused me pain directly. I
> also recommend using one of the plugins for eclipse that actively synchs
> your data internally rather than updating eclipse configuration files
> outside of eclipse. However, I'll try to make sure we provide better help
> in this area.
>
> Would one of the lift committers please add the following to your plugins
> section in the poms for your acrchetypes:
>
>
> org.codehaus.mojo
> build-helper-maven-plugin
>
>
> add-source
> generate-sources
>
> add-source
>
>
>
> src/main/scala
>
>
>
>
> add-test-source
> generate-sources
>
> add-test-source
>
>
>
> src/test/scala
>
>
>
>
>
>
>
> > TBH, I'm a little bit cheesed off to discover that lots of the alleged
> > brokenness of the Scala IDE for Eclipse seem to boil down to Maven
> > trampling all over internal Eclipse metadata.
>
> True, the broken-ness is actually with the maven-eclipse integrations
> (specifically, the maven-eclipse-plugin "cheating" when it comes to
> calculating source directories). I understand the gripe, however when
> integrating diverse plugins, I think misconceptions on who's to blame happen
> all the time. The big fail here is that Maven is still working on being
> friendlier for multi-language projects, and some of the "downstream"
> projects aren't up-to-date yet. I'm not aware of any "maven aspects" like
> feature that is flexible enoguh to allow me to monkey-patch fixes on plugins
> I have no control over, so I'm limited to trying to submit patches when
> applicable. I hope it's not terribly inconvenient, but feel free to send
> any Maven + Eclipse questions (as they relate to adding scala support) my
> way. I'm hoping to solve most of these issues with ESMi.
>
> -Josh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
