The plugin 'org.apache.maven.plugins:maven-scala-plugin' does not exist

[Timothy Perrett]

Guys,

Im getting the below when building a fresh pull of lift - It doesnt
even appear to be looking at scala-tools, despite it being defined.
Very odd, any ideas?

Cheers, Tim


[INFO] Searching repository for plugin with prefix: 'scala'.
[INFO] org.apache.maven.plugins: checking for updates from scala-
tools.release
[INFO] org.apache.maven.plugins: checking for updates from scala-
tools.snapshot
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from scala-
tools.release
[INFO] org.codehaus.mojo: checking for updates from scala-
tools.snapshot
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-scala-plugin: checking
for updates from scala-tools.release
[INFO] artifact org.apache.maven.plugins:maven-scala-plugin: checking
for updates from scala-tools.snapshot
[INFO] artifact org.apache.maven.plugins:maven-scala-plugin: checking
for updates from central
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-scala-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------

[YING-KWANG TU]

hi Tim,

May I ask which version of lift is in question? master? 1.1-M6?

Thank you.
  yk

[Indrajit Raychaudhuri]

Tim,

That's odd indeed. Hopefully your local repository is not broken.

Can you please attempt it on the branch irc_wip_restruct_stage and see
if it happens there too? If it still persists for you I'll take a look
later in the day.

Cheers, Indrajit

[Timothy Perrett]

Hey Indrajit,

No that branch does not work either - im trying to build from the very
root of lift - this should work!! I have the maven plugin in my local
repo and build lots of other scala projects fine; this has only been
an issue since your restructure.

Any ideas what could be going wrong? Could do with fixing this ASAP as
its annoying as hell to have to build separate modules.

Cheers, Tim

[Indrajit Raychaudhuri]

Tim,

That's confusing to me too. I was trying to see if it has something
related to the problem that affects Netbeans. Looks like it's not.

Can you please send me the output of mvn goal with -X switch?

Cheers, Indrajit

[Timothy Perrett]

Indrajit,

I found out what the problem is. I always run:

mvn clean install scala:doc

this fails with the new setup, where as:

mvn clean install

works no problem.

Can you please configure the pom.xml so that its possible to run
documentation from the root... its a pain in the ass to have to
generate documentation on a per-module basis.

Cheers, Tim

[Indrajit Raychaudhuri]

Tim,

Got it! I'll try to fix this and post it in few hours.
Committers, is it possible to make an exception to the cut off date for
the M7 for this one?

Cheers, Indrajit

[David Pollak]

On Fri, Oct 30, 2009 at 7:44 AM, Indrajit Raychaudhuri <indr...@gmail.com> wrote:

Tim,

Got it! I'll try to fix this and post it in few hours.
Committers, is it possible to make an exception to the cut off date for
the M7 for this one?

We're in code slush which means that code can be committed to master as long as it fixes a bug (rather than being a new feature or enhancement.)  This strikes me as a real, hardcore bug... if you can't build it, it's a bug ;-)

So, please open a ticket, make the fix, and let's get it into master.
 

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

[Indrajit Raychaudhuri]

Found it!

Looks like build plugin settings aren't picked up from reporting plugin
settings unless that appears in <build><plugin/></build>. This hurts :(

Workaround coming up. Not a good one but should work. I'll investigate a
cleaner fix/workaround at a later point.

Cheers, Indrajit