Failed to resolve artifact with 2.7.0-SNAPSHOT about gwt-maven-plugin HOT 12 CLOSED

Maybe it's linked directly with the GWT2.7.0-SNAPSHOT

from gwt-maven-plugin.

I've tested by using gwt-maven-plugin:2.6.1 and specifying dependencies to GWT 2.7.0-SNAPSHOT. It works fine.

 <plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>gwt-maven-plugin</artifactId>
                    <version>2.6.1</version>
                    <dependencies>
                        <dependency>
                            <groupId>com.google.gwt</groupId>
                            <artifactId>gwt-user</artifactId>
                            <version>2.7.0-SNAPSHOT</version>
                        </dependency>
                        <dependency>
                            <groupId>com.google.gwt</groupId>
                            <artifactId>gwt-dev</artifactId>
                            <version>2.7.0-SNAPSHOT</version>
                        </dependency>
                        <dependency>
                            <groupId>com.google.gwt</groupId>
                            <artifactId>gwt-codeserver</artifactId>
                            <version>2.7.0-SNAPSHOT</version>
                        </dependency>
                    </dependencies>
                    <configuration>
...

from gwt-maven-plugin.

This is a maven bug. Update maven to 3.2.3.

from gwt-maven-plugin.

I guess I should say I got the same error and updated and it got rid of it.

https://github.com/branflake2267/Archetypes/blob/master/archetypes/gwt-basic-snapshot/pom.xml

I formulated a quick test using the BOM import strategy.

mvn archetype:generate \
-DarchetypeRepository=https://oss.sonatype.org/content/repositories/snapshots \
-DarchetypeGroupId=com.github.branflake2267.archetypes \
-DarchetypeArtifactId=gwt-basic-snapshot-archetype \
-DarchetypeVersion=1.0-SNAPSHOT \
-DgroupId=com.projectname.project \
-DartifactId=new-project-name \
-Dmodule=Project

from gwt-maven-plugin.

The real issue is occurring b/c its trying to get org.ow2 from the snapshot repo and should be resolving to the release repo. In this case if the snapshot changes to release, no need for snapshot repo.

from gwt-maven-plugin.

Thanks Brandon, I've updated to the last version of maven and it works fine

from gwt-maven-plugin.

Good to hear, thanks for checking! :)

from gwt-maven-plugin.

Hi,

I have updated to latest version of maven. Still I get same error. Please guide.

Thanks.
P

from gwt-maven-plugin.

what is the maven version mvn -v?

from gwt-maven-plugin.

Hi,

Below has the maven version details,

Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-12T02:28:10+05:30)
Maven home: F:\apache-maven-3.2.5\bin..
Java version: 1.8.0_45, vendor: Oracle Corporation
Java home: C:\Program Files (x86)\Java\jdk1.8.0_45\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"

I also tried with maven 3.3.3, but same error

I m using sprint framework. I understand this issue might be due to asm mismatch. My .m2 (repository) folder contains so many version of asm

3.1
3.2
3.3.1

I m using java version "1.8.0_45"

Help in this regard is highly appreciated. I m trying to upgrade to gwt 2.7 from many days and i m stuck with this error.

Thanks,
P

from gwt-maven-plugin.

Even though I am using the latest version of maven.
i encountered same problem.

mvn -version
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T20:57:37+09:00)
Maven home: /Users/simon/dev/apache-maven-3.3.3
Java version: 1.8.0_60, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
Default locale: ko_KR, platform encoding: UTF-8
OS name: "mac os x", version: "10.11", arch: "x86_64", family: "mac"

from gwt-maven-plugin.

Hi,

I had a same problem and it was resolved by ASM version.

I had issue mainly with older version of ASM and I had difficulty in finding which plugin is downloading the older version of ASM, then I figured it out by using maven --debug mode option, which gives the complete log of which plugin was downloading the older version of ASM. Then, I upgraded those plugin's, then it downloaded new version of ASM and it resolved my issue.

Hope it helps

Thanks,
Preetham.J

from gwt-maven-plugin.