[dbscott525]

270 or 680

Staged an update that addresses the POI dependency. New staging URL is

<url>https://oss.sonatype.org/content/repositories/comgooglecodesmartgwt-maven-plugin-270/</url>

I'm a little confused by this. In the first post you wanted us to use the 270 plugin. In a later post you said you had updated it to the 608 plugin. Which on should we used?

[bbruyn]

Should I ignore this if I'm using 3.1P?

Yes, exactly.

[dbscott525]

use a plugin version other than the latest (3.1)?

Could you please explain what you mean by:

//use a plugin version other than the latest (3.1) to be downloaded / installed locally (requires fully qualified group and artifact id)
mvn com.googlecode.smartgwt-maven-plugin:smartgwt-maven-plugin:3.0:install

Should I ignore this if I'm using 3.1P?

[bbruyn]

Actually it appears that your last staging repo and the original are identical

No.

and it does not contain a 4.0 version

I know. Use the snapshot repo.

[jpappalardo]

So the 4.0 version is not in your current staging repo?

Actually it appears that your last staging repo and the original are identical and it does not contain a 4.0 version

Index of /content/repositories/comgooglecodesmartgwt-maven-plugin-270/com/googlecode/smartgwt-maven-plugin/smartgwt-maven-plugin/
Name Last Modified Size Description
Parent Directory
maven-metadata.xml Fri Jan 25 21:53:36 CST 2013 416
maven-metadata.xml.md5 Fri Jan 25 21:53:37 CST 2013 32
maven-metadata.xml.sha1 Fri Jan 25 21:53:36 CST 2013 40
2.5/ Fri Jan 25 21:47:52 CST 2013
3.0/ Fri Jan 25 21:50:00 CST 2013
3.1/ Fri Jan 25 21:53:56 CST 2013

[bbruyn]

Make sure you have the sonatype-snapshots repo defined as in post #1. Then it's the same as before.

mvn com.googlecode.smartgwt-maven-plugin:smartgwt-maven-plugin:4.0-SNAPSHOT:install -Pisc -Dlicense=EVAL

[jpappalardo]

How can I use this to get 4.0 eval?

[bbruyn]

Staged an update that addresses the POI dependency. New staging URL is

<url>https://oss.sonatype.org/content/repositories/comgooglecodesmartgwt-maven-plugin-270/</url>

[bbruyn]

Thanks for the feedback. I see what you mean. I'll probably try to get that sorted over the weekend and publish to staging one more time.

[hanspetter]

First, thank you for your effort.
Then, a note about the optional dependency xbean. I believe that the intended dependency is

		<dependency>
		    <groupId>org.apache.xmlbeans</groupId>
		    <artifactId>xmlbeans</artifactId>
		    <version>2.3.0</version>
		    <optional>true</optional>
		</dependency>

But, since both poi-ooxml-schemas and xmlbeans (and stax-api) is pulled in automaticallt by the poi-ooxml dependency, you really don't need to specify them at all.
Regards
Hans Petter Simonsen - EVRY Norway

[jpappalardo]

How exactly do I update the plugin to the new version?

***Edit***
Never mind, I had to delete the cached version out of artifactory, and then all was fine.

[bbruyn]

Ooof. Thanks for pointing that out. I've staged an update that fixes the fileupload dependency and works around the problem with isc-jakarta-oro by just versioning it along with everything else (e.g., 3.1-p20130116 instead of 2.0.6).

You'll need to change the staging repo to

<url>https://oss.sonatype.org/content/repositories/comgooglecodesmartgwt-maven-plugin-608/</url>

Please give that a try and let me know if you find anything else.

[jpappalardo]

I seem to have found an issue with the plugin.

isc-jakarta-oro installs into the local m2 repo during the install phase, but does not get pushed up to the repository during the deploy phase.

[jpappalardo]

I get it now. I needed to add -Pisc to the command. Will you notify me when you get the core-rpc dependency updated?

[bbruyn]

Yeah, I need to do a better job of validating parameter values. I'll fix all that in the near future.

Meanwhile, it looks like you're missing the 'license' parameter. Check out the settings.xml in the original post.