Problem building on Windows with Maven 3.0.3

[Alec Munro]

Hi group!

First off, thanks for making this available. Looks pretty nifty.

Unfortunately, I can't seem to build it locally. It's been several
years since I have done any serious work with Maven, so that is
probably a factor.

It's unable to resolve the gwt-dnd dependency. I see there's a repo
listed in the POM: http://gwtquery-plugins.googlecode.com/svn/mavenrepo,
but "mvn package" is either ignoring this or having trouble with it,
as it is trying to get gwt-dnd from "central".

Has anyone else hit this?

Thanks,
Alec

[Jim Reardon]

I've not tried to build on windows before, but you could try adding a repo that for-sure has the package.  I think the official distro just started pushing it to a more central location.

http://search.maven.org/#search%7Cga%7C1%7Ccom.allen-sauer.gwt.dnd

Sorry I can't be of much help.  I'm tempted to rip out this dependency because of GWT's built in D&D support but doubt I'll have time to actually do that.

- Jim

[Mike C.]

I ran into a gwt-dnd dependency issue as well. I'm not sure at what
point in the build yours occurred, but my build started barking when
it hit the Maven GWT plugin. The pom.xml doesn't contain a
<pluginRepositories> section which from the looks of it is required
for plugin dependencies. That check does not fall back to the
<repositories> listing. Adding the following to pom.xml resolved the
build complaint.

<pluginRepositories>
<pluginRepository>
<id>has gwt-dnd 3.1.1</id>
<url>http://gwtquery-plugins.googlecode.com/svn/mavenrepo</url>
</pluginRepository>
</pluginRepositories>


Honestly I'm not sure why this worked. I'd imagine it would have been
seen as an issue before. In any case, everything went smoother after
that and I could run a local instance of test-analytics with gae:run.
If this helps someone else, good. If not, well it work for me!

-Mike C.

[Jim Reardon]

So changing the repositories section to pluginRepositories makes this work?  I can hopefully submit a patch to change this if it's a blocker for most people to compile.

- Jim

[Jim Reardon]

I've submitted this change after verifying with it everything still builds for me.  But, I've never experienced this problem, so it'd be great if you could give it a try and see if it solves it for you.

Jim

[Mike C.]

I see that you made the change already. Just to clarify, I did not
replace repositories with pluginRepositories, but simply added that
section. So my pom.xml has:

<repositories>
<repository>

<id>has gwt-dnd 3.1.1</id>
<url>http://gwtquery-plugins.googlecode.com/svn/mavenrepo</url>

</repository>
</repositories>

<pluginRepositories>
<pluginRepository>
<id>has gwt-dnd 3.1.1</id>
<url>http://gwtquery-plugins.googlecode.com/svn/mavenrepo</url>
</pluginRepository>
</pluginRepositories>

However, since that is a plugins link, I'm thinking we don't need the
<repositories> section after all. In any case, the build errors I got
were from not being able to fetch the plugins. This wiki has a good
authoritative description of what I was seeing:

"You are using a third-party Maven plugin that is not deployed to the
central Maven repository and your POM/settings is missing the required
<pluginRepository> to download the plugin. Note that <repository>
declarations are not considered when looking for the plugin and its
dependencies, only <pluginRepositories> are searched for plugins."
https://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

Adding the plugin repo solved my problem, but it would be good to
confirm that is also solves Alec's issue. Perhaps you haven't been
running into the issue because your local repository already contains
those dependencies? I'll be trying to deploy this on an AppScale
server next week. I'll build on a fresh machine and tinker with this.
I'll post back if I notice any issues. Otherwise assume this fixes
what we saw.

-Mike

On Jan 20, 2:11 pm, Jim Reardon <j...@google.com> wrote:
> I've submitted this change after verifying with it everything still builds
> for me.  But, I've never experienced this problem, so it'd be great if you
> could give it a try and see if it solves it for you.
>
> Jim
>
>
>
>
>
>
>
> On Fri, Jan 20, 2012 at 4:43 PM, Jim Reardon <j...@google.com> wrote:
> > So changing the repositories section to pluginRepositories makes this
> > work?  I can hopefully submit a patch to change this if it's a blocker for
> > most people to compile.
>
> >  - Jim
>