[bbruyn]

How can I contribute this change?

Hrm, probably the easiest thing for now is to attach your new pom(s) to this thread. I'll get the wiki attachment updated for you.

[futtegud]

I am trying to install a newly purchased Smart GWT Pro using maven 3 with the guide on: http://wiki.smartclient.com/display/Main/Using+Maven+with+SmartGWT

It fails on:
[ERROR] Plugin com.google.code.maven.plugins:maven-http-client-plugin:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.google.code.maven.plugins:maven-http-client-plugin:jar:1.0.0-SNAPSHOT: Failure to find com.google.code.maven.plugins:maven-http-client-plugin:pom:1.0.0-20110216.014446-3 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

As far as I can see on the google code website the only version of this plugin available is "maven-http-client-plugin-1.0.0-beta1" and not "maven-http-client-plugin-1.0.0-SNAPSHOT".

Does anyone have any experience with this setup? Or even experienced this error? I could obviously use some help...

Danny

[bbruyn]

The build should try to get it from https://oss.sonatype.org/content/groups/public.

Seemed like that server was unavailable when I went to double check it a minute ago, but appears to be available now. Try again and let us know if it doesn't get sorted out.

[futtegud]

Unfortunately it still does not work.

It first gives a warning:

[WARNING] The POM for com.google.code.maven.plugins:maven-http-client-plugin:jar:1.0.0-20110216.014446-3 is missing, no dependency information available

and then when the build fails:

[ERROR] Plugin com.google.code.maven.plugins:maven-http-client-plugin:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.google.code.maven.plugins:maven-http-client-plugin:jar:1.0.0-SNAPSHOT: Failure to find com.google.code.maven.plugins:maven-http-client-plugin:pom:1.0.0-20110216.014446-3 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

[bbruyn]

This is a maven thing, and doesn't have anything to do with smartgwt or the mavenizer...

Get rid of the files at ~/.m2/com/google/code/maven/plugins and try again. If you still have trouble, you can of course install that dependency independent of the build.

[futtegud]

I have actually tried this...

If I delete

~/.m2/repository/com/google/code/maven/plugins/maven-http-client-plugin

and try again I first get this warning:

[WARNING] The POM for com.google.code.maven.plugins:maven-http-client-plugin:jar:1.0.0-20110216.014446-3 is missing, no dependency information available

and it fails with:

[ERROR] Plugin com.google.code.maven.plugins:maven-http-client-plugin:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.google.code.maven.plugins:maven-http-client-plugin:jar:1.0.0-SNAPSHOT: Could not find artifact com.google.code.maven.plugins:maven-http-client-plugin:pom:1.0.0-20110216.014446-3 in central (http://repo1.maven.org/maven2) -> [Help 1]

If I run again after this (without deleting the before mentioned folder) I get the error from my previous post... I really have no idea what I have done wrong...

[bbruyn]

This isn't going to be the best place to find maven help. That said, I'll give it one more try.

Do you perhaps have some mirror set up to a corporate repository (e.g., nexus) that's getting in your way? From what you've posted here, it doesn't look like your build is looking in the right place... If so, you'll want to turn that off, reconfigure your mirror, or proxy the sonatype repo from your corporate repo.

Again, if all else fails, you can download the jar and the pom manually and 'mvn install-file' to get the dependency installed before you run the build.

[futtegud]

I have tried it on two separate computers. None of the should have any special settings.

If I look at the repository:
https://oss.sonatype.org/content/groups/public/com/google/code/maven/plugins/maven-http-client-plugin/1.0.0-SNAPSHOT/

there is nothing really to download... or is it just me?

[bbruyn]

You're right, it's gone. I'd swear it was there when I looked yesterday, but that of course doesn't help you now.

You'll have to download the artifacts from the project site and get them installed via mvn install-file. I guess I'll have to update the wiki to include those instructions and the attachments themselves.

[futtegud]

The only problem is that on the project website on google code:
http://code.google.com/p/maven-http-client-plugin/downloads/list

there is only the beta available:
maven-http-client-plugin-1.0.0-beta1.jar
and not
maven-http-client-plugin-1.0.0-SNAPSHOT.jar

Do you know if it is possible to get elsewhere?

[bbruyn]

Well, I'd been hopeful that the beta1 version would work just as well. I just tried it locally though, and no joy.

I'll reach out to the developer of that project and also try to find out what happened on the sonatype repo. Meanwhile, I've added another attachment to the wiki. :-(

[jpappalardo]

How can I change the project such that the nightly pom version would be 3.0.1-SNAPSHOT? That why I can have the nightly builds as snapshots, and the release as a release in my companies repo.

[bbruyn]

Funny you should ask, because I've been thinking that it probably makes sense to align the artifact versions with the new p/d build discriminators anyway. I was thinking of something along the lines of:

smartgwtpower-3.0
smartgwtpower-3.0p.20120127
smartgwtpower-3.1d.20120127-SNAPSHOT

You'd then also probably need to allow a mvn release goal to 'release' the snapshot builds internally, in the event that you wanted to use them in production. e.g., I have some feature sponsorships going that I might need to deploy before a final 3.1 build is available. That result would then of course look something like

smartgwtpower-3.1d.20120127


Sound okay?

[jpappalardo]

I could do without the date, but whatever makes your life easier. I just know that I need the poms version to be xxx-SNAPSHOT to push it up to our snapshot repository, as they dont want release and nightly builds in the same repo. Can I ask what you're sponsoring them for?

[bbruyn]

Can I ask what you're sponsoring them for?

You mean what features have we sponsored? I trust that Isomorphic will edit or delete my post if I shouldn't say in the forum... though this thread is a weird place for it...

We've actually had a few things done. FWIW, we've so far found really good value in the feature sponsorship program. Recommended.

Anyway, current WIP includes:

1. DataSourceLoader automatic dependency loading from client-side load API. Some background on it here:

- special variant of load() that triggers this
- avoids clobbering already-loaded DataSources unless forceReload flag is set

2. direct DataSource i18n (my personal favorite):

- eliminate .jsp approach for DataSource for typical i18n attributes:
title, errorMessage, etc
- ability to specify resource bundle and attribute name, as well as
probably a loading strategy (eg classpath, spring)

3. Enum valueMaps (aka single-field schemaBean):

Property on a DataSource field allows auto-deriving valueMaps from a
Java enum