sonatype / m2eclipse-scala

m2eclipse-scala

m2eclipse-scala is a work in progress to ease integration between m2eclipse and scala-ide for eclipse.

• issue tracker : m2eclipse-scala at github
• mailing-list : scala-ide-user
• update-site : http://alchim31.free.fr/m2e-scala/update-site
• update-site for previous-version follow pattern : http://alchim31.free.fr/m2e-scala/update-site-..

Working configuration

The plugin is "validated" by importing into Eclipse the sample projects :

• Scala Only (no java)
• Scala depends of some java code
• Scala and Java cyclic dependency (configuration longer than mono direction scala -> java or java -> scala to compile under maven)
• Java main code and Scala for test
• Custom Layout java + scala cyclic dependencies, java+scala under the same source folder src and test (for test source folder).
• Lift based project created from a shell created + imported project (used lift-archetype-basic 2.0-scala280-SNAPSHOT)

Changes

0.5.1

• remove use of Jobs to update classpath (fix #35 & #36 )

0.5.0

• improve compatibility with scala version auto-detection of Scala-IDE 4.0

0.4.3

• add license in feature (EPL)
• fix a bug in support of "add-source": "src/main/scala" and "src/test/scala" should be added when "add-source" is executed

0.4.2

• add support for eclipse WTP contribution of Fred Bricon
• upgrade tycho (0.15.0)
• remove automatic add of "src/main/scala" and "src/test/scala"

0.4.1

• upgrade tycho (0.14.1), eclipse p2 repository (indigo)
• modify lifecycle: every goals are modified to "ignore" or to avoid run during incremental compilation
• add JavaNature to project if it missing

0.4.0

• remove scala-tools.org from catalags
• add support for scala-maven-plugin
• sort classpath and entries of the project

0.3.1

• support of m2eclipse 1.0.0
• upate update-site to propose install of m2eclipse

0.3.0

• support of m2eclipse 0.13.0

0.2.3

• change urls of scala-tools.org catalags

0.2.2

• rebuild to work with m2eclipse 0.12

0.2.1

• fix critical bug about detection/activation of scala (plugin, nature) => 0.2.0 useless

0.2.0

• should work with lift-archetype-basic 2.0-scala280-SNAPSHOT (new sample project added)
• support current and futur ids of scala-ide, select from the installed plugin (ch.epfl... and org.scala-ide....)

0.1.0

• reintegration to sonatype repository

0.0.5

• use assembla as "project host" to be under Scala-IDE umbrella
• re-do tycho configuration (to build on any box)
• rename directory
• generate update-site via tycho
• align groupId/artifactId to m2eclipse-extras

0.0.4

• include a workaround to run JUnit test, but right-click on JUnit test doesn't propose 'Run as unit test'. Tu run as junit :
  • select source file and use keybord shortcut (Alt+Shit+X T)
    • source file have to be named with test class name and being in the 'right' directory (like in java)
    • I only test with annotation (see source of samples projects listed on wiki)
  • create JUnit Launch configuration

0.0.3

• try to fix a issue (NPE) if default folders doesn't exist

0.0.2

• auto add "src/main/scala" and "src/test/scala" if you don't use goal "add-sources" (nor )
• add samples project http://github.com/sonatype/m2eclipse-scala/tree/master/samples/
• put documentation at https://www.assembla.com/wiki/show/scala-ide/With_M2Eclipse

0.0.1

• I fork the m2eclipse-scala project from sonatype and add the following feature
• remove of scala-library, scala-compiler, scala-dbc, scala-swing from "Maven Dependencies" Container (under eclipse only)
• re-order JRE Container and Scala Container (to avoid scala.ScalaObject NotFound and C° when use "Run As Scala Application")
• add Scala-tools.org catalog

m2eclipse-scala's Issues

DepShield encountered errors while building your project

The project could not be analyzed because of build errors. Please review the error messages here. Another build will be scheduled within 24 hours. If the build is successful this issue will be closed, otherwise the error message will be updated.

_{This is an automated GitHub Issue created by Sonatype DepShield. GitHub Apps, including DepShield, can be managed from the Developer settings of the repository administrators.}

When converting scala project to maven-nature...

Scala nature is overwritten by java nature?

All of the icons in the package explorer except the main project folder icon revert to grey java "J" icons, and main will no longer run as a Scala executable?

sample project "prj-scala-only" compilation failure

while issuing the command:
$mvn -X clean install
Getting the following error (some sequence of snaps is attached)

java.util.ConcurrentModificationException when running 0.5.0 with scala eclipse 4.0rc1

Scala IDE version:
4.0.0.rc1-2_11-201410101606-7b622ed
Scala compiler version:
2.11.2.
Scala library version:
2.11.2.
Eclipse version:
4.4.0.v20140925-0400
Class loader store: 0 entries
Maven Integration for Scala IDE 0.5.0.201410100759

whenever I try to do "Maven/Update project" i get:

An internal error occurred during: "Updating Maven Project".

java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:886)
at java.util.ArrayList$Itr.next(ArrayList.java:836)
at org.eclipse.m2e.jdt.internal.BuildPathManager.configureAttchedSourcesAndJavadoc(BuildPathManager.java:283)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:255)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:747)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:876)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:291)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:374)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Should use the scala library that is specified in the pom

I noticed that the Scala version being used is the one that comes with the bundle rather than the one provided by the POM. This yields an error when using Akka Actors 2.1-M1 which uses 2.10 of Scala. Ideally it would already be part of Maven dependencies so the scala libraries should not need to be loaded separately.

ScalaProjectConfigurator should sort .classpath entries

David:

currently, presentation order of .classpath entries in eclipse after
"Maven -> Update Project ..." is random, since ScalaProjectConfigurator
just add entries and does not do any sorting;

this is rather annoying, since every time you run update,
you get a new layout :-)

instead, with alphabetical sorting activated, it should be:

src/main/java
src/main/scala
src/main/resources
src/test/java
src/test/scala
src/test/resources

thank you,

Andrei

m2eclipse seems to sort the classpath without a need

m2eclipse sorts the classpath so that the scala library is before the JRE elements on the bootclasspath:
https://github.com/sonatype/m2eclipse-scala/blob/master/org.maven.ide.eclipse.scala/src/org/maven/ide/eclipse/scala/ScalaProjectConfigurator.java#L192

But when an Eclipse project has the Scala Nature, this is done automatically. I've also added a test to check the builder works fine with a misordered classpath. I've played with a copy of prj-scala-only in which the classpath was misordered and found no ill effects either on build or Run as a Scala Application.

Would you mind checking the reordering of elements on classpath is really necessary ? If it isn't, I'd be happy to submit a PR which removes it.

Compiling tests from src/test/scala should produce .class files in target/test-classes. They end up in target/classes instead.

This makes for some bad interactions with command-line builds, which compile tests to target/test-classes. Since (I presume) target/test-classes takes higher precedence on the classpath than target/classes, if a test is edited and run in the IDE after a command line build, the old .class file from target/test-classes will be used, not the new, IDE-compiled one in target/classes.

A fix would be to make IDE-compiled .class files from sources in src/test/scala go to target/test-classes.

Discussion with more info on scala-ide-user:

https://groups.google.com/forum/?fromgroups=#!topic/scala-ide-user/47Aiw3CnJmA

SCALA Container still not being detected from Maven plugin

Using
Eclipse Oxygen.1
SCALA IDE 4.7.0
Maven Integration for Scala IDE 0.5.1.201410131304
m2e - Maven Integration for Eclipse 1.8.2.20171007-0217
Java 8
importing a Maven project containing
<plugin>
<groupId>net.alchim31.maven</groupId>
<artifactId>scala-maven-plugin</artifactId>
<version>3.3.1</version>
<executions>
<execution>
<goals>
<goal>compile</goal>
<goal>testCompile</goal>
</goals>
</execution>
</executions>
<configuration>
<scalaVersion>2.11.11</scalaVersion>
<scalaCompatVersion>2.11</scalaCompatVersion>
</configuration>
</plugin>

the detected SCALA Container in Eclipse imported project is 2.12.3
conflicting with Maven dependencies (cross-compilation issue)
while 2.11.11 was expected

Any thoughts?

Eclipse warning: More than one scala library found in the build path

I am getting this warning on my Scala only project.

I have these two in my Scala Library container:

/home/muhuk/lib/eclipse/plugins/org.scala-lang.scala-library_2.11.8.v20160304-115712-1706a37eb8.jar
/home/muhuk/lib/eclipse/plugins/org.scala-lang.scala-reflect_2.11.8.v20160304-115712-1706a37eb8.jar

Also in the Maven Dependencies:

M2_REPO/org/scala-lang/scala-library/2.11.8/scala-library-2.11.8.jar - /home/muhuk/.m2/repository/org/scala-lang/scala-library/2.11.8/scala-library-2.11.8.jar
M2_REPO/org/scala-lang/scala-reflect/2.11.7/scala-reflect-2.11.7.jar - /home/muhuk/.m2/repository/org/scala-lang/scala-reflect/2.11.7/scala-reflect-2.11.7.jar

Plugin versions:

Eclipse SDK 4.5.2.M20160212-1500
Scala IDE for Eclipse   4.4.0.v-2_11-201604010957-ff530d2
Maven Integration for Scala IDE 0.5.1.201410131304

My POM file like like:

<properties>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
    <encoding>UTF-8</encoding>
    <scala.version>2.11.8</scala.version>
    <scala.compat.version>2.11</scala.compat.version>
</properties>

<dependencies>
    <dependency>
        <groupId>org.scala-lang</groupId>
        <artifactId>scala-library</artifactId>
        <version>${scala.version}</version>
    </dependency>

    <!-- Test -->
    <dependency>
        <groupId>org.scalatest</groupId>
        <artifactId>scalatest_${scala.compat.version}</artifactId>
        <version>2.2.6</version>
        <scope>test</scope>
    </dependency>
    ...
    <dependency>
        <groupId>org.scalacheck</groupId>
        <artifactId>scalacheck_${scala.compat.version}</artifactId>
        <version>1.12.5</version>
        <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>org.scalamock</groupId>
        <artifactId>scalamock-scalatest-support_${scala.compat.version}</artifactId>
        <version>3.2.2</version>
        <scope>test</scope>
    </dependency>
</dependencies>

<build>
    <sourceDirectory>src/main/scala</sourceDirectory>
    <testSourceDirectory>src/test/scala</testSourceDirectory>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>net.alchim31.maven</groupId>
                <artifactId>scala-maven-plugin</artifactId>
                <version>3.2.1</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>compile</goal>
                            <goal>testCompile</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <!-- disable surefire -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.18.1</version>
                <configuration>
                    <skipTests>true</skipTests>
                </configuration>
            </plugin>
            <!-- enable scalatest -->
            <plugin>
                <groupId>org.scalatest</groupId>
                <artifactId>scalatest-maven-plugin</artifactId>
                <version>1.0</version>
                <configuration>
                    <reportsDirectory>${project.build.directory}/surefire-reports</reportsDirectory>
                    <junitxml>.</junitxml>
                    <stdout>W</stdout>
                    <filereports>WDF TestSuite.txt</filereports>
                </configuration>
                <executions>
                    <execution>
                        <id>test</id>
                        <goals>
                            <goal>test</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

---

This is on a fresh Eclipse install. Before, removing and then adding the scala nature didn't fix the issue. So I tried to reinstall m2e stuff. JDT plugin ended up deleting eclipse binary when I uninstalled it. So I ended up creating everything from scratch.

Internets say it is just a warning, don't pay attention but I'd like to think there is a way to get rid of this warning.

Adding scala-reflect as a maven dependency brings the correct version, but doesn't help with the warning. Also, please note that both Scala IDE and maven are using 2.11.8.

Missing folders should not yield compiler errors

In some projects there can be no src/main/java or src/test/java. This should not generate an error.

Error in Scala compiler: C:\Projects\maven-jee6\behavior-driven-testing\src\test\java does not exist or is not a directory

Importing Tycho test plugin pom

I have developed an Eclipse plugin with separate test plugin in the usual way for Tycho. What I'd like to do is write the tests in Scala (using ScalaTest). However, when I try to import the tests plugin pom with:

<packaging>eclipse-test-plugin</packaging>

then none of the specified Scala source folders are recognized (even the default ones).
If I change the packaging to jar, then everything works correctly.

I can do a mvn clean package from the parent command line and all is fine, including compiling and running ScalaTests.

Any clues on what to do?

XPlugin: configurator does not set compiler plugin property

the following feature is missing:

in order for scala macro compiler plugin to work,
http://docs.scala-lang.org/overviews/macros/paradise.html

1. m2e must look for <compilerPlugin> entries in pom.xml

<compilerPlugins>
  <compilerPlugin>
    <groupId>org.scalamacros</groupId>
    <artifactId>paradise_<YOUR.SCALA.VERSION></artifactId>
    <version>2.0.1</version>
  </compilerPlugin>
</compilerPlugins>

2. resolve them into path in local maven repository
   and place path list as comma separated list into XPlugin scala-ide property per project

prj-liftbased sample in Eclipse Helios

I'm seeing a number of errors using Scala 2.8.0 and Eclipse Helios with the liftbased sample project. It seems to work fine in Galileo with Scala 2.8.0. Is this expected? I'm using the Scala IDE for Helios (nightly build), but not sure if m2eclipse-scala supports Helios yet or not? Note, these are just Eclipse errors. The project builds fine with Maven.

Update Site down ?

Hi,

I'm trying to reach the update site URL to install m2e scala, but it seems to be down. My browser can't navigate to the following urls :

• http://alchim31.free.fr/
• http://alchim31.free.fr/m2e-scala/update-site/

Cheers,
Romain

scala-swing missing from classpath after updating to Scala IDE 4.0.0.m2

After updating to 4.0.0.m2 "scala-swing" has disappeared from the Scala Library container in Eclipse Project

/opt/eclipse-dist/eclipse_scala_4.3/plugins/org.scala-lang.scala-library_2.10.4.v20140209-180020-VFINAL-b66a39653b.jar
/opt/eclipse-dist/eclipse_scala_4.3/plugins/org.scala-lang.scala-reflect_2.10.4.v20140209-180020-VFINAL-b66a39653b.jar
/opt/eclipse-dist/eclipse_scala_4.3/plugins/org.scala-lang.scala-actors_2.10.4.v20140209-180020-VFINAL-b66a39653b.jar

scala-swing is present in the pom but it doesn't get imported in the Maven container (a quick look at the m2e scala source code show that it is removed)

    <dependency>
        <groupId>org.scala-lang</groupId>
        <artifactId>scala-swing</artifactId>
        <version>${scala.version}</version>
        <scope>compile</scope>
    </dependency>

where scala.version=2.10.4

Scala Archetype doesn't show up after installing m2eclipse-scala plugin

Hello

I was able to successfully install the m2eclipse-scala plugin from the available software site: http://alchim31.free.fr/m2e-scala/update-site/

However, when I try to create a new maven project for scala ( as per the instructions mentioned in: http://scala-ide.org/docs/tutorials/m2eclipse/) I can't find the scala archetype in the list of archetypes.

I am attaching the screenshot of the installed software on the IDE for reference.

I am not sure where I am going wrong. Any help would be appreciated, thank you.

WTP war file creation failing

The removal of the scala* libs from the maven classpath container seem to cause WTP war file creations to not put those libs into the WEB-INF/lib folder.

As a workaround, you can add the Scala classpath container manually to the deployment assembly list (project preferences), but it would be much nicer to have those libs being added to the war automatically.

update 0.4.3 -> 0.5.0 breaks m2e 1.5 and 1.6 on eclipse 4.3 and 4.4

description:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=446748

possible reason: pull request #34

unable to reach update site

I'm not able to reach update site at http://alchim31.free.fr/m2e-scala/update-site . can you please let me know if this working or there is a new update site

No notification

Hi Sonatype Team,

I'm the main author of m2eclipse-scala, but I don't receive github notification about the project sonatype / m2eclipse-scala (issue, ...) could you change the configuration.

github Id : davidB

Thanks.

Installing the plugin from local

Hello

I am not able to use the update site due to some problems with my proxy settings. So, I've downloaded the files onto my desktop trying to install the plugin from local. Can you please help me with installing the plugin from local?

Any help is appreciated. Thank you!

Class not found in JUnit java tests for java-scala cycle dependency

Hi,

In sample app "prj-scala-cycle-java" i've added JUnit Java test under src/test/java:

package sample;

import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import static org.junit.Assert.assertTrue;

import org.junit.Test;

import samples.JavaObj;
import samples.ScalaObj;
import samples.UseJavaObj;
import samples.UseScalaObj;

public class JavaTest {

    @Test
    public void testOK() {
        assertTrue(true);
    }

    @Test
    public void testJavaObj() throws Exception {
        assertEquals(33, new JavaObj().doStuff());
    }

    @Test
    public void testUseJavaObj() {
        assertEquals(66, new UseJavaObj().use());
    }

    @Test
    public void testScalaObj() {
        assertEquals(280, new ScalaObj().foo());
    }

    @Test
    public void testUseScalaObj() throws Exception {
        assertEquals(-280, new UseScalaObj().use());
    }

}

And it works great, both eclipse and maven.

Then i've added code to ScalaObj.scala:

package samples

class ScalaObj {
  def foo() = 280

  def xmlTest() = {
    val xml = <foo><bar/></foo>
    (xml \\ "foo").text
  }
}

and new test to JUnit Java tests:

@Test
public void testScalaXml() {
    assertNotNull(new ScalaObj().xmlTest());
}

Test crashes in eclipse. It works in maven, and even in eclipse after maven build. But after "project->clean" it fails again.

Underlying JDK?

Hi David,

I've had the feeling for a long time that the scala-maven-plugin (or something else in the build chain) was doing some strange things. For example, my build on Cloudbees randomly fails and it seems to do so because the underlying JDK is selected randomly (or in a way I fail to understand).

This impression was confirmed recently as Apple (great move, people) decided to force the latest JDK version on everyone:

• my project pom declares 1.6 source and target levels
• my project indeed displays the JDK6 library
• I get some compilation errors in eclipse complaining that some classes extending some Swing classes should be parameterized. Problem is these classes have a type parameter only since... Java 7!
• I finally uninstalled JDK7 from my Mac, and the errors magically disappeared

Any idea?

Cheers,

Stéphane

Mirror down

The update site (http://alchim31.free.fr/m2e-scala/update-site) seems to be down.

Update site unavailable and no download for version 0.4.0

When I try to access the update site (http://alchim31.free.fr/m2e-scala/update-site) the connection hangs and times out. There is also no download for 0.4.0 in the downloads tab.

Finally, building locally (MacOS X) with mvn 3.0.3 gives me an internal maven error currently and I'd really prefer to use the update site.

Scala library should always be placed before Maven dependencies in the project class path

I am using the Scala IDE plugin based on Scala 2.9.0.final toolchain. Some of my Maven projects still use Scala 2.8.1.final.

m2eclipse-scala sometimes place the 'Scala library' before 'Maven dependencies' in the class path, and sometimes after. If placed 'after', build will almost always fail because the toolchain version and the library version differ (i.e. 2.9.0 vs 2.8.1). If placed 'before', build succeeds because code written with Scala 2.8.1 should compile fine with Scala 2.9.0.

Switching back to older Scala IDE plugin is not an option because the one based on 2.8.1.final toolchain is literally 'unusable' in terms of stability.

m2eclipse-scala plugin available in the Scala IDE ecosystem?

Hi guys, would you be interested in making your plugin available in the Scala IDE ecosystem?

You never heard of the Scala IDE ecosystem? The idea is really simple, we want to provide a central locations for plugins relevant for Scala development inside Eclipse. We officially launched the service last week (25th of July), and for the moment it includes the Scala IDE and the ScalaTest plugin. It would be truly great if we could include the m2eclipse-scala plugin!

If you are interested, the process for being included in the ecosystem is really simple (and quick). You can read the details here. And, of course, we can help out. Just drop us a note in the scala-ide-dev ML if needed.

If you want to read a bit more about the Scala IDE ecosystem, here is the blogged article and here is the (rather essential for the moment) page on our website.

Cannot install Maven Integration for Scala IDE 0.4.0

I have Eclipse 3.7.2 with Scala IDE 2.0.1. When I try to install Maven Integration for Scala IDE 0.4.0 from http://alchim31.free.fr/m2e-scala/update-site/ I get the following error message:

An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.maven.ide.eclipse.scala,0.4.0
No repository found containing: org.eclipse.update.feature,org.maven.ide.eclipse.scala_feature,0.4.0

Am I doing something wrong?

m2eclipse-scala does not set scala library container properly

With Eclipse Luna and the Eclipse IDE 4.0 milestone 3, loading maven projects configured to use scala 2.10 does not work. The projects get configured to use scala 2.11.2 as the library container.

This leads to "The version of scala library found in the build path (2.11.2) is incompatible with the one expected by scala IDE (2.10). Please replace the scala library with the scala container or a compatible scala library jar."

Or if -Xsource:2.10 is not present "akka-actor_2.10-2.3.0.jar of rrScalaCommon build path is cross-compiled with an incompatible version of Scala (2.10.0.). In case this report is mistaken, this check can be disabled in the compiler preference page."

The m2e integration for eclipse should:
Set the Scala Library container on a per project basis in accordance with the major version specified in the project pom's scala-library dependency.

This is very obnoxious at the moment, as I will have to manually set the version for 30+ projects.

Post a License

Would you post the license for this project? I would like to use it, but if it is not an open source project I will have to pass. Thanks.

can't push my changes

➜ m2eclipse-scala git:(master) ✗ git push origin master
ERROR: Permission to sonatype/m2eclipse-scala denied to davidB.
fatal: The remote end hung up unexpectedly

Modules dependencies not refreshed when editing parent pom

Upgrade a version in the parent dependencyManagement doesn't upgrade modules dependencies, even when using "Update Project".

The only way I could find to update the modules is to remove them from workspace, remove all .setting, .classpath, .project files and re-import them.

I tested tons of different combinations between eclipse (indigo vs juno), scala IDE (2.0.2 vs nightly), m2e (1.0.2 vs 1.1.0) and it never works properly. The only constant is the m2e-scala-plugin, as only 0.4.1 is available on the update-site.

Error installing plugin with Eclipse Neon?

Hi,

Is this plugin compatible with Eclipse Neon? When I try and install the plugin i get the below error message.

scala-reflect dependency should not be added to .classpath

If I have dependency to scala reflect in my pom file like

<dependency>
  <groupId>org.scala-lang</groupId>
  <artifactId>scala-reflect</artifactId>
  <version>2.10.0</version>
</dependency>

it should be ignored like is scala-library.
It is already presented in Scala Library Container.
Currently it is presented in both Scala Library Container an Maven Dependencies Container.