Nabble - mojo - dev

[jira] Created: (MEXEC-71) "mvn exec:java" as described in Ch 4, "Maven: The Definitive Guide", fails for me with error message shown below

2009-11-08T20:19:55Z

"mvn exec:java" as described in Ch 4, "Maven: The Definitive Guide", fails for me with error message shown below
-----------------------------------------------------------------------------------------------------------------

Key: MEXEC-71
URL: http://jira.codehaus.org/browse/MEXEC-71
Project: Maven 2.x Exec Plugin
Issue Type: Bug
Components: exec
Environment: Windows NT, MS-DOS
Reporter: Robert Kruck
Priority: Minor
Attachments: pom.xml_CAN_INSTALL, pom.xml_COPIED

1) I was using the expanded simple-weather pom.xml that was downloaded with the other "Maven: The Definitive Guide", Ch4 example files.

2) I find that I get a successful "simple-weather" mvn install, with simple-weather in the state it is in as of page 47, if I delete the <parent> ... </parent> section of the provided pom.xml that I uploaded along with this Issue.

3) With the <parent> ... </parent> section deleted I can do "mvn install" but now get a complaint about a missing class when running the command

mvn exec:java -Dexec.mainClass=org.sonatype.mavenbook.weather.Main

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An exception occured while executing the Java class. org.sonatype.mavenbook.weather.Main

Caused by: java.lang.ClassNotFoundException: org.sonatype.mavenbook.weather.Main

My current pom.xml file is attached (includes CAN_INSTALL in its name).

The Maven book's CH4 pom.xml, which I downloaded from www.sonatype.org, is also attached. This pom.xml can neither "mvn install" nor "mvn exec:java"

Does anyone have a pom.xml that can be used to do mvn exec:java -Dexec.mainClass=org.sonatype.mavenbook.weather.Main for the "Maven: The Definitive Guide" Chapter 4 example "simple-weather" ?

My java version is: java version "1.6.0_17"

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (MGWT-137) Could not find the main class: com.google.gwt.dev.DevMode

2009-11-08T16:42:55Z

[ http://jira.codehaus.org/browse/MGWT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197652#action_197652 ]

jieryn commented on MGWT-137:
-----------------------------

I'm sorry - are you saying that you can not reproduce the problem?

> Could not find the main class: com.google.gwt.dev.DevMode
> ---------------------------------------------------------
>
> Key: MGWT-137
> URL: http://jira.codehaus.org/browse/MGWT-137
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: jieryn
> Assignee: Olivier Lamy
>
> Using gwt-maven-plugin-1.2-SNAPSHOT (rev 11123) no longer allows gwt:run to work. A couple of revisions ago I was able to use my exact configuration and it was working. I see in MGWT-132 there was a change from dev.HostedMode -> dev.DevMode. I don't think this was tested..
> [INFO] [gwt:compile {execution: default}]
> [INFO] using GWT jars from project dependencies : 2.0.0-ms1
> [INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
> [INFO] establishing classpath list (scope = compile)
> [INFO] com.ibm.isvt.shamrock.gwt.Application is up to date. GWT compilation skipped
> [INFO] [gwt:mergewebxml {execution: default}]
> [INFO] using GWT jars from project dependencies : 2.0.0-ms1
> [INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
> [INFO] 0 servlet(s) merged into /home/jesse/workspace/com.ibm.isvt.shamrock/gwt/ui/target/web.xml
> [INFO] [gwt:run {execution: default-cli}]
> [INFO] using GWT jars from project dependencies : 2.0.0-ms1
> [INFO] establishing classpath list (scope = runtime)
> [INFO] create exploded Jetty webapp in /home/jesse/workspace/com.ibm.isvt.shamrock/gwt/ui/war
> [INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
> [ERROR] Exception in thread "main" java.lang.NoClassDefFoundError: com/google/gwt/dev/DevMode
> [ERROR] Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.DevMode
> [ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> [ERROR] at java.security.AccessController.doPrivileged(Native Method)
> [ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> [ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> [ERROR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> [ERROR] Could not find the main class: com.google.gwt.dev.DevMode. Program will exit.
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> $ svn info
> Path: .
> URL: http://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin
> Repository Root: http://svn.codehaus.org/mojo
> Repository UUID: 52ab4f32-60fc-0310-b215-8acea882cd1b
> Revision: 11123
> Node Kind: directory
> Schedule: normal
> Last Changed Author: olamy
> Last Changed Rev: 11104
> Last Changed Date: 2009-11-06 12:20:06 -0500 (Fri, 06 Nov 2009)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Assigned: (MGWT-137) Could not find the main class: com.google.gwt.dev.DevMode

2009-11-08T16:23:55Z

[ http://jira.codehaus.org/browse/MGWT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reassigned MGWT-137:
---------------------------------

Assignee: Olivier Lamy

[jira] Commented: (MGWT-137) Could not find the main class: com.google.gwt.dev.DevMode

2009-11-08T16:23:55Z

[ http://jira.codehaus.org/browse/MGWT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197650#action_197650 ]

Olivier Lamy commented on MGWT-137:
-----------------------------------

I have tested with 2.0.0-ms2

[jira] Commented: (MGWT-137) Could not find the main class: com.google.gwt.dev.DevMode

2009-11-08T15:15:55Z

[ http://jira.codehaus.org/browse/MGWT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197649#action_197649 ]

jieryn commented on MGWT-137:
-----------------------------

I fall back to r10938, and everything works again..

> Could not find the main class: com.google.gwt.dev.DevMode
> ---------------------------------------------------------
>
> Key: MGWT-137
> URL: http://jira.codehaus.org/browse/MGWT-137
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: jieryn
>
> Using gwt-maven-plugin-1.2-SNAPSHOT (rev 11123) no longer allows gwt:run to work. A couple of revisions ago I was able to use my exact configuration and it was working. I see in MGWT-132 there was a change from dev.HostedMode -> dev.DevMode. I don't think this was tested..
> [INFO] [gwt:compile {execution: default}]
> [INFO] using GWT jars from project dependencies : 2.0.0-ms1
> [INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
> [INFO] establishing classpath list (scope = compile)
> [INFO] com.ibm.isvt.shamrock.gwt.Application is up to date. GWT compilation skipped
> [INFO] [gwt:mergewebxml {execution: default}]
> [INFO] using GWT jars from project dependencies : 2.0.0-ms1
> [INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
> [INFO] 0 servlet(s) merged into /home/jesse/workspace/com.ibm.isvt.shamrock/gwt/ui/target/web.xml
> [INFO] [gwt:run {execution: default-cli}]
> [INFO] using GWT jars from project dependencies : 2.0.0-ms1
> [INFO] establishing classpath list (scope = runtime)
> [INFO] create exploded Jetty webapp in /home/jesse/workspace/com.ibm.isvt.shamrock/gwt/ui/war
> [INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
> [ERROR] Exception in thread "main" java.lang.NoClassDefFoundError: com/google/gwt/dev/DevMode
> [ERROR] Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.DevMode
> [ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> [ERROR] at java.security.AccessController.doPrivileged(Native Method)
> [ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> [ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> [ERROR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> [ERROR] Could not find the main class: com.google.gwt.dev.DevMode. Program will exit.
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> $ svn info
> Path: .
> URL: http://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin
> Repository Root: http://svn.codehaus.org/mojo
> Repository UUID: 52ab4f32-60fc-0310-b215-8acea882cd1b
> Revision: 11123
> Node Kind: directory
> Schedule: normal
> Last Changed Author: olamy
> Last Changed Rev: 11104
> Last Changed Date: 2009-11-06 12:20:06 -0500 (Fri, 06 Nov 2009)

[jira] Created: (MGWT-137) Could not find the main class: com.google.gwt.dev.DevMode

2009-11-08T14:58:55Z

Could not find the main class: com.google.gwt.dev.DevMode
---------------------------------------------------------

Key: MGWT-137
URL: http://jira.codehaus.org/browse/MGWT-137
Project: Maven 2.x GWT Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: jieryn

Using gwt-maven-plugin-1.2-SNAPSHOT (rev 11123) no longer allows gwt:run to work. A couple of revisions ago I was able to use my exact configuration and it was working. I see in MGWT-132 there was a change from dev.HostedMode -> dev.DevMode. I don't think this was tested..

[INFO] [gwt:compile {execution: default}]
[INFO] using GWT jars from project dependencies : 2.0.0-ms1
[INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
[INFO] establishing classpath list (scope = compile)
[INFO] com.ibm.isvt.shamrock.gwt.Application is up to date. GWT compilation skipped
[INFO] [gwt:mergewebxml {execution: default}]
[INFO] using GWT jars from project dependencies : 2.0.0-ms1
[INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
[INFO] 0 servlet(s) merged into /home/jesse/workspace/com.ibm.isvt.shamrock/gwt/ui/target/web.xml
[INFO] [gwt:run {execution: default-cli}]
[INFO] using GWT jars from project dependencies : 2.0.0-ms1
[INFO] establishing classpath list (scope = runtime)
[INFO] create exploded Jetty webapp in /home/jesse/workspace/com.ibm.isvt.shamrock/gwt/ui/war
[INFO] auto discovered modules [com.ibm.isvt.shamrock.gwt.Application]
[ERROR] Exception in thread "main" java.lang.NoClassDefFoundError: com/google/gwt/dev/DevMode
[ERROR] Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.DevMode
[ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
[ERROR] at java.security.AccessController.doPrivileged(Native Method)
[ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
[ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
[ERROR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
[ERROR] Could not find the main class: com.google.gwt.dev.DevMode. Program will exit.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------

$ svn info
Path: .
URL: http://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin
Repository Root: http://svn.codehaus.org/mojo
Repository UUID: 52ab4f32-60fc-0310-b215-8acea882cd1b
Revision: 11123
Node Kind: directory
Schedule: normal
Last Changed Author: olamy
Last Changed Rev: 11104
Last Changed Date: 2009-11-06 12:20:06 -0500 (Fri, 06 Nov 2009)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[VOTE] Release animal-sniffer-maven-plugin version 1.3

2009-11-08T11:11:21Z

Folks,

I have put as much effort into getting animal-sniffer ready for a
release as I think I can take. I need a break from it and I think it
is ready to be released.

This is the first release of animal-sniffer and its related projects
from the mojo project. The animal-sniffer is designed to generate
sigantures of APIs and to check java classes against those signatures.
It includes

* a CLI utility for reporting the Java version used to compile java classes

* A set of ANT Tasks for generating and checking API signatures

* A Maven Enforcer Rule for checking API signatures

* A Maven plugin to generating and checking API signatures

* A Java 1.5+ annotation for marking code which safely references
classes from newer APIs

We cannot release any signatures until we have released the
animal-sniffer-maven-plugin.

The new sites have just been deployed here:
http://mojo.codehaus.org/animal-sniffer-maven-plugin
http://mojo.codehaus.org/animal-sniffer
http://mojo.codehaus.org/animal-sniffer/animal-sniffer
http://mojo.codehaus.org/animal-sniffer/animal-sniffer-annotations
http://mojo.codehaus.org/animal-sniffer/animal-sniffer-enforcer-rule
http://mojo.codehaus.org/animal-sniffer/animal-sniffer-ant-tasks
http://mojo.codehaus.org/animal-sniffer/java-boot-classpath-detector

Snapshot have been published on
http://snapshots.repository.codehaus.org/org/codehaus/mojo/anima-sniffer-maven-plugin

This vote will be open for 72 hours and will use lazy consensus.

[+1] release it
[0] don't care
[-1] don't release!

Thanks,

Stephen

P.S.

Here is my +1

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [VOTE] Promote dita-maven-plugin out of sanbox and cut the first beta release

2009-11-08T09:41:13Z

Hi Benjamin,

Thank you so much for this review.

I will get the fixes in quickly

-Dan

On Sun, Nov 8, 2009 at 6:08 AM, Benjamin Bentmann
<benjamin.bentmann@...> wrote:

> Dan Tran wrote:
>
>> I would like to promote dita-maven-plugin out of sandbox and cut the
>> first beta release.
>
> +0, notes:
>
> In case you intend to do the promotion and release in one go, be sure to
> update the SVN references and plugin version on the site as well.
>
> The default value for the skip parameter [0] should likely be "false"
> instead of "${false}". Also, the since version of this parameter is
> 1.0-alpha-1, shouldn't that be beta-1?
>
> The project parameter [1] should be annotated with "@readonly".
>
> mvn dependency:analyze reports undeclared dependencies.
>
> The dependency org.codehaus.mojo:truezip-maven-plugin is declared twice.
>
> scm/developerConnection points at an invalid URL.
>
> The file AntOutputConsumer.java has no license header.
>
> The parameter antProperties [2] is annotated with "@since since ...", note
> the superfluos/duplicate "since". Same applies for many parameters of
> dita:run.
>
> Mojo parameters with expression="${project.*}" should better use
> default-value="${project.*}" to query the POM data.
>
>
> Benjamin
>
>
> [0] http://mojo.codehaus.org/dita-maven-plugin/chm2web-mojo.html#skip
> [1] http://mojo.codehaus.org/dita-maven-plugin/chm2web-mojo.html#project
> [2]
> http://mojo.codehaus.org/dita-maven-plugin/version-mojo.html#antProperties
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [VOTE][RESULT] Release JBoss Maven Plugin version 1.4

2009-11-08T07:40:01Z

The vote has passed with the following results.

+1: Stephen Connolly, Paul Gier

I will proceed with the release.

Paul Gier wrote:

> Hi,
>
> This release has improvements to several of the mojos. Specifically
> improvements to make configuration easier and more flexible. The site
> documentation has also been improved quite a bit, and the code has been
> reformatted to fit the Maven standards.
>
> We solved 13 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11217&version=15401
>
>
> There is still one issue left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MJBOSS+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>
>
> A snapshot is available at
> http://snapshots.repository.codehaus.org/org/codehaus/mojo/jboss-maven-plugin/1.4-SNAPSHOT
>
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Thanks!
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [VOTE] Promote dita-maven-plugin out of sanbox and cut the first beta release

2009-11-08T06:08:26Z

Dan Tran wrote:

> I would like to promote dita-maven-plugin out of sandbox and cut the
> first beta release.

+0, notes:

In case you intend to do the promotion and release in one go, be sure to
update the SVN references and plugin version on the site as well.

The default value for the skip parameter [0] should likely be "false"
instead of "${false}". Also, the since version of this parameter is
1.0-alpha-1, shouldn't that be beta-1?

The project parameter [1] should be annotated with "@readonly".

mvn dependency:analyze reports undeclared dependencies.

The dependency org.codehaus.mojo:truezip-maven-plugin is declared twice.

scm/developerConnection points at an invalid URL.

The file AntOutputConsumer.java has no license header.

The parameter antProperties [2] is annotated with "@since since ...",
note the superfluos/duplicate "since". Same applies for many parameters
of dita:run.

Mojo parameters with expression="${project.*}" should better use
default-value="${project.*}" to query the POM data.

Benjamin

[0] http://mojo.codehaus.org/dita-maven-plugin/chm2web-mojo.html#skip
[1] http://mojo.codehaus.org/dita-maven-plugin/chm2web-mojo.html#project
[2]
http://mojo.codehaus.org/dita-maven-plugin/version-mojo.html#antProperties

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[VOTE] Promote dita-maven-plugin out of sanbox and cut the first beta release

2009-11-08T00:15:02Z

Hi Mojo team,

I would like to promote dita-maven-plugin out of sandbox and cut the
first beta release.

Snapshot has been deployed and

the site is at http://mojo.codehaus.org/dita-maven-plugin

The vote is open for 72 hours and will succeed by lazy consensus.

Please vote

Thanks

-Dan

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Created: (MOJO-1453) xml-maven-plugin:transform - "Premature end of file" when overwriting.

2009-11-06T22:27:55Z

xml-maven-plugin:transform - "Premature end of file" when overwriting.
----------------------------------------------------------------------

Key: MOJO-1453
URL: http://jira.codehaus.org/browse/MOJO-1453
Project: Mojo
Issue Type: Bug
Components: xml
Environment: Maven 2.2.1
Reporter: Ondrej Zizka
Assignee: Jochen Wiedmann

When the resulting file is the same as being transformed, the XML plugin throws an exception and leaves the file empty (0 bytes long).

[INFO] [xml:transform {execution: switch-web.xml}]
[INFO] Transforming file: .../target/war/work/org.jboss.jopr/jopr-embedded-jbas5/WEB-INF/web.xml
CHYBA: 'Premature end of file.'
CHYBA: 'com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Premature end of file.'

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (MOJO-1363) IO exception when the result file already exists

2009-11-06T22:23:55Z

[ http://jira.codehaus.org/browse/MOJO-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197541#action_197541 ]

Ondrej Zizka commented on MOJO-1363:
------------------------------------

Thanks for fixing.

XML plugin has another problem:

[INFO] [xml:transform {execution: switch-web.xml}]
[INFO] Transforming file: .../target/war/work/org.jboss.jopr/jopr-embedded-jbas5/WEB-INF/web.xml
CHYBA: 'Premature end of file.'
CHYBA: 'com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Premature end of file.'

> IO exception when the result file already exists
> ------------------------------------------------
>
> Key: MOJO-1363
> URL: http://jira.codehaus.org/browse/MOJO-1363
> Project: Mojo
> Issue Type: Bug
> Components: xslt
> Reporter: Ondrej Zizka
>
> If the target file already exists, XSLT plugin throws an exception.
> There should be an option to overwrite existing files.
> How to test:
> 1) Set up some project to transform some XML. Put the config into <project><build>, to be able to run it using `mvn xslt:transform`.
> 2) Now run it twice: `mvn xslt:transform`. You will see that the second time, XSLT plugin will throw an exception saying "Unexpected end of file".

[jira] Closed: (MGWT-135) -style parameter not supported on new trunk GWT version (r6727)

2009-11-06T14:23:55Z

[ http://jira.codehaus.org/browse/MGWT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MGWT-135.
-----------------------------

Resolution: Fixed
Fix Version/s: 1.2

> -style parameter not supported on new trunk GWT version (r6727)
> ---------------------------------------------------------------
>
> Key: MGWT-135
> URL: http://jira.codehaus.org/browse/MGWT-135
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: the latest snapshot version of the gwt-maven-plugin from svn (r11099)
> the latest GWT trunk version (r6727)
> opensuse linux
> Reporter: stole
> Assignee: Olivier Lamy
> Fix For: 1.2
>
>
> The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
> I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java
> {code}
> public void doExecute( GwtRuntime runtime )
> throws MojoExecutionException, MojoFailureException
> {
> String clazz = runtime.getVersion().getShellFQCN();
> JavaCommand cmd = new JavaCommand( clazz, runtime )
> .withinScope( Artifact.SCOPE_RUNTIME )
> .arg( runtime.getVersion().getWebOutputArgument() )
> .arg( quote( hostedWebapp.getAbsolutePath() ) )
> .arg( "-gen" )
> .arg( quote( getGen().getAbsolutePath() ) )
> .arg( "-logLevel" )
> .arg( getLogLevel() )
> //The following lines generate the -style arguments that the new DevMode will not swallow
> //.arg( "-style" )
> //.arg( getStyle() )
> .arg( "-port" )
> .arg( Integer.toString( getPort() ) )
> .arg( noServer, "-noserver" );
> ...
> }
> {code}
> I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

[jira] Commented: (MGWT-135) -style parameter not supported on new trunk GWT version (r6727)

2009-11-06T14:20:55Z

[ http://jira.codehaus.org/browse/MGWT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197529#action_197529 ]

stole commented on MGWT-135:
----------------------------

Now it works. Thanks for the quick fix ;).

> -style parameter not supported on new trunk GWT version (r6727)
> ---------------------------------------------------------------
>
> Key: MGWT-135
> URL: http://jira.codehaus.org/browse/MGWT-135
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: the latest snapshot version of the gwt-maven-plugin from svn (r11099)
> the latest GWT trunk version (r6727)
> opensuse linux
> Reporter: stole
> Assignee: Olivier Lamy
>
> The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
> I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java
> {code}
> public void doExecute( GwtRuntime runtime )
> throws MojoExecutionException, MojoFailureException
> {
> String clazz = runtime.getVersion().getShellFQCN();
> JavaCommand cmd = new JavaCommand( clazz, runtime )
> .withinScope( Artifact.SCOPE_RUNTIME )
> .arg( runtime.getVersion().getWebOutputArgument() )
> .arg( quote( hostedWebapp.getAbsolutePath() ) )
> .arg( "-gen" )
> .arg( quote( getGen().getAbsolutePath() ) )
> .arg( "-logLevel" )
> .arg( getLogLevel() )
> //The following lines generate the -style arguments that the new DevMode will not swallow
> //.arg( "-style" )
> //.arg( getStyle() )
> .arg( "-port" )
> .arg( Integer.toString( getPort() ) )
> .arg( noServer, "-noserver" );
> ...
> }
> {code}
> I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

[ANN] Maven JAXB 2.1 Plugin 1.3 Released

2009-11-06T13:34:34Z

The Mojo team is pleased to announce the release of the JAXB 2.1 Plugin, version 1.3.

This plugin is able to create the object graph from XSDs or DTDs based on the JAXB 2.1 implementation.
With this release it's also possible create a schemafile for sources.

See the plugin's site for more details:
http://mojo.codehaus.org/jaxb2-maven-plugin

To use the updated plugin in your projects, you need to add the
following snippet to the plugins or plugin management section of your POM:

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>1.3</version>
<executions>
...
</executions>
</plugin>

Release Notes - Maven 2.x JAXB 2.1 Plugin - Version 1.3

Bug

[MJAXB-2] - cowardly refuses to write to a non-existent directory exception when there are many executions of the plugin
[MJAXB-17] - Filter out directories when collecting schema and binding files
[MJAXB-28] - Plugin site shows incorrect issue tracking URL

Improvement

[MJAXB-13] - add generated date to staleFile
[MJAXB-14] - Support generation from DTDs
[MJAXB-15] - jaxb2-maven-plugin: support for URLs
[MJAXB-16] - Update dependencies to JAXB 2.1.11
[MJAXB-18] - Use Plexus FileUtils.copyURLToFile(URL, File) instead of hand-written code
[MJAXB-19] - Use StringBuilder instead of StringBuffer to avoid unnecessary synchronization
[MJAXB-21] - Show system ID in error output if public ID is unavailable

New Feature

[MJAXB-11] - Add schemagen goal

Enjoy,

-The Mojo team

Express yourself instantly with MSN Messenger! MSN Messenger

[jira] Created: (MBUILDHELPER-17) If the project version contains an incremental version, the parsedVersion information is all zeroes.

2009-11-06T10:06:55Z

If the project version contains an incremental version, the parsedVersion information is all zeroes.
----------------------------------------------------------------------------------------------------

Key: MBUILDHELPER-17
URL: http://jira.codehaus.org/browse/MBUILDHELPER-17
Project: Maven 2.x Build Helper Plugin
Issue Type: Bug
Affects Versions: 1.4
Reporter: Edward Campbell

If you have an artifact version <version>2.0.017-SNAPSHOT</version>
the parsedVersion information will all be set to zero. i.e. parsedVersion.majorVersion = 0 ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (MGWT-135) -style parameter not supported on new trunk GWT version (r6727)

2009-11-06T09:52:55Z

[ http://jira.codehaus.org/browse/MGWT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197504#action_197504 ]

Olivier Lamy commented on MGWT-135:
-----------------------------------

fix committed in [rev 11104|http://fisheye.codehaus.org/changelog/mojo/?cs=11104]
SNAPSHOT deployed.
Can you test it ? (I don't have this gwt version here)
Thanks !

> -style parameter not supported on new trunk GWT version (r6727)
> ---------------------------------------------------------------
>
> Key: MGWT-135
> URL: http://jira.codehaus.org/browse/MGWT-135
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: the latest snapshot version of the gwt-maven-plugin from svn (r11099)
> the latest GWT trunk version (r6727)
> opensuse linux
> Reporter: stole
> Assignee: Olivier Lamy
>
> The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
> I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java
> {code}
> public void doExecute( GwtRuntime runtime )
> throws MojoExecutionException, MojoFailureException
> {
> String clazz = runtime.getVersion().getShellFQCN();
> JavaCommand cmd = new JavaCommand( clazz, runtime )
> .withinScope( Artifact.SCOPE_RUNTIME )
> .arg( runtime.getVersion().getWebOutputArgument() )
> .arg( quote( hostedWebapp.getAbsolutePath() ) )
> .arg( "-gen" )
> .arg( quote( getGen().getAbsolutePath() ) )
> .arg( "-logLevel" )
> .arg( getLogLevel() )
> //The following lines generate the -style arguments that the new DevMode will not swallow
> //.arg( "-style" )
> //.arg( getStyle() )
> .arg( "-port" )
> .arg( Integer.toString( getPort() ) )
> .arg( noServer, "-noserver" );
> ...
> }
> {code}
> I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

[jira] Updated: (MGWT-135) -style parameter not supported on new trunk GWT version (r6727)

2009-11-06T09:15:55Z

[ http://jira.codehaus.org/browse/MGWT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MGWT-135:
------------------------------

Description:
The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java
{code}
public void doExecute( GwtRuntime runtime )
throws MojoExecutionException, MojoFailureException
{
String clazz = runtime.getVersion().getShellFQCN();
JavaCommand cmd = new JavaCommand( clazz, runtime )
.withinScope( Artifact.SCOPE_RUNTIME )
.arg( runtime.getVersion().getWebOutputArgument() )
.arg( quote( hostedWebapp.getAbsolutePath() ) )
.arg( "-gen" )
.arg( quote( getGen().getAbsolutePath() ) )
.arg( "-logLevel" )
.arg( getLogLevel() )
//The following lines generate the -style arguments that the new DevMode will not swallow
//.arg( "-style" )
//.arg( getStyle() )
.arg( "-port" )
.arg( Integer.toString( getPort() ) )
.arg( noServer, "-noserver" );

...
}
{code}
I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

was:
The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java

public void doExecute( GwtRuntime runtime )
throws MojoExecutionException, MojoFailureException
{
String clazz = runtime.getVersion().getShellFQCN();
JavaCommand cmd = new JavaCommand( clazz, runtime )
.withinScope( Artifact.SCOPE_RUNTIME )
.arg( runtime.getVersion().getWebOutputArgument() )
.arg( quote( hostedWebapp.getAbsolutePath() ) )
.arg( "-gen" )
.arg( quote( getGen().getAbsolutePath() ) )
.arg( "-logLevel" )
.arg( getLogLevel() )
//The following lines generate the -style arguments that the new DevMode will not swallow
//.arg( "-style" )
//.arg( getStyle() )
.arg( "-port" )
.arg( Integer.toString( getPort() ) )
.arg( noServer, "-noserver" );

...
}

I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

> -style parameter not supported on new trunk GWT version (r6727)
> ---------------------------------------------------------------
>
> Key: MGWT-135
> URL: http://jira.codehaus.org/browse/MGWT-135
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: the latest snapshot version of the gwt-maven-plugin from svn (r11099)
> the latest GWT trunk version (r6727)
> opensuse linux
> Reporter: stole
> Assignee: Olivier Lamy
>
> The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
> I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java
> {code}
> public void doExecute( GwtRuntime runtime )
> throws MojoExecutionException, MojoFailureException
> {
> String clazz = runtime.getVersion().getShellFQCN();
> JavaCommand cmd = new JavaCommand( clazz, runtime )
> .withinScope( Artifact.SCOPE_RUNTIME )
> .arg( runtime.getVersion().getWebOutputArgument() )
> .arg( quote( hostedWebapp.getAbsolutePath() ) )
> .arg( "-gen" )
> .arg( quote( getGen().getAbsolutePath() ) )
> .arg( "-logLevel" )
> .arg( getLogLevel() )
> //The following lines generate the -style arguments that the new DevMode will not swallow
> //.arg( "-style" )
> //.arg( getStyle() )
> .arg( "-port" )
> .arg( Integer.toString( getPort() ) )
> .arg( noServer, "-noserver" );
> ...
> }
> {code}
> I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

Re: [VOTE] Moving dbunit-maven-plugin to DBUnit at sourceforge and change license from MIT to LPGL

2009-11-06T08:00:03Z

Yes, I will update the site to forward user to the new site

retire current dbunit-maven-plugin SVN folder

drop dbunit component from MOJO @ codehaus jira

-Dan

On Fri, Nov 6, 2009 at 2:19 AM, <david@...> wrote:

> On Thu, 5 Nov 2009, Dan Tran wrote:
>
>> No objection,
>>
>> The dbunit team will move it to sourceforge and change license to LPGL
>>
>> Thanks Nicolas for the vote.
>
> Will code be moved to the retired tree?
> And should we put in a note in http://mojo.codehaus.org/plugins.html about
> the new location?
> Probably the jira project should be dropped as well?
>
>
> --
> David J. M. Karlsen - +47 90 68 22 43
> http://www.davidkarlsen.com
> http://mp3.davidkarlsen.com
> Sent from my bog-standard SMTP client
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Created: (MGWT-136) Support running GWTTestCase tests in web-mode

2009-11-06T06:52:55Z

Support running GWTTestCase tests in web-mode
---------------------------------------------

Key: MGWT-136
URL: http://jira.codehaus.org/browse/MGWT-136
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Affects Versions: 1.2
Reporter: Jamie Gennis
Priority: Minor
Attachments: webmode-test-2009-11-06.patch

The attached patch ('webmode-test-2009-11-06.patch') enables running GWTTestCase's in web-mode by passing the "-web" argument to GWT via the gwt.args property when the webMode Maven config parameter is set to true.

The patch also fixes an issue where the "-out <dir>" argument wasn't getting sent to GWT, which seems to have gotten dropped as part of the transition from org.codehaus.mojo.gwt.test.TestMojo -> org.codehaus.mojo.gwt.shell.TestMojo.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Assigned: (MGWT-135) -style parameter not supported on new trunk GWT version (r6727)

2009-11-06T04:06:55Z

[ http://jira.codehaus.org/browse/MGWT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reassigned MGWT-135:
---------------------------------

Assignee: Olivier Lamy

> -style parameter not supported on new trunk GWT version (r6727)
> ---------------------------------------------------------------
>
> Key: MGWT-135
> URL: http://jira.codehaus.org/browse/MGWT-135
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: the latest snapshot version of the gwt-maven-plugin from svn (r11099)
> the latest GWT trunk version (r6727)
> opensuse linux
> Reporter: stole
> Assignee: Olivier Lamy
>
> The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
> I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java
> public void doExecute( GwtRuntime runtime )
> throws MojoExecutionException, MojoFailureException
> {
> String clazz = runtime.getVersion().getShellFQCN();
> JavaCommand cmd = new JavaCommand( clazz, runtime )
> .withinScope( Artifact.SCOPE_RUNTIME )
> .arg( runtime.getVersion().getWebOutputArgument() )
> .arg( quote( hostedWebapp.getAbsolutePath() ) )
> .arg( "-gen" )
> .arg( quote( getGen().getAbsolutePath() ) )
> .arg( "-logLevel" )
> .arg( getLogLevel() )
> //The following lines generate the -style arguments that the new DevMode will not swallow
> //.arg( "-style" )
> //.arg( getStyle() )
> .arg( "-port" )
> .arg( Integer.toString( getPort() ) )
> .arg( noServer, "-noserver" );
> ...
> }
> I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

[jira] Created: (MGWT-135) -style parameter not supported on new trunk GWT version (r6727)

2009-11-06T02:35:55Z

-style parameter not supported on new trunk GWT version (r6727)
---------------------------------------------------------------

Key: MGWT-135
URL: http://jira.codehaus.org/browse/MGWT-135
Project: Maven 2.x GWT Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: the latest snapshot version of the gwt-maven-plugin from svn (r11099)
the latest GWT trunk version (r6727)
opensuse linux
Reporter: stole

The new (soon to be 2.0) version of GWT has apparently dropped the support for the -style parameter in the com.google.gwt.dev.DevMode shell class. Since the plugin always creates this parameter when it starts the DevMode server it refuses to start with "Unknown argument: -style" error.
I located the faulting lines in /src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java

public void doExecute( GwtRuntime runtime )
throws MojoExecutionException, MojoFailureException
{
String clazz = runtime.getVersion().getShellFQCN();
JavaCommand cmd = new JavaCommand( clazz, runtime )
.withinScope( Artifact.SCOPE_RUNTIME )
.arg( runtime.getVersion().getWebOutputArgument() )
.arg( quote( hostedWebapp.getAbsolutePath() ) )
.arg( "-gen" )
.arg( quote( getGen().getAbsolutePath() ) )
.arg( "-logLevel" )
.arg( getLogLevel() )
//The following lines generate the -style arguments that the new DevMode will not swallow
//.arg( "-style" )
//.arg( getStyle() )
.arg( "-port" )
.arg( Integer.toString( getPort() ) )
.arg( noServer, "-noserver" );

...
}

I commented out the lines just to keep working with the new version but i think that it should be fixed using the GWT version or something but I do not know how. Please contact me if you need some further explanation.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [VOTE] Moving dbunit-maven-plugin to DBUnit at sourceforge and change license from MIT to LPGL

2009-11-06T02:19:41Z

On Thu, 5 Nov 2009, Dan Tran wrote:

> No objection,
>
> The dbunit team will move it to sourceforge and change license to LPGL
>
> Thanks Nicolas for the vote.

Will code be moved to the retired tree?
And should we put in a note in http://mojo.codehaus.org/plugins.html about
the new location?
Probably the jira project should be dropped as well?

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Sent from my bog-standard SMTP client

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

http://www.davidkarlsen.com

Re: [VOTE] Moving dbunit-maven-plugin to DBUnit at sourceforge and change license from MIT to LPGL

2009-11-05T19:09:33Z

No objection,

The dbunit team will move it to sourceforge and change license to LPGL

Thanks Nicolas for the vote.

-Dan

On Sun, Nov 1, 2009 at 12:37 AM, nicolas de loof
<nicolas.deloof@...> wrote:

> +1
>
> 2009/10/31 Dan Tran <dantran@...>
>>
>> Hi MOJO team,
>>
>> The DBUnit team is now actively pursuing the move and also request for
>> license change
>>
>>
>> The vote is open for 72 hours and will succeed by lazy consensus.
>>
>>
>> +1 from me
>>
>> -Dan
>>
>> ---------- Forwarded message ----------
>> From: Raphaël Piéroni <raphaelpieroni@...>
>> Date: 2008/11/6
>> Subject: Re: [mojo-dev] Moving dbunit-maven-plugin to DBUnit at
>> sourceforge
>> To: dev@...
>>
>>
>> +0 i don't use this plugin yet
>>
>> Raphaël
>>
>> 2008/11/3 Benjamin Bentmann <benjamin.bentmann@...>:
>> > Dan Tran wrote:
>> >
>> >> I think it is best to move it to the right knowledge.
>> >
>> > Sure, as long as the other side is really willing to maintain the Maven
>> > code.
>> >
>> >> However current DBUnit's license is LPGL. Is that a problem?
>> >
>> > No idea. Where are those lawyers when one is needed ;-) ?
>> >
>> >> +1 from me
>> >
>> > +1, who would argue with the plugin's main committer ;-)
>> >
>> >
>> > Benjamin
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe from this list, please visit:
>> >
>> > http://xircles.codehaus.org/manage_email
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (MWAS-56) allow ability when deploying to map to HTTP server and application server for module

2009-11-05T15:07:55Z

[ http://jira.codehaus.org/browse/MWAS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197418#action_197418 ]

Josh Joy commented on MWAS-56:
------------------------------

Yup, this is really nice description
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rxml_taskoptions.html

It also demonstrates how to use the "+" syntax to bind to multiple servers.

In regards to tests, I looked thru the project code, though I can't think of a nice way to have Integration tests since it requires an IBM HTTP server to bind to.... do you have any suggestions?

I can say though we have been using this patch for the past 3 weeks with no issues :)

Heres a sample of how I've configured it for our server. I have a generic deploy script to be able to plugin in artifact information, then pass that to the plugin. I use maven-dependency-plugin to get the artifact from our company repository.

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy</id>
<phase>compile</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>${deployable.groupId}</groupId>
<artifactId>${deployable.artifactId}</artifactId>
<version>${deployable.artifactid.version}</version>
<type>${deployable.type}</type>
<overWrite>true</overWrite>
<destFileName>deploy.ear</destFileName>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>was6-maven-plugin</artifactId>
<version>1.2-SNAPSHOT</version>
<executions>
<execution>
<id>integration-test</id>
<phase>integration-test</phase>
<goals>
<goal>wsDefaultBindings</goal>
<goal>wsUninstallApp</goal>
<goal>installApp</goal>
<goal>wsStartApp</goal>
</goals>
</execution>
</executions>
<configuration>
<was6.virtualHost>default_host</was6.virtualHost>
<verbose>true</verbose>
<wasHome>${was6.home}</wasHome>
<host>${was6.host}</host>
<port>${was6.port}</port>
<conntype>SOAP</conntype>
<earFile>${project.build.outputDirectory}/../dependency/deploy.ear</earFile>
<applicationName>${deployable.artifactId}</applicationName>
<updateExisting>false</updateExisting>
<was6.mapModulesToServers>{"Examples Application" examples.war,WEB-INF\web.xml WebSphere:cell=mycell,node=mynode,server=server2+WebSphere:cell=mycell,node=yournode,server=server1}}</was6.mapModulesToServers>
</configuration>
</plugin>

> allow ability when deploying to map to HTTP server and application server for module
> -------------------------------------------------------------------------------------
>
> Key: MWAS-56
> URL: http://jira.codehaus.org/browse/MWAS-56
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Improvement
> Affects Versions: 1.2
> Environment: when using IBM HTTP Server
> Reporter: Josh Joy
> Assignee: David J. M. Karlsen
> Attachments: wasv6-maven-plugin.txt
>
>
> when using IBM HTTP Server, there is a Websphere option in the Admin console "Map modules to servers". If IBM HTTP Server is setup and configured, there is an option to bind to both HTTP Server and the application server. The Websphere option is "-MapModulesToServers". This patch provides another configuration parameter to the plugin "mapModulesToServers".
> For example, to use it
> <configuration>
> ....
> <was6.mapModulesToServers>{{SOMEWEB SOMEWEB.war,WEB-INF/web.xml WebSphere:cell=SOMEHOST-SOMECELL,node=SOMEHTTPSERVER,server=webserver1+WebSphere:cell=SOMECELL,node=SOMENODE,server=server1}}</was6.mapModulesToServers>
> ...
> </configuration>
> These parameters can be found from the Websphere configuration and vary server to server. The exact mapping typically can be extraced from the Admin Console.

[jira] Updated: (MOJO-1452) svnversion is better than svn -info for build numbers.

2009-11-05T13:10:55Z

[ http://jira.codehaus.org/browse/MOJO-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MOJO-1452:
-------------------------------

Issue Type: Improvement (was: Bug)

> svnversion is better than svn -info for build numbers.
> ------------------------------------------------------
>
> Key: MOJO-1452
> URL: http://jira.codehaus.org/browse/MOJO-1452
> Project: Mojo
> Issue Type: Improvement
> Components: _Plugin Submission
> Affects Versions: buildnumber-maven-plugin-1.0-beta-3
> Environment: Any subversion
> Reporter: James R. Collings
>
> "svn --info" isn't the proper subversion tool for retrieving version info of local copy.
> See this thread:
> http://tinyurl.com/yh4mzf7
> The point is that I might be using a generated artifact and not be quite certain of the version and/or the status of that version. 'svnversion' will handle this while svn --info does not.

RE: Re: [REVIEW REQUEST] Animal Sniffer

2009-11-05T13:09:22Z

> Date: Thu, 5 Nov 2009 20:36:18 +0000
> From: stephen.alan.connolly@...
> To: dev@...
> CC: dev@...
> Subject: [mojo-dev] Re: [REVIEW REQUEST] Animal Sniffer
>
> Damn, ment to go for dev@codehaus
>
> 2009/11/5 Stephen Connolly <stephen.alan.connolly@...>:
> > Hey all,
> >
> > I've been working on the animal-sniffer documentation.
> >
> > It would be greatly appreciated if some more eyes could take a look at
> > what I've done so far:
> >
> > Main site: http://mojo.codehaus.org/animal-sniffer/
> > Java Boot classpath detector:
> > http://mojo.codehaus.org/animal-sniffer/java-boot-classpath-detector/index.html
> > Annotations for Java 1.5+:
> > http://mojo.codehaus.org/animal-sniffer/animal-sniffer-annotations/index.html
> > API/CLI: http://mojo.codehaus.org/animal-sniffer/animal-sniffer/index.html
> > Maven Enforcer Rule:
> > http://mojo.codehaus.org/animal-sniffer/animal-sniffer-enforcer-rule/index.html
> > ANT Tasks: http://mojo.codehaus.org/animal-sniffer/animal-sniffer-ant-tasks/index.html
> > Maven Plugin: http://mojo.codehaus.org/animal-sniffer-maven-plugin/index.html
> >
> > Please respond with comments on this thread, or please update SVN with
> > your fixes
> >
> > I'd like to have the site fixed and ready for a Vote by Saturday...
> > Then I just have to sort out the Java Signatures (which I cannot roll
> > a release of until we have animal-sniffer-maven-plugin released
> >
> > Thanks,
> >
> > -Stephen
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

Express yourself instantly with MSN Messenger! MSN Messenger

Re: [REVIEW REQUEST] Animal Sniffer

2009-11-05T12:36:18Z

Damn, ment to go for dev@codehaus

2009/11/5 Stephen Connolly <stephen.alan.connolly@...>:

> Hey all,
>
> I've been working on the animal-sniffer documentation.
>
> It would be greatly appreciated if some more eyes could take a look at
> what I've done so far:
>
> Main site: http://mojo.codehaus.org/animal-sniffer/
> Java Boot classpath detector:
> http://mojo.codehaus.org/animal-sniffer/java-boot-classpath-detector/index.html
> Annotations for Java 1.5+:
> http://mojo.codehaus.org/animal-sniffer/animal-sniffer-annotations/index.html
> API/CLI: http://mojo.codehaus.org/animal-sniffer/animal-sniffer/index.html
> Maven Enforcer Rule:
> http://mojo.codehaus.org/animal-sniffer/animal-sniffer-enforcer-rule/index.html
> ANT Tasks: http://mojo.codehaus.org/animal-sniffer/animal-sniffer-ant-tasks/index.html
> Maven Plugin: http://mojo.codehaus.org/animal-sniffer-maven-plugin/index.html
>
> Please respond with comments on this thread, or please update SVN with
> your fixes
>
> I'd like to have the site fixed and ready for a Vote by Saturday...
> Then I just have to sort out the Java Signatures (which I cannot roll
> a release of until we have animal-sniffer-maven-plugin released
>
> Thanks,
>
> -Stephen
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (MWAS-56) allow ability when deploying to map to HTTP server and application server for module

2009-11-05T11:38:55Z

[ http://jira.codehaus.org/browse/MWAS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197396#action_197396 ]

David J. M. Karlsen commented on MWAS-56:
-----------------------------------------

Cool - thanks.
Do you have links to any IBM documentation and/or articles?
Would you care to add some documentation as well (examples on usage).
Are you able to provide any tests for this?

[jira] Created: (MOJO-1452) svnversion is better than svn -info for build numbers.

2009-11-05T11:29:55Z

svnversion is better than svn -info for build numbers.
------------------------------------------------------

Key: MOJO-1452
URL: http://jira.codehaus.org/browse/MOJO-1452
Project: Mojo
Issue Type: Bug
Components: _Plugin Submission
Affects Versions: buildnumber-maven-plugin-1.0-beta-3
Environment: Any subversion
Reporter: James R. Collings

"svn --info" isn't the proper subversion tool for retrieving version info of local copy.

See this thread:

http://tinyurl.com/yh4mzf7

The point is that I might be using a generated artifact and not be quite certain of the version and/or the status of that version. 'svnversion' will handle this while svn --info does not.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (MWAS-56) allow ability when deploying to map to HTTP server and application server for module

2009-11-05T11:23:55Z

[ http://jira.codehaus.org/browse/MWAS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197392#action_197392 ]

Josh Joy commented on MWAS-56:
------------------------------

Additionally, this patch changes the validation of type "ear" to validate the artifact rather than the project POM.

The reason for this, is typically when moving an EAR from dev->test->prod, the same EAR should be used. Thus, in certain situations a "deploy" POM may be used, rather than building the artifact for each environment. Since the "deploy" POM will be of type "pom", though the actual artifact being deployed is of type "ear", thus to be more specific would like to propose that the artifact itself be validated to be of type "EAR".

[jira] Created: (MWAS-56) allow ability when deploying to map to HTTP server and application server for module

2009-11-05T11:19:55Z

allow ability when deploying to map to HTTP server and application server for module
-------------------------------------------------------------------------------------

Key: MWAS-56
URL: http://jira.codehaus.org/browse/MWAS-56
Project: Maven 2.x WebSphere 6 Plugin
Issue Type: Improvement
Affects Versions: 1.2
Environment: when using IBM HTTP Server
Reporter: Josh Joy
Assignee: David J. M. Karlsen
Attachments: wasv6-maven-plugin.txt

when using IBM HTTP Server, there is a Websphere option in the Admin console "Map modules to servers". If IBM HTTP Server is setup and configured, there is an option to bind to both HTTP Server and the application server. The Websphere option is "-MapModulesToServers". This patch provides another configuration parameter to the plugin "mapModulesToServers".

For example, to use it

<configuration>
....
<was6.mapModulesToServers>{{SOMEWEB SOMEWEB.war,WEB-INF/web.xml WebSphere:cell=SOMEHOST-SOMECELL,node=SOMEHTTPSERVER,server=webserver1+WebSphere:cell=SOMECELL,node=SOMENODE,server=server1}}</was6.mapModulesToServers>
...
</configuration>

These parameters can be found from the Websphere configuration and vary server to server. The exact mapping typically can be extraced from the Admin Console.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Closed: (MOJO-1414) Upgrade to last scm svnjava provider (to upgrade to SVNkit 1.3.0 in order to support svn 1.6)

2009-11-05T07:03:55Z

[ http://jira.codehaus.org/browse/MOJO-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MOJO-1414.
------------------------------

Resolution: Fixed
Fix Version/s: buildnumber-maven-plugin-1.0-beta-4

upgrade done

> Upgrade to last scm svnjava provider (to upgrade to SVNkit 1.3.0 in order to support svn 1.6)
> ---------------------------------------------------------------------------------------------
>
> Key: MOJO-1414
> URL: http://jira.codehaus.org/browse/MOJO-1414
> Project: Mojo
> Issue Type: Improvement
> Affects Versions: buildnumber-maven-plugin-1.0-beta-3, buildnumber-maven-plugin-1.0-beta-4
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: buildnumber-maven-plugin-1.0-beta-4
>
>

[jira] Reopened: (MOJO-1414) Upgrade to last scm svnjava provider (to upgrade to SVNkit 1.3.0 in order to support svn 1.6)

2009-11-05T07:03:55Z

[ http://jira.codehaus.org/browse/MOJO-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reopened MOJO-1414:
--------------------------------