Nabble - mojo - user

Re: Multiple tests and reports

2009-11-12T13:25:23Z

I believe the problem is the stuff in the parent pom. The dataid present here seem to take precedence over the dataid's in the child pom.

I do not have acces to the code right now, but why do You want to mention it in the root pom at all?

If You send me Your pom's, I can take a look at them tomorrow.

/Kent

Den 09/11/2009 kl. 15.08 skrev Andy Bell:

Hi Kent

I'm afraid it makes no difference. What seems to be adding complexity to this is that the report's pom.xml is picking up the overall project's pom.xml from the maven repository and configuring this seems to be part of the problem. What we are looking to achieve is to run all our tests (which is happening), produce all the history reports (again this is fine) and then produce the individual tests - but this bit fails because I cannot find a way to get chronos to generate them all.

In the main project's pom.xml there is this bit:

<plugin>
                  <groupId>org.codehaus.mojo</groupId>
                  <artifactId>chronos-maven-plugin</artifactId>
                  <version>1.0-SNAPSHOT</version>
                  <configuration>
                        <historydir>${history.home}</historydir>
                        <dataid>broker-import-service-volume-report</dataid>
                  </configuration>

If I exclude the <dataid> tag, then the report fails as it doesn't know what to build but if i include the <dataid> then only that single report gets built. What I need is a way for chronos to determine (or me to tell it) which reports to build... If you want I can email both these pom.xml file to you...

Andy

2009/11/9 Kent Sølvsten <ksr@...>
Hi Andy

This part looks weird, what happens, if you delete that?

Den 09/11/2009 kl. 12.29 skrev Andy Bell:

<reportSet>
<reports>
<report>report</report>
</reports>
</reportSet>

/Kent

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

http://xircles.codehaus.org/manage_email

--
Andy

[ANN] Animal Sniffer 1.3 released

2009-11-12T02:23:55Z

The Mojo team is pleased to announce the release of Animal Sniffer version 1.3.

This is the first release of Animal Sniffer
(http://mojo.codehaus.org/animal-sniffer/) since it moved from
java.net to the mojo project at codehaus.

Animal Sniffer provides tools to assist verifying that classes
compiled with a newer JDK/API are compatible with an older JDK/API.

The following tools are provided by animal sniffer:

* A command line tool to dump the class file version number
(http://mojo.codehaus.org/animal-sniffer/animal-sniffer/index.html).
This helps you track down the offending jar file when you see
UnsupportedClassVersionError.

* A set of ANT tasks
(http://mojo.codehaus.org/animal-sniffer/animal-sniffer-ant-tasks/index.html)
for verifying that your classes comply with an API signature as well
as tasks for creating API signatures from a JDK, or a collection or
jar and class files, or a collection of other API signature files, or
combination of these elements.

* A rule for use in the maven-enforcer-plugin
(http://mojo.codehaus.org/animal-sniffer/animal-sniffer-enforcer-rule/index.html)
for verifying that your classes comply with an API signature .

* A maven plugin
(http://mojo.codehaus.org/animal-sniffer-maven-plugin/index.html) for
verifying that your classes comply with an API signature as well as
for creating API signatures from a JDK, or the current module's
classes, or the current module's dependencies, or a collection of
other API signature files, or combination of these elements.

The artifacts have been deployed to the codehaus repository and have
been/will be
mirrored to central.

The Mojo Team.

Note: as of 10:22 GMT 12/11/2009 animal sniffer has not
been pushed to maven central. If you cannot wait the (at most) 24
hours for this sync, you can use the codehaus repository
(http://repository.codehaus.org/).

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

http://xircles.codehaus.org/manage_email

[ANN] JBoss Maven Plugin 1.4 Released

2009-11-09T06:19:28Z

The Mojo team is pleased to announce the release of the JBoss Maven Plugin
version 1.4.

http://mojo.codehaus.org/jboss-maven-plugin/

Some notable features in this release include improvements to the start-and-wait
mojo and general improvements to the plugin configuration. The plugin site has
also been improved and now provides more docs and examples.

To get this update, simply specify the version in your project's plugin
configuration:

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-maven-plugin</artifactId>
<version>1.4</version>
</plugin>

A comprehensive list of changes is attached at the end of this mail.

Regards,

The Mojo team.

Release Notes - Maven 2.x JBoss Plugin - Version 1.4.0

** Bug
* [MJBOSS-23] - jboss:undeploy causes NPE
* [MJBOSS-30] - NullPointerException in UndeployMojo

** Improvement
* [MJBOSS-24] - JBoss plugin should be able to read JBOSS_HOME when using
JDK < 1.5
* [MJBOSS-25] - Refactor to follow Maven code formatting conventions.
* [MJBOSS-26] - Should be able to override the parameters for the
startAndWait mojo from the command line.
* [MJBOSS-28] - harddeploy should skip unconfigured POMs without failing
* [MJBOSS-31] - Fix deprecation warnings about using components.
* [MJBOSS-32] - Improve parameter configuration
* [MJBOSS-33] - Improve site documentation
* [MJBOSS-34] - Add a wait period between retries of the JMX Connection
when using startAndWaitGoal
* [MJBOSS-35] - startAndWait mojo needs a security manager
* [MJBOSS-36] - Mojo goal names should follow standard Maven naming format.

** New Feature
* [MJBOSS-29] - Add exploded deployment support

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

http://xircles.codehaus.org/manage_email

Re: Multiple tests and reports

2009-11-09T06:08:34Z

Hi Kent

I'm afraid it makes no difference. What seems to be adding complexity to this is that the report's pom.xml is picking up the overall project's pom.xml from the maven repository and configuring this seems to be part of the problem. What we are looking to achieve is to run all our tests (which is happening), produce all the history reports (again this is fine) and then produce the individual tests - but this bit fails because I cannot find a way to get chronos to generate them all.

In the main project's pom.xml there is this bit:

<plugin>
                  <groupId>org.codehaus.mojo</groupId>
                  <artifactId>chronos-maven-plugin</artifactId>
                  <version>1.0-SNAPSHOT</version>
                  <configuration>
                        <historydir>${history.home}</historydir>
                        <dataid>broker-import-service-volume-report</dataid>
                  </configuration>

If I exclude the <dataid> tag, then the report fails as it doesn't know what to build but if i include the <dataid> then only that single report gets built. What I need is a way for chronos to determine (or me to tell it) which reports to build... If you want I can email both these pom.xml file to you...

Andy

2009/11/9 Kent Sølvsten <ksr@...>

Hi Andy

This part looks weird, what happens, if you delete that?

Den 09/11/2009 kl. 12.29 skrev Andy Bell:

<reportSet>
<reports>
<report>report</report>
</reports>
</reportSet>

/Kent

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

http://xircles.codehaus.org/manage_email

--
Andy

Re: Multiple tests and reports

2009-11-09T05:52:18Z

Hi Andy

This part looks weird, what happens, if you delete that?

Den 09/11/2009 kl. 12.29 skrev Andy Bell:

> <reportSet>
> <reports>
> <report>report</report>
> </reports>
> </reportSet>

/Kent

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

http://xircles.codehaus.org/manage_email

Re: Multiple tests and reports

2009-11-09T03:29:25Z

Hi Kent

Here's the bits from the pom (reporting section)

<reporting>
      <plugins>
        <plugin>
         <groupId>org.codehaus.mojo</groupId>
         <artifactId>chronos-maven-plugin</artifactId>
         <version>1.0-SNAPSHOT</version>
                  <configuration>
                        <historydir>${history.directory}</historydir>
                  </configuration>

             <reportSets>
                <reportSet>
                  <reports>
                    <report>report</report>
                  </reports>
                </reportSet>
                <reportSet>
                  <id>broker-import-service-volume-report</id>
                   <configuration>
                      <dataid>broker-import-service-volume-report</dataid>
                      <reportid>broker-import-service-volume-report</reportid>
                      <title>Broker Service Import Volume Test History Report</title>
                      <description>
                      <![CDATA[Volume Performance tests which are focused on determining or validating performance characteristics of the Broker service import operation when subjected to payloads of increasing size.]]>
                      </description>
                      <historydir>${history.home}</historydir>
                      <showaverage>true</showaverage>
                      <showpercentile>true</showpercentile>
                      <showinfotable>true</showinfotable>
                      <showtimeinfo>true</showtimeinfo>
                      <showsummary>true</showsummary>
                      <showdetails>true</showdetails>
                      <showresponse>true</showresponse>
                      <showhistogram>true</showhistogram>
                      <showthroughput>true</showthroughput>
                      <showsummarycharts>true</showsummarycharts>
                      <showgc>true</showgc>
                  </configuration>

                  <reports>
                    <report>report</report>
                  </reports>
                </reportSet>
                <reportSet>
                  <id>broker-import-service-concurrency-report</id>
                   <configuration>
                      <dataid>broker-import-service-concurrency-report</dataid>
                      <reportid>broker-import-service-concurrency-report</reportid>
                      <title>Broker Service Import Concurrency Test History Report</title>
                      <description>
                      <![CDATA[Concurrency Performance tests which are focused on determining or validating performance characteristics of the Broker service import operation when subjected to multiple users anticipated during production operations.]]>
                      </description>
                      <historydir>${history.home}</historydir>
                      <showaverage>true</showaverage>
                      <showpercentile>true</showpercentile>
                      <showinfotable>true</showinfotable>
                      <showtimeinfo>true</showtimeinfo>
                      <showsummary>true</showsummary>
                      <showdetails>true</showdetails>
                      <showresponse>true</showresponse>
                      <showhistogram>true</showhistogram>
                      <showthroughput>true</showthroughput>
                      <showsummarycharts>true</showsummarycharts>
                      <showgc>true</showgc>
                  </configuration>
                  <reports>
                    <report>report</report>
                  </reports>
                </reportSet>
            </reportSets>
          </plugin>
        </plugins>
    </reporting>

2009/11/9 Kent Sølvsten <ksr@...>

Hi Andy

Can you show the relevant parts of the pom?

You may be missing some dataid elements. If you have multiple tests, each should be identified by a unique dataid element, which should be referred to from reports.

/Kent

Den 09/11/2009 kl. 11.33 skrev Andy Bell:

Hi

This page:

http://mojo.codehaus.org/chronos-maven-plugin/usage.html

Shows how to set up a maven .pom to run a test and report on it. I am trying to amend this .pom to run and report on multiple tests. I can get it to run as many tests as i want by having multiple <execution> sections in the <executions> block, BUT I cannot find a way to get chronos to produce reports for each of these fromthe same POM.

I have tried adding many <reportSet> elements to the <reportSets> section, but the only report that is produced is the one whose <dataid> and <reportid> is the same as that stated in the <configuration> element. Is there a way to have multiple <configuration> elements?? If there is, I cannot find out how to do it...

--
Andy

--
Andy

Re: Multiple tests and reports

2009-11-09T03:09:19Z

Hi Andy

Can you show the relevant parts of the pom?

You may be missing some dataid elements. If you have multiple tests, each should be identified by a unique dataid element, which should be referred to from reports.

/Kent

Den 09/11/2009 kl. 11.33 skrev Andy Bell:

Hi

This page:

http://mojo.codehaus.org/chronos-maven-plugin/usage.html

Shows how to set up a maven .pom to run a test and report on it. I am trying to amend this .pom to run and report on multiple tests. I can get it to run as many tests as i want by having multiple <execution> sections in the <executions> block, BUT I cannot find a way to get chronos to produce reports for each of these fromthe same POM.

I have tried adding many <reportSet> elements to the <reportSets> section, but the only report that is produced is the one whose <dataid> and <reportid> is the same as that stated in the <configuration> element. Is there a way to have multiple <configuration> elements?? If there is, I cannot find out how to do it...

--
Andy

Multiple tests and reports

2009-11-09T02:33:25Z

Hi

This page:

http://mojo.codehaus.org/chronos-maven-plugin/usage.html

Shows how to set up a maven .pom to run a test and report on it. I am trying to amend this .pom to run and report on multiple tests. I can get it to run as many tests as i want by having multiple <execution> sections in the <executions> block, BUT I cannot find a way to get chronos to produce reports for each of these fromthe same POM.

I have tried adding many <reportSet> elements to the <reportSets> section, but the only report that is produced is the one whose <dataid> and <reportid> is the same as that stated in the <configuration> element. Is there a way to have multiple <configuration> elements?? If there is, I cannot find out how to do it...

--
Andy

deploy rpm to rpm repository using maven + mojo rpm plugin

2009-11-08T00:00:10Z

Hi guys,

I've just starting to play around with maven as a candidate for our whole build/deploy system for java applications.

we're been programming so far using Perl, packaging with Rpm on Fedora and Deploying it though a local yum repository.

We still haven't decided if we could ditch the yum/rpm idea all together and switch to mvn repository. but in case we won't,

Do you know if there is a way to config mvn to upload the rpm (using SCP?) to the yum repository after

it finishes building the RPM (today we use a build system based on make files and in the end it scp's the rpm to the repository and run make there to update the list of rpms).

thank you.

--
Eyal Edri

[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

Re: org.codehaus.mojo: scmchangelog-maven-plugin problems

2009-11-06T09:50:31Z

This is expected, as your comments don't respect any grammar we can't extract the bug id and so include a link to the bug.
If you could provide a regexp to extract your issue ids this would work.
By the way, I am not familiar with JIRA integration with SVN, if you could provide such information we would gladly integrate it into our plugin.
Emmanuel

On Fri, Nov 6, 2009 at 5:13 PM, Martin Todorov <carlspring@...> wrote:

Hi Emmanuel,

Thanks!

This has solved the SVN log problem I was running into.

Now I am facing another problem - there are no JIRA issues/links in the produced reports.
I have an isssueManagement described as follows:
    <issueManagement>
        <system>JIRA</system>
        <url>http://myJira/jira/BrowseProject.jspa?id=10390</url>

        
        
    </issueManagement>

And the settings for the plugin are as follows

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

                <configuration>
                    <trackerType>jira</trackerType>
                    <trackerUrlPattern>http://myJira/jira/BrowseProject.jspa?id=10390</trackerUrlPattern>

                    <connectionUrl>scm:svn:https://mySVN/subversion/uicc/production/hpl2/trunk/</connectionUrl>
                    <tagBase>https://mySVN/subversion/uicc/production/hpl2/tags/</tagBase>
                    <grammar>ALL</grammar>

                </configuration>
            </plugin>

There is no output concerning the JIRA links whatsoever, so I can't attach a useful log.

Maybe I haven't configured something...?

My JIRA and SVN usernames/passwords are different and I can't change them. Could this be the problem?

Thanks again and I hope you have some more hints!
All the best,

Martin

On Fri, Nov 6, 2009 at 3:18 PM, Emmanuel Hugonnet <ehsavoie73@...> wrote:

Hi,
Rémy sent me your log file.It looks like your commetns are not respecting the grammar format which explains why the messages are not displayed. If you use the ALL grammar all the messages should appear. Could you please try it ?
Emmanuel

On Fri, Nov 6, 2009 at 11:58 AM, Emmanuel Hugonnet <ehsavoie73@...> wrote:

Hi,
For the svn in the $PATh this is because at that time we can't use Maven SCM since it is missing some attributes (the XML log for svn and the fact that I need the BetterChangeset instead of their ChangeSet) but the code is more than just similar, it is just an adaptation. SVNKit should be a problem, but I am not very familiar with it and I did'nt have time to look into it, but of course any help is welcome.
I am surprised by the XML parsing erreor, as we use Subversion own schemas to generate the parsing code. Maybe it has evolved since, but that would surprise me ? It seems like there is n exception thrown could you please give us the traces so we could see where the issue comes from ? Maybe you could create a JIRA issue o you could attach your log file (and your SVNKit patch :-P )
Emmanuel

On Thu, Nov 5, 2009 at 4:32 PM, Rémy Sanlaville <remy.sanlaville@...> wrote:

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

Re: org.codehaus.mojo: scmchangelog-maven-plugin problems

2009-11-06T05:18:54Z

Hi,
Rémy sent me your log file.It looks like your commetns are not respecting the grammar format which explains why the messages are not displayed. If you use the ALL grammar all the messages should appear. Could you please try it ?
Emmanuel

On Fri, Nov 6, 2009 at 11:58 AM, Emmanuel Hugonnet <ehsavoie73@...> wrote:

Hi,
For the svn in the $PATh this is because at that time we can't use Maven SCM since it is missing some attributes (the XML log for svn and the fact that I need the BetterChangeset instead of their ChangeSet) but the code is more than just similar, it is just an adaptation. SVNKit should be a problem, but I am not very familiar with it and I did'nt have time to look into it, but of course any help is welcome.
I am surprised by the XML parsing erreor, as we use Subversion own schemas to generate the parsing code. Maybe it has evolved since, but that would surprise me ? It seems like there is n exception thrown could you please give us the traces so we could see where the issue comes from ? Maybe you could create a JIRA issue o you could attach your log file (and your SVNKit patch :-P )
Emmanuel

On Thu, Nov 5, 2009 at 4:32 PM, Rémy Sanlaville <remy.sanlaville@...> wrote:

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

Reports only generated for first report

2009-11-06T03:01:10Z

Hi

We have a suite of reports, all of which are specified in a .pom file in the <executions> section. i.e.:

<executions>
              <execution>
                <id>portfolio-service-report</id>
                <configuration>
                  <dataid>portfolio-service-report</dataid>
                  <input>${basedir}/src/test/jmeter/Portfolio Service Concurrency Test.jmx</input>
                </configuration>
               ...omit loads of bits...
              </execution>
              <execution>
                <id>security-service-report</id>
              ...and so forth...

When we ask chronos to produce a History Report - all is fine, each test's reports get genrated correctly.

But if we ask for the ordinary Reports, Chronos only produces a report from the first report in our .pom ...

Is this a bug or do we need to specify things differently in the pom?

Thanks,

--
Andy

Re: org.codehaus.mojo: scmchangelog-maven-plugin problems

2009-11-06T02:58:43Z

Hi,
For the svn in the $PATh this is because at that time we can't use Maven SCM since it is missing some attributes (the XML log for svn and the fact that I need the BetterChangeset instead of their ChangeSet) but the code is more than just similar, it is just an adaptation. SVNKit should be a problem, but I am not very familiar with it and I did'nt have time to look into it, but of course any help is welcome.
I am surprised by the XML parsing erreor, as we use Subversion own schemas to generate the parsing code. Maybe it has evolved since, but that would surprise me ? It seems like there is n exception thrown could you please give us the traces so we could see where the issue comes from ? Maybe you could create a JIRA issue o you could attach your log file (and your SVNKit patch :-P )
Emmanuel

On Thu, Nov 5, 2009 at 4:32 PM, Rémy Sanlaville <remy.sanlaville@...> wrote:

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

Re: org.codehaus.mojo: scmchangelog-maven-plugin problems

2009-11-05T07:32:59Z

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

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

http://xircles.codehaus.org/manage_email

RE: Maven versions plugin - Questions regarding updating versions in branches

2009-11-05T02:56:59Z

I've used xslt in the past for doing similar things, a lot easier
than the awk scripts I used to use. The following updates versions
(for both the pom artifact and it's depenancies) for specified group
and optional artifact

<?xml version="1.1" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" >
<xsl:output method="xml"/>
<xsl:preserve-space elements="*"/>

<xsl:param name="groupId"/>
<xsl:param name="oldVersion"/>
<xsl:param name="newVersion"/>
<xsl:param name="artifact"/>

<xsl:template match="*[name()='version'][not($artifact) or preceding-sibling::*[name()='artifactId'][text()=$artifact]][text()=$oldVersion][preceding-sibling::*[name()='groupId'][text()=$groupId]]">
<version><xsl:value-of select="$newVersion"/></version>
</xsl:template>

<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>

</xsl:stylesheet>

This can be executed using saxon with the command

java -jar saxon9.jar -o:pom.xml -s:pom.xml -xsl:updateVersion.xsl groupId=my.group oldVersion=0.9.9 newVersion=1.0.0

Regards, Vic

-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@...]
Sent: 05 November 2009 10:15
To: user@...
Subject: Re: [mojo-user] Maven versions plugin - Questions regarding updating versions in branches

2009/10/30 Børge Haugsdal <borge.haugsdal@...>:

>
>
> ---------- Forwarded message ----------
> From: Børge Haugsdal <borge.haugsdal@...>
> Date: 2009/10/30
> Subject: Maven versions plugin - Questions regarding updating versions
> in branches
> To: user@...
>
>
> We have now more that 50 multi-module projects to manage each with
> 2-10 sub-modules. The list is growing fast.
>
> In out project we have a lot of dependencies between projects, so
> tagging and version management makes a lot of work, and creates a lot
> of hassle.
>
> And we have right now 4 complete branches to manage at the same time.
>
> I have tried now making scripts (shell and .bat) to handle the tagging
> process. And it works. I must say that the versions plugin has saved
> us for a lot of work. All version information is stored in properties
> like <logging.version>33.1.1</logging.version> in each multimodule
> pom.xml

the main use-case for properties defining versions is where you have a suite of dependencies which must have their version aligned.

If you are not in that use-case I would use the http://mojo.codehaus.org/versions-maven-plugin/examples/advancing-dependency-versions.html
goals
as they support filtering exactly which groupId/artifactIds to advance, and can limit advancing to minor updates only

> All groupIds in our internal projects is made in the format
> <groupId>no.mycompany.area</groupId>
>
> Tagging TRUNK using scripts - solved
> When we tag the TRUNK we always tag all code if changes has been made
> in a module, and updates all modules to the latest versions of our
> internal dependencies. So, we are able to automate the process just by
> listing the projects to tag in a given order, and then calling scripts
> to tag and update versions dependencies.
> So the TRUNK is no problem anymore, much thanks to the maven versions
> plugin.
>
> Tagging BRANCHES using scripts - still a problem
> When it comes to the BRANCHES we still have problems.
> I know that in the versions plugin it is possible to update to the
> newest versions using ranges defined in the poms. But it seems to me
> like have to change each pom for each time we create a branch with
> range information, and add our dependencies twice in the pom, once in
> dependency list and once in the plugin def. itself. As far as I have
> understood the process... So the pom grows and it becomes more work to
> manage it. . I hope I can do this without doing a lot of changes in
> the poms.
>
> I hope I can script tagging of branches too.
> When we are working in trunk we have the same majorVersion and
> minorVersion in all projects. Like 33.1.X When we create a new branch
> from trunk, we update the versions in the TRUNK poms. Like 34.1.0
>
> So in our branch coming from the trunk version 33.1.X we want to
> always use the latest release or snapshot versions in the range
> 33.1.0.0 to 34.0.0
>
> So (finally) my question is:
> Is there a way that I from a script/command-line can specify that for
> a given groupId I want to update all versions stored in the pom (in
> <properties>) for all of our dependencies, with versions higher that
> 33.1.0.0 and less that 34.0.0
>
> Example update to latest RELEASE version of all our artifacts in the
> branch: mvn versions:update-properties -DGroupId=no.<mycompany>
> -DVersionRange=[33.1.0.0,34.0.0)
>
> Example update to latest SNAPSHOT version of all our artifacts in the
> branch:
> mvn versions:update-properties -DGroupId=no.<mycompany>
> -DVersionRange=[33.1.0,34.0.0) -DallowSnapshot
> -DexcludePeroperties="XX.version,YY.version"
>
> Is something like this possible?
> What is the best solution for this?
>
> I hope you can help me out here.
>
> Another, and less important question.
> It would be nice to have a command like this:
> mvn versions:update-properties -DGroupId=no.<mycompany>
> -DVersionRange=[33.1.0,33.2.0) -DallowSnapshots
> -DexcludeGroupIds="no-<mycompany>.common"
> Right now the excludeProterties is growing fast.
> All of our modules always in stable versions has a common groupId like
> above. The list with dependencies to exclude is growing, so I hope for
> an easier way.
>
> I hope you have time for my questions...
>
> Best Regards
>
> Børge Haugsdal
>
>
>
>
> --
> Hilsen
>
> Børge Haugsdal
>
>
>
> --
> Hilsen
>
> Børge Haugsdal
>

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

http://xircles.codehaus.org/manage_email

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

This e-mail and any attachments are for the intended addressee(s) only
and may contain confidential and/or privileged material. If you are not a
named addressee, do not use, retain or disclose such information.
This email is not guaranteed to be free from viruses and does not bind
Serco in any contract or obligation.
Serco Limited. Registered in England and Wales. No: 242246
Registered Office: Serco House,16 Bartley Wood Business Park, Hook,
Hampshire RG27 9UY United Kingdom.

Help cut carbon...please don’t print this e-mail unless you really need to.

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

http://xircles.codehaus.org/manage_email

Re: Maven versions plugin - Questions regarding updating versions in branches

2009-11-05T02:14:53Z

2009/10/30 Børge Haugsdal <borge.haugsdal@...>:

>
>
> ---------- Forwarded message ----------
> From: Børge Haugsdal <borge.haugsdal@...>
> Date: 2009/10/30
> Subject: Maven versions plugin - Questions regarding updating versions in
> branches
> To: user@...
>
>
> We have now more that 50 multi-module projects to manage each with 2-10
> sub-modules.
> The list is growing fast.
>
> In out project we have a lot of dependencies between projects, so tagging
> and version management makes a lot of work, and creates a lot of hassle.
>
> And we have right now 4 complete branches to manage at the same time.
>
> I have tried now making scripts (shell and .bat) to handle the tagging
> process. And it works.
> I must say that the versions plugin has saved us for a lot of work.
> All version information is stored in properties like
> <logging.version>33.1.1</logging.version> in each multimodule pom.xml

the main use-case for properties defining versions is where you have a
suite of dependencies which must have their version aligned.

If you are not in that use-case I would use the
http://mojo.codehaus.org/versions-maven-plugin/examples/advancing-dependency-versions.html
goals
as they support filtering exactly which groupId/artifactIds to
advance, and can limit advancing to minor updates only

> All groupIds in our internal projects is made in the format
> <groupId>no.mycompany.area</groupId>
>
> Tagging TRUNK using scripts - solved
> When we tag the TRUNK we always tag all code if changes has been made in a
> module, and updates all modules to the latest versions of our internal
> dependencies.
> So, we are able to automate the process just by listing the projects to tag
> in a given order, and then calling scripts to tag and update versions
> dependencies.
> So the TRUNK is no problem anymore, much thanks to the maven versions
> plugin.
>
> Tagging BRANCHES using scripts - still a problem
> When it comes to the BRANCHES we still have problems.
> I know that in the versions plugin it is possible to update to the newest
> versions using ranges defined in the poms.
> But it seems to me like have to change each pom for each time we create a
> branch with range information, and add our dependencies twice in the pom,
> once in dependency list and once in the plugin def. itself.
> As far as I have understood the process...
> So the pom grows and it becomes more work to manage it. .
> I hope I can do this without doing a lot of changes in the poms.
>
> I hope I can script tagging of branches too.
> When we are working in trunk we have the same majorVersion and minorVersion
> in all projects. Like 33.1.X
> When we create a new branch from trunk, we update the versions in the TRUNK
> poms. Like 34.1.0
>
> So in our branch coming from the trunk version 33.1.X we want to always use
> the latest release or snapshot versions in the range 33.1.0.0 to 34.0.0
>
> So (finally) my question is:
> Is there a way that I from a script/command-line can specify that for a
> given groupId I want to update all versions stored in the pom (in
> <properties>) for all of our dependencies, with versions higher that
> 33.1.0.0 and less that 34.0.0
>
> Example update to latest RELEASE version of all our artifacts in the branch:
> mvn versions:update-properties -DGroupId=no.<mycompany>
> -DVersionRange=[33.1.0.0,34.0.0)
>
> Example update to latest SNAPSHOT version of all our artifacts in the
> branch:
> mvn versions:update-properties -DGroupId=no.<mycompany>
> -DVersionRange=[33.1.0,34.0.0) -DallowSnapshot
> -DexcludePeroperties="XX.version,YY.version"
>
> Is something like this possible?
> What is the best solution for this?
>
> I hope you can help me out here.
>
> Another, and less important question.
> It would be nice to have a command like this:
> mvn versions:update-properties -DGroupId=no.<mycompany>
> -DVersionRange=[33.1.0,33.2.0) -DallowSnapshots
> -DexcludeGroupIds="no-<mycompany>.common"
> Right now the excludeProterties is growing fast.
> All of our modules always in stable versions has a common groupId like
> above. The list with dependencies to exclude is growing, so I hope for an
> easier way.
>
> I hope you have time for my questions...
>
> Best Regards
>
> Børge Haugsdal
>
>
>
>
> --
> Hilsen
>
> Børge Haugsdal
>
>
>
> --
> Hilsen
>
> Børge Haugsdal
>

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

http://xircles.codehaus.org/manage_email

Re: gwt-maven-plugin Using multiproject with gwt

2009-11-04T13:20:51Z

The builder-helper-maven-plugin should solve this for you. If you want to run hosted mode in your JAR projects, you might want to checkout the following blog entry as well:

http://raibledesigns.com/rd/entry/running_hosted_mode_in_gwt

Matt

P.Kernevez wrote:

Hi,

I have a multiproject gwt application.
Like :

Root
|
|--> project A (GUI framework)
|--> project B ( customer gwt module)
|--> project C ( contract gwt module)
|--> project Final (packaging of the webapp)

I would like to be able to launch the hosted browser on my Final module and work on the source of the project A, B and C.
We can simply do that with GWT by add the project source folder to the classpath, and we only have to click on the Refresh button of the hosted browser to see the last modifications.

Is there a solution for that ?

I take a look on the plugin code, I saw a mecanism for doing that in the class : ClasspathBuilder.addSourcesWithActiveProjects() but that don't seems to my request.
Tis is due to the fact that it's done for compiling only (not for the hosted browser) and it need to be in the reactor mode.
The full build (reactor) is a good way for a full compilation but it doesn't have sens for the hosted browser.
If you don't have an already solution, what do you think about a patch that add an optional list of source folders to the beginning of the classpath and that would be set mannualy ?

Thanks,
Philippe Kernevez

Re: gwt-maven-plugin Package fails because of arrays in Interface

2009-11-02T03:16:45Z

Bernhard, are you sure the GWT shell can generate the async
interface?. The graph in this page says the opposite:

http://code.google.com/intl/es/webtoolkit/doc/1.6/DevGuideServerCommunication.html

If the maven-gwt-plugin does it and it's failing in this case,
shouldn't I report the issue in the Mojo page?.

Thank you,

Ivan

On Mon, Nov 2, 2009 at 6:51 AM, bernhard s <nebenmir@...> wrote:

>
>
>>
>> I think the cause of the problem is the mismatch in the definition of
>> the methods in both versions of DirectorioTiendasServiceAsync, the
>> original one has arrays and the generated one is missing them.
>
> ja, i think thats the problem. unfortunately i have no answer to that, just
> a question.
> Does the gwt-maven-plugin generate the async interface for you (well it
> seems so because of the folder it lays in)? Does the async interface also
> miss the arrays when you create it directly with gwts shell skript?
>
> sry that this is no solution, just another thing to think about ...
>
> mfg nebenmir
>
>
>
> 2009/10/30 Ivan Martinez <supertrasgu@...>
>>
>> Hello all,
>> I have a GWT service with the following interface:
>>
>>
>> package es.mycompany.myapp.client;
>>
>> import java.util.Date;
>>
>> import es.mycompany.myapp.client.modelo.Area;
>> import es.mycompany.myapp.client.modelo.ComercialCorporate;
>> import es.mycompany.myapp.client.modelo.Tienda;
>> import com.google.gwt.user.client.rpc.AsyncCallback;
>>
>> public interface DirectorioTiendasServiceAsync {
>>
>> public void areas(Date fecha, AsyncCallback<Area[]> callback);
>>
>> public void tiendas(Date fecha, AsyncCallback<Tienda[]> callback);
>>
>> public void comercialesCorporate(Date fecha,
>> AsyncCallback<ComercialCorporate[]> callback);
>> }
>>
>>
>> Compiling with org.codehaus.mojo:gwt-maven-plugin:1.0:compile works
>> fine, but when I try to do a Maven package I get:
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\DirectorioTiendasServiceAsync.java:[11,7]
>> duplicate class:
>> es.mycompany.myapp.client.DirectorioTiendasServiceAsync
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaAreas.java:[62,36]
>>
>> areas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area>)
>> in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
>> applied to
>> (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area[]>)
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaTiendas.java:[90,36]
>>
>> tiendas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda>)
>> in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
>> applied to
>> (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda[]>)
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaComercialesCorporate.java:[67,36]
>>
>> comercialesCorporate(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate>)
>> in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
>> applied to
>> (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate[]>)
>>
>>
>> I have found that the definition of DirectorioTiendasServiceAsync in
>> target/generated-sources... is as follows:
>>
>>
>> package es.mycompany.myapp.client;
>>
>> import java.util.Date;
>> import com.google.gwt.core.client.GWT;
>> import com.google.gwt.user.client.rpc.RemoteServiceRelativePath;
>> import com.google.gwt.user.client.rpc.ServiceDefTarget;
>> import es.mycompany.myapp.client.modelo.Area;
>> import es.mycompany.myapp.client.modelo.ComercialCorporate;
>> import es.mycompany.myapp.client.modelo.Tienda;
>> import com.google.gwt.core.client.GWT;
>> import com.google.gwt.user.client.rpc.AsyncCallback;
>> import com.google.gwt.user.client.rpc.ServiceDefTarget;
>>
>> public interface DirectorioTiendasServiceAsync
>> {
>>
>> /**
>> * GWT-RPC service asynchronous (client-side) interface
>> * @see es.mycompany.myapp.client.DirectorioTiendasService
>> */
>> void areas( java.util.Date fecha, AsyncCallback<Area> callback );
>>
>> /**
>> * GWT-RPC service asynchronous (client-side) interface
>> * @see es.mycompany.myapp.client.DirectorioTiendasService
>> */
>> void tiendas( java.util.Date fecha, AsyncCallback<Tienda> callback );
>>
>> /**
>> * GWT-RPC service asynchronous (client-side) interface
>> * @see es.mycompany.myapp.client.DirectorioTiendasService
>> */
>> void comercialesCorporate( java.util.Date fecha,
>> AsyncCallback<ComercialCorporate> callback );
>>
>> /**
>> * Utility class to get the RPC Async interface from client-side code
>> */
>> public static class Util
>> {
>> private static DirectorioTiendasServiceAsync instance;
>>
>> public static DirectorioTiendasServiceAsync getInstance()
>> {
>> if ( instance == null )
>> {
>> instance = (DirectorioTiendasServiceAsync) GWT.create(
>> DirectorioTiendasService.class );
>> ServiceDefTarget target = (ServiceDefTarget) instance;
>> target.setServiceEntryPoint( GWT.getModuleBaseURL() +
>> "DirectorioTiendasService" );
>> }
>> return instance;
>> }
>> }
>> }
>>
>>
>> I think the cause of the problem is the mismatch in the definition of
>> the methods in both versions of DirectorioTiendasServiceAsync, the
>> original one has arrays and the generated one is missing them. The
>> weird thing is I had this problem before, then I don't know what I did
>> but it disappeared, and again I don't know why it is here again. Does
>> anyone know what the problem can be?. Thank you.
>> Iván Martínez
>>
>> ---------------------------------------------------------------------
>> 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: gwt-maven-plugin Package fails because of arrays in Interface

2009-11-02T03:11:47Z

Thank you, that worked.

On Fri, Oct 30, 2009 at 3:28 PM, nicolas de loof
<nicolas.deloof@...> wrote:

> If you manually create the Async interface you must disable the
> generateAsync goal in the plugin configuration
>
> 2009/10/30 Ivan Martinez <supertrasgu@...>
>>
>> Hello all,
>> I have a GWT service with the following interface:
>>
>>
>> package es.mycompany.myapp.client;
>>
>> import java.util.Date;
>>
>> import es.mycompany.myapp.client.modelo.Area;
>> import es.mycompany.myapp.client.modelo.ComercialCorporate;
>> import es.mycompany.myapp.client.modelo.Tienda;
>> import com.google.gwt.user.client.rpc.AsyncCallback;
>>
>> public interface DirectorioTiendasServiceAsync {
>>
>> public void areas(Date fecha, AsyncCallback<Area[]> callback);
>>
>> public void tiendas(Date fecha, AsyncCallback<Tienda[]> callback);
>>
>> public void comercialesCorporate(Date fecha,
>> AsyncCallback<ComercialCorporate[]> callback);
>> }
>>
>>
>> Compiling with org.codehaus.mojo:gwt-maven-plugin:1.0:compile works
>> fine, but when I try to do a Maven package I get:
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\DirectorioTiendasServiceAsync.java:[11,7]
>> duplicate class:
>> es.mycompany.myapp.client.DirectorioTiendasServiceAsync
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaAreas.java:[62,36]
>>
>> areas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area>)
>> in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
>> applied to
>> (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area[]>)
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaTiendas.java:[90,36]
>>
>> tiendas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda>)
>> in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
>> applied to
>> (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda[]>)
>>
>> D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
>> -
>> Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaComercialesCorporate.java:[67,36]
>>
>> comercialesCorporate(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate>)
>> in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
>> applied to
>> (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate[]>)
>>
>>
>> I have found that the definition of DirectorioTiendasServiceAsync in
>> target/generated-sources... is as follows:
>>
>>
>> package es.mycompany.myapp.client;
>>
>> import java.util.Date;
>> import com.google.gwt.core.client.GWT;
>> import com.google.gwt.user.client.rpc.RemoteServiceRelativePath;
>> import com.google.gwt.user.client.rpc.ServiceDefTarget;
>> import es.mycompany.myapp.client.modelo.Area;
>> import es.mycompany.myapp.client.modelo.ComercialCorporate;
>> import es.mycompany.myapp.client.modelo.Tienda;
>> import com.google.gwt.core.client.GWT;
>> import com.google.gwt.user.client.rpc.AsyncCallback;
>> import com.google.gwt.user.client.rpc.ServiceDefTarget;
>>
>> public interface DirectorioTiendasServiceAsync
>> {
>>
>> /**
>> * GWT-RPC service asynchronous (client-side) interface
>> * @see es.mycompany.myapp.client.DirectorioTiendasService
>> */
>> void areas( java.util.Date fecha, AsyncCallback<Area> callback );
>>
>> /**
>> * GWT-RPC service asynchronous (client-side) interface
>> * @see es.mycompany.myapp.client.DirectorioTiendasService
>> */
>> void tiendas( java.util.Date fecha, AsyncCallback<Tienda> callback );
>>
>> /**
>> * GWT-RPC service asynchronous (client-side) interface
>> * @see es.mycompany.myapp.client.DirectorioTiendasService
>> */
>> void comercialesCorporate( java.util.Date fecha,
>> AsyncCallback<ComercialCorporate> callback );
>>
>> /**
>> * Utility class to get the RPC Async interface from client-side code
>> */
>> public static class Util
>> {
>> private static DirectorioTiendasServiceAsync instance;
>>
>> public static DirectorioTiendasServiceAsync getInstance()
>> {
>> if ( instance == null )
>> {
>> instance = (DirectorioTiendasServiceAsync) GWT.create(
>> DirectorioTiendasService.class );
>> ServiceDefTarget target = (ServiceDefTarget) instance;
>> target.setServiceEntryPoint( GWT.getModuleBaseURL() +
>> "DirectorioTiendasService" );
>> }
>> return instance;
>> }
>> }
>> }
>>
>>
>> I think the cause of the problem is the mismatch in the definition of
>> the methods in both versions of DirectorioTiendasServiceAsync, the
>> original one has arrays and the generated one is missing them. The
>> weird thing is I had this problem before, then I don't know what I did
>> but it disappeared, and again I don't know why it is here again. Does
>> anyone know what the problem can be?. Thank you.
>> Iván Martínez
>>
>> ---------------------------------------------------------------------
>> 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: gwt-maven-plugin Package fails because of arrays in Interface

2009-11-01T21:51:13Z

I think the cause of the problem is the mismatch in the definition of
the methods in both versions of DirectorioTiendasServiceAsync, the
original one has arrays and the generated one is missing them.

ja, i think thats the problem. unfortunately i have no answer to that, just a question.
Does the gwt-maven-plugin generate the async interface for you (well it seems so because of the folder it lays in)? Does the async interface also miss the arrays when you create it directly with gwts shell skript?

sry that this is no solution, just another thing to think about ...

mfg nebenmir

2009/10/30 Ivan Martinez <supertrasgu@...>

Hello all,
I have a GWT service with the following interface:

package es.mycompany.myapp.client;

import java.util.Date;

import es.mycompany.myapp.client.modelo.Area;
import es.mycompany.myapp.client.modelo.ComercialCorporate;
import es.mycompany.myapp.client.modelo.Tienda;
import com.google.gwt.user.client.rpc.AsyncCallback;

public interface DirectorioTiendasServiceAsync {

public void areas(Date fecha, AsyncCallback<Area[]> callback);

public void tiendas(Date fecha, AsyncCallback<Tienda[]> callback);

public void comercialesCorporate(Date fecha,
AsyncCallback<ComercialCorporate[]> callback);
}

Compiling with org.codehaus.mojo:gwt-maven-plugin:1.0:compile works
fine, but when I try to do a Maven package I get:

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\DirectorioTiendasServiceAsync.java:[11,7]
duplicate class:
es.mycompany.myapp.client.DirectorioTiendasServiceAsync

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaAreas.java:[62,36]
areas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area[]>)

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaTiendas.java:[90,36]
tiendas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda[]>)

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaComercialesCorporate.java:[67,36]
comercialesCorporate(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate[]>)

I have found that the definition of DirectorioTiendasServiceAsync in
target/generated-sources... is as follows:

package es.mycompany.myapp.client;

import java.util.Date;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.client.rpc.RemoteServiceRelativePath;
import com.google.gwt.user.client.rpc.ServiceDefTarget;
import es.mycompany.myapp.client.modelo.Area;
import es.mycompany.myapp.client.modelo.ComercialCorporate;
import es.mycompany.myapp.client.modelo.Tienda;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.client.rpc.AsyncCallback;
import com.google.gwt.user.client.rpc.ServiceDefTarget;

public interface DirectorioTiendasServiceAsync
{

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void areas( java.util.Date fecha, AsyncCallback<Area> callback );

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void tiendas( java.util.Date fecha, AsyncCallback<Tienda> callback );

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void comercialesCorporate( java.util.Date fecha,
AsyncCallback<ComercialCorporate> callback );

/**
* Utility class to get the RPC Async interface from client-side code
*/
public static class Util
{
private static DirectorioTiendasServiceAsync instance;

public static DirectorioTiendasServiceAsync getInstance()
{
if ( instance == null )
{
instance = (DirectorioTiendasServiceAsync) GWT.create(
DirectorioTiendasService.class );
ServiceDefTarget target = (ServiceDefTarget) instance;
target.setServiceEntryPoint( GWT.getModuleBaseURL() +
"DirectorioTiendasService" );
}
return instance;
}
}
}

I think the cause of the problem is the mismatch in the definition of
the methods in both versions of DirectorioTiendasServiceAsync, the
original one has arrays and the generated one is missing them. The
weird thing is I had this problem before, then I don't know what I did
but it disappeared, and again I don't know why it is here again. Does
anyone know what the problem can be?. Thank you.
Iván Martínez

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

http://xircles.codehaus.org/manage_email

Re: maven-tomcat-plugin and the 'system' classpath

2009-10-30T17:02:19Z

Never mind that. MTOMCAT-39 is your test case.

On Fri, Oct 30, 2009 at 7:03 PM, Benson Margulies <bimargulies@...> wrote:

In trying to set up a test case, I seem to have hit MTOMCAT-6. dependency:tree shows no sign of the wrong servlet apis. I've got the geronimo servet api artifact in my project.

On Fri, Oct 30, 2009 at 5:49 PM, Olivier Lamy <olamy@...> wrote:

Hi,
Yes the plugin classLoader is used to start tomcat because tomcat
dependencies comes from the plugin dependencies.
What we could do is to create a classLoader with all tomcat deps (ones
with groupId : org.apache.tomcat ) and start tomcat with.
But as I don't have any sample project it's difficult to work on this.
Can you record an issue in http://jira.codehaus.org/browse/MTOMCAT ?
(and include a test project which reproduce the issue)

Thanks,
--
Olivier

2009/10/29 Benson Margulies <bimargulies@...>:

> I've hit what seems to be a problem with classpath management with the
> maven-tomcat-plugin.
>
> I have a webapp that includes xercesImpl 2.9.1.
>
> It includes some code that builds a DOM tree with XML Schema validation
> turned on.
>
> This all works fine when the code is run in a POJO unit test.
>
> Run from inside the webapp by tomcat:run, it fails. The failure mode seems
> to result from the use of a strange hybrid of building JDK JAXP classes and
> the xerces classes.
>
> I eventually got my code to work by introducing the JAXP 1.4 APIs to the
> webapp and then calling the newInstance(...) methods that allow me to very
> explicitly specify Xerces.
>
> My theory here is that the 'system' classpath of tomcat in the plugin is
> maven's classpath, not the project's classpath or a clean classpath. There's
> some loopy old version of xml-apis or something else on that classpath
> causing all this chaos.
>
> I suggest that the plugin should load tomcat, insofar as possible, in a
> clean classloader, or even a classloader with the same things in it as show
> up by default in the lib directory of the relevant version of tomcat.
>
>
>

--
Olivier

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

http://xircles.codehaus.org/manage_email

Re: maven-tomcat-plugin and the 'system' classpath

2009-10-30T16:03:19Z

In trying to set up a test case, I seem to have hit MTOMCAT-6. dependency:tree shows no sign of the wrong servlet apis. I've got the geronimo servet api artifact in my project.

On Fri, Oct 30, 2009 at 5:49 PM, Olivier Lamy <olamy@...> wrote:

Hi,
Yes the plugin classLoader is used to start tomcat because tomcat
dependencies comes from the plugin dependencies.
What we could do is to create a classLoader with all tomcat deps (ones
with groupId : org.apache.tomcat ) and start tomcat with.
But as I don't have any sample project it's difficult to work on this.
Can you record an issue in http://jira.codehaus.org/browse/MTOMCAT ?
(and include a test project which reproduce the issue)

Thanks,
--
Olivier

2009/10/29 Benson Margulies <bimargulies@...>:

> I've hit what seems to be a problem with classpath management with the
> maven-tomcat-plugin.
>
> I have a webapp that includes xercesImpl 2.9.1.
>
> It includes some code that builds a DOM tree with XML Schema validation
> turned on.
>
> This all works fine when the code is run in a POJO unit test.
>
> Run from inside the webapp by tomcat:run, it fails. The failure mode seems
> to result from the use of a strange hybrid of building JDK JAXP classes and
> the xerces classes.
>
> I eventually got my code to work by introducing the JAXP 1.4 APIs to the
> webapp and then calling the newInstance(...) methods that allow me to very
> explicitly specify Xerces.
>
> My theory here is that the 'system' classpath of tomcat in the plugin is
> maven's classpath, not the project's classpath or a clean classpath. There's
> some loopy old version of xml-apis or something else on that classpath
> causing all this chaos.
>
> I suggest that the plugin should load tomcat, insofar as possible, in a
> clean classloader, or even a classloader with the same things in it as show
> up by default in the lib directory of the relevant version of tomcat.
>
>
>

--
Olivier

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

http://xircles.codehaus.org/manage_email

Re: maven-tomcat-plugin and the 'system' classpath

2009-10-30T14:59:42Z

Can do.

On Fri, Oct 30, 2009 at 5:49 PM, Olivier Lamy <olamy@...> wrote:

Hi,
Yes the plugin classLoader is used to start tomcat because tomcat
dependencies comes from the plugin dependencies.
What we could do is to create a classLoader with all tomcat deps (ones
with groupId : org.apache.tomcat ) and start tomcat with.
But as I don't have any sample project it's difficult to work on this.
Can you record an issue in http://jira.codehaus.org/browse/MTOMCAT ?
(and include a test project which reproduce the issue)

Thanks,
--
Olivier

2009/10/29 Benson Margulies <bimargulies@...>:

> I've hit what seems to be a problem with classpath management with the
> maven-tomcat-plugin.
>
> I have a webapp that includes xercesImpl 2.9.1.
>
> It includes some code that builds a DOM tree with XML Schema validation
> turned on.
>
> This all works fine when the code is run in a POJO unit test.
>
> Run from inside the webapp by tomcat:run, it fails. The failure mode seems
> to result from the use of a strange hybrid of building JDK JAXP classes and
> the xerces classes.
>
> I eventually got my code to work by introducing the JAXP 1.4 APIs to the
> webapp and then calling the newInstance(...) methods that allow me to very
> explicitly specify Xerces.
>
> My theory here is that the 'system' classpath of tomcat in the plugin is
> maven's classpath, not the project's classpath or a clean classpath. There's
> some loopy old version of xml-apis or something else on that classpath
> causing all this chaos.
>
> I suggest that the plugin should load tomcat, insofar as possible, in a
> clean classloader, or even a classloader with the same things in it as show
> up by default in the lib directory of the relevant version of tomcat.
>
>
>

--
Olivier

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

http://xircles.codehaus.org/manage_email

Re: maven-tomcat-plugin and the 'system' classpath

2009-10-30T14:49:26Z

Hi,
Yes the plugin classLoader is used to start tomcat because tomcat
dependencies comes from the plugin dependencies.
What we could do is to create a classLoader with all tomcat deps (ones
with groupId : org.apache.tomcat ) and start tomcat with.
But as I don't have any sample project it's difficult to work on this.
Can you record an issue in http://jira.codehaus.org/browse/MTOMCAT ?
(and include a test project which reproduce the issue)

Thanks,
--
Olivier

2009/10/29 Benson Margulies <bimargulies@...>:

> I've hit what seems to be a problem with classpath management with the
> maven-tomcat-plugin.
>
> I have a webapp that includes xercesImpl 2.9.1.
>
> It includes some code that builds a DOM tree with XML Schema validation
> turned on.
>
> This all works fine when the code is run in a POJO unit test.
>
> Run from inside the webapp by tomcat:run, it fails. The failure mode seems
> to result from the use of a strange hybrid of building JDK JAXP classes and
> the xerces classes.
>
> I eventually got my code to work by introducing the JAXP 1.4 APIs to the
> webapp and then calling the newInstance(...) methods that allow me to very
> explicitly specify Xerces.
>
> My theory here is that the 'system' classpath of tomcat in the plugin is
> maven's classpath, not the project's classpath or a clean classpath. There's
> some loopy old version of xml-apis or something else on that classpath
> causing all this chaos.
>
> I suggest that the plugin should load tomcat, insofar as possible, in a
> clean classloader, or even a classloader with the same things in it as show
> up by default in the lib directory of the relevant version of tomcat.
>
>
>

--
Olivier

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

http://xircles.codehaus.org/manage_email

[ANN] Versions Maven Plugin 1.1 released

2009-10-30T14:31:18Z

he Mojo team is pleased to announce the release of the Versions Maven
Plugin, version 1.1.

The Versions Plugin has the following goals.

* versions:display-dependency-updates scans a project's
dependencies and produces a report of those dependencies which have
newer versions available.
* versions:display-plugin-updates scans a project's plugins and
produces a report of those plugins which have newer versions
available.
* versions:display-property-updates scans a projectand produces a
report of those properties which are used to control artifact versions
and which properies have newer versions available.
* versions:update-parent updates the parent section of a project
so that it references the newest available version. For example, if
you use a corporate root POM, this goal can be helpful if you need to
ensure you are using the latest version of the corporate root POM.
* versions:update-properties updates properties defined in a
project so that they correspond to the latest available version of
specific dependencies. This can be useful if a suite of dependencies
must all be locked to one version.
* versions:update-child-modules updates the parent section of the
child modules of a project so the version matches the version of the
current project. For example, if you have an aggregator pom that is
also the parent for the projects that it aggregates and the children
and parent versions get out of sync, this mojo can help fix the
versions of the child modules. (Note you may need to invoke Maven with
the -N option in order to run this goal if your project is broken so
badly that it cannot build because of the version mis-match).
* versions:lock-snapshots searches the pom for all -SNAPSHOT
versions and replaces them with the current timestamp version of that
-SNAPSHOT, e.g. -20090327.172306-4
* versions:unlock-snapshots searches the pom for all timestamp
locked snapshot versions and replaces them with -SNAPSHOT.
* versions:resolve-ranges finds dependencies using version ranges
and resolves the range to the specific version being used.
* versuibs:set can be used to set the project version from the command line.
* versions:use-releases searches the pom for all -SNAPSHOT
versions which have been released and replaces them with the
corresponding release version.
* versions:use-next-releases searches the pom for all non-SNAPSHOT
versions which have been a newer release and replaces them with the
next release version.
* versions:use-latest-releases searches the pom for all
non-SNAPSHOT versions which have been a newer release and replaces
them with the latest release version.
* versions:use-next-snapshots searches the pom for all
non-SNAPSHOT versions which have been a newer -SNAPSHOT version and
replaces them with the next -SNAPSHOT version.
* versions:use-latest-snapshots searches the pom for all
non-SNAPSHOT versions which have been a newer -SNAPSHOT version and
replaces them with the latest -SNAPSHOT version.
* versions:use-next-versions searches the pom for all versions
which have been a newer version and replaces them with the next
version.
* versions:use-latest-versions searches the pom for all versions
which have been a newer version and replaces them with the latest
version.
* versions:commit removes the pom.xml.versionsBackup files. Forms
one half of the built-in "Poor Man's SCM".
* versions:revert restores the pom.xml files from the
pom.xml.versionsBackup files. Forms one half of the built-in "Poor
Man's SCM".

The artifacts have been deployed to the mojo repository and have been
mirrored to central.

The Mojo Team.

Release Notes - Maven 2.x Versions Plugin - Version 1.1

** Bug
* [MVERSIONS-66] - FATAL Error thrown for
versions:dependency-updates-report GOAL
* [MVERSIONS-67] - Reporting IllegalArgumentException plugin
comparator used for normal dependencies
* [MVERSIONS-71] - versions:set changes both parent and module version
* [MVERSIONS-75] - Spelling error
* [MVERSIONS-80] - update-properties doesn't work when version is
specified in plugin configuration

** Improvement
* [MVERSIONS-72] - versions-maven-plugin should determine POM
encoding from property/configuration entry
* [MVERSIONS-73] - Documentation should provide a matrix table
showing what the different goals do exactly

Note: as of 21:22 GMT 30/10/2009 the versions-maven-plugin has not
been pushed to maven central. If you cannot wait the (at most) 24
hours for this sync, you can use the codehaus repository
(http://repository.codehaus.org/).

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

http://xircles.codehaus.org/manage_email

Re: gwt-maven-plugin Package fails because of arrays in Interface

2009-10-30T07:28:25Z

If you manually create the Async interface you must disable the generateAsync goal in the plugin configuration

2009/10/30 Ivan Martinez <supertrasgu@...>

Hello all,
I have a GWT service with the following interface:

package es.mycompany.myapp.client;

import java.util.Date;

import es.mycompany.myapp.client.modelo.Area;
import es.mycompany.myapp.client.modelo.ComercialCorporate;
import es.mycompany.myapp.client.modelo.Tienda;
import com.google.gwt.user.client.rpc.AsyncCallback;

public interface DirectorioTiendasServiceAsync {

public void areas(Date fecha, AsyncCallback<Area[]> callback);

public void tiendas(Date fecha, AsyncCallback<Tienda[]> callback);

public void comercialesCorporate(Date fecha,
AsyncCallback<ComercialCorporate[]> callback);
}

Compiling with org.codehaus.mojo:gwt-maven-plugin:1.0:compile works
fine, but when I try to do a Maven package I get:

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\DirectorioTiendasServiceAsync.java:[11,7]
duplicate class:
es.mycompany.myapp.client.DirectorioTiendasServiceAsync

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaAreas.java:[62,36]
areas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area[]>)

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaTiendas.java:[90,36]
tiendas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda[]>)

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaComercialesCorporate.java:[67,36]
comercialesCorporate(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate[]>)

I have found that the definition of DirectorioTiendasServiceAsync in
target/generated-sources... is as follows:

package es.mycompany.myapp.client;

import java.util.Date;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.client.rpc.RemoteServiceRelativePath;
import com.google.gwt.user.client.rpc.ServiceDefTarget;
import es.mycompany.myapp.client.modelo.Area;
import es.mycompany.myapp.client.modelo.ComercialCorporate;
import es.mycompany.myapp.client.modelo.Tienda;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.client.rpc.AsyncCallback;
import com.google.gwt.user.client.rpc.ServiceDefTarget;

public interface DirectorioTiendasServiceAsync
{

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void areas( java.util.Date fecha, AsyncCallback<Area> callback );

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void tiendas( java.util.Date fecha, AsyncCallback<Tienda> callback );

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void comercialesCorporate( java.util.Date fecha,
AsyncCallback<ComercialCorporate> callback );

/**
* Utility class to get the RPC Async interface from client-side code
*/
public static class Util
{
private static DirectorioTiendasServiceAsync instance;

public static DirectorioTiendasServiceAsync getInstance()
{
if ( instance == null )
{
instance = (DirectorioTiendasServiceAsync) GWT.create(
DirectorioTiendasService.class );
ServiceDefTarget target = (ServiceDefTarget) instance;
target.setServiceEntryPoint( GWT.getModuleBaseURL() +
"DirectorioTiendasService" );
}
return instance;
}
}
}

I think the cause of the problem is the mismatch in the definition of
the methods in both versions of DirectorioTiendasServiceAsync, the
original one has arrays and the generated one is missing them. The
weird thing is I had this problem before, then I don't know what I did
but it disappeared, and again I don't know why it is here again. Does
anyone know what the problem can be?. Thank you.
Iván Martínez

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

http://xircles.codehaus.org/manage_email

gwt-maven-plugin Package fails because of arrays in Interface

2009-10-30T05:52:48Z

Hello all,
I have a GWT service with the following interface:

package es.mycompany.myapp.client;

import java.util.Date;

import es.mycompany.myapp.client.modelo.Area;
import es.mycompany.myapp.client.modelo.ComercialCorporate;
import es.mycompany.myapp.client.modelo.Tienda;
import com.google.gwt.user.client.rpc.AsyncCallback;

public interface DirectorioTiendasServiceAsync {

public void areas(Date fecha, AsyncCallback<Area[]> callback);

public void tiendas(Date fecha, AsyncCallback<Tienda[]> callback);

public void comercialesCorporate(Date fecha,
AsyncCallback<ComercialCorporate[]> callback);
}

Compiling with org.codehaus.mojo:gwt-maven-plugin:1.0:compile works
fine, but when I try to do a Maven package I get:

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\DirectorioTiendasServiceAsync.java:[11,7]
duplicate class:
es.mycompany.myapp.client.DirectorioTiendasServiceAsync

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaAreas.java:[62,36]
areas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Area[]>)

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaTiendas.java:[90,36]
tiendas(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.Tienda[]>)

D:\Documents and Settings\martini06\Mis documentos\Mis proyectos\DT\3
- Construcción\myapp\src\main\java\es\mycompany\myapp\client\paneles\TablaComercialesCorporate.java:[67,36]
comercialesCorporate(java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate>)
in es.mycompany.myapp.client.DirectorioTiendasServiceAsync cannot be
applied to (java.util.Date,com.google.gwt.user.client.rpc.AsyncCallback<es.mycompany.myapp.client.modelo.ComercialCorporate[]>)

I have found that the definition of DirectorioTiendasServiceAsync in
target/generated-sources... is as follows:

package es.mycompany.myapp.client;

import java.util.Date;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.client.rpc.RemoteServiceRelativePath;
import com.google.gwt.user.client.rpc.ServiceDefTarget;
import es.mycompany.myapp.client.modelo.Area;
import es.mycompany.myapp.client.modelo.ComercialCorporate;
import es.mycompany.myapp.client.modelo.Tienda;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.client.rpc.AsyncCallback;
import com.google.gwt.user.client.rpc.ServiceDefTarget;

public interface DirectorioTiendasServiceAsync
{

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void areas( java.util.Date fecha, AsyncCallback<Area> callback );

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void tiendas( java.util.Date fecha, AsyncCallback<Tienda> callback );

/**
* GWT-RPC service asynchronous (client-side) interface
* @see es.mycompany.myapp.client.DirectorioTiendasService
*/
void comercialesCorporate( java.util.Date fecha,
AsyncCallback<ComercialCorporate> callback );

/**
* Utility class to get the RPC Async interface from client-side code
*/
public static class Util
{
private static DirectorioTiendasServiceAsync instance;

public static DirectorioTiendasServiceAsync getInstance()
{
if ( instance == null )
{
instance = (DirectorioTiendasServiceAsync) GWT.create(
DirectorioTiendasService.class );
ServiceDefTarget target = (ServiceDefTarget) instance;
target.setServiceEntryPoint( GWT.getModuleBaseURL() +
"DirectorioTiendasService" );
}
return instance;
}
}
}

I think the cause of the problem is the mismatch in the definition of
the methods in both versions of DirectorioTiendasServiceAsync, the
original one has arrays and the generated one is missing them. The
weird thing is I had this problem before, then I don't know what I did
but it disappeared, and again I don't know why it is here again. Does
anyone know what the problem can be?. Thank you.
Iván Martínez

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

http://xircles.codehaus.org/manage_email

Maven versions plugin - Questions regarding updating versions in branches

2009-10-29T17:14:49Z

---------- Forwarded message ----------
From: Børge Haugsdal <borge.haugsdal@...>
Date: 2009/10/30
Subject: Maven versions plugin - Questions regarding updating versions in branches
To: user@...

We have now more that 50 multi-module projects to manage each with 2-10 sub-modules.

The list is growing fast.

In out project we have a lot of dependencies between projects, so tagging and version management makes a lot of work, and creates a lot of hassle.

And we have right now 4 complete branches to manage at the same time.

I have tried now making scripts (shell and .bat) to handle the tagging process. And it works.

I must say that the versions plugin has saved us for a lot of work.

All version information is stored in properties like <logging.version>33.1.1</logging.version> in each multimodule pom.xml
All groupIds in our internal projects is made in the format <groupId>no.mycompany.area</groupId>

Tagging TRUNK using scripts - solved

When we tag the TRUNK we always tag all code if changes has been made in a module, and updates all modules to the latest versions of our internal dependencies.

So, we are able to automate the process just by listing the projects to tag in a given order, and then calling scripts to tag and update versions dependencies.

So the TRUNK is no problem anymore, much thanks to the maven versions plugin.

Tagging BRANCHES using scripts - still a problem

When it comes to the BRANCHES we still have problems.
I know that in the versions plugin it is possible to update to the newest versions using ranges defined in the poms.
But it seems to me like have to change each pom for each time we create a branch with range information, and add our dependencies twice in the pom, once in dependency list and once in the plugin def. itself.

As far as I have understood the process...
So the pom grows and it becomes more work to manage it. .
I hope I can do this without doing a lot of changes in the poms.

I hope I can script tagging of branches too.
When we are working in trunk we have the same majorVersion and minorVersion in all projects. Like 33.1.X

When we create a new branch from trunk, we update the versions in the TRUNK poms. Like 34.1.0

So in our branch coming from the trunk version 33.1.X we want to always use the latest release or snapshot versions in the range 33.1.0.0 to 34.0.0

So (finally) my question is:
Is there a way that I from a script/command-line can specify that for a given groupId I want to update all versions stored in the pom (in <properties>) for all of our dependencies, with versions higher that 33.1.0.0 and less that 34.0.0

Example update to latest RELEASE version of all our artifacts in the branch:
mvn versions:update-properties -DGroupId=no.<mycompany> -DVersionRange=[33.1.0.0,34.0.0)

Example update to latest SNAPSHOT version of all our artifacts in the branch:
mvn versions:update-properties -DGroupId=no.<mycompany> -DVersionRange=[33.1.0,34.0.0) -DallowSnapshot -DexcludePeroperties="XX.version,YY.version"

Is something like this possible?
What is the best solution for this?

I hope you can help me out here.

Another, and less important question.

It would be nice to have a command like this:
mvn versions:update-properties -DGroupId=no.<mycompany> -DVersionRange=[33.1.0,33.2.0) -DallowSnapshots -DexcludeGroupIds="no-<mycompany>.common"

Right now the excludeProterties is growing fast.

All of our modules always in stable versions has a common groupId like above. The list with dependencies to exclude is growing, so I hope for an easier way.

I hope you have time for my questions...

Best Regards

Børge Haugsdal

--
Hilsen

Børge Haugsdal

maven-tomcat-plugin and the 'system' classpath

2009-10-29T14:26:53Z

I've hit what seems to be a problem with classpath management with the maven-tomcat-plugin.

I have a webapp that includes xercesImpl 2.9.1.

It includes some code that builds a DOM tree with XML Schema validation turned on.

This all works fine when the code is run in a POJO unit test.

Run from inside the webapp by tomcat:run, it fails. The failure mode seems to result from the use of a strange hybrid of building JDK JAXP classes and the xerces classes.

I eventually got my code to work by introducing the JAXP 1.4 APIs to the webapp and then calling the newInstance(...) methods that allow me to very explicitly specify Xerces.

My theory here is that the 'system' classpath of tomcat in the plugin is maven's classpath, not the project's classpath or a clean classpath. There's some loopy old version of xml-apis or something else on that classpath causing all this chaos.

I suggest that the plugin should load tomcat, insofar as possible, in a clean classloader, or even a classloader with the same things in it as show up by default in the lib directory of the relevant version of tomcat.

Maven rpm plug-in and sha1header collision

2009-10-28T08:46:50Z

Hi,

My name is Dudley Fox, and I am a developer at PayPal. We have happily been using the maven rpm plug-in for one of our current projects, and we are running into a small problem. I was hoping the users list could help us out.

We have a.rpm and b.rpm. And we have user_a and user_b.

We install a.rpm as user_a, and then b.rpm as user_b. The installation of b.rpm fails, because it does not have permission to overwrite a Sha1header, which is created when you have files under your %files section.

We know we can fix this if we use something like: %files -f $PWD/$Name.list

However we don't see a way using the maven rpm plug-in to achieve this.

If we cannot find a way within the existing plug-in to overcome this problem, we will have to modify the plug-in to allow for the -f option. We'd prefer not to do this, since it will take a lot of time.

Sincerely,

Dudley Fox

Re: hibernate3-maven-plugin stuck in 3.0-SNAPSHOT

2009-10-26T07:24:29Z

Ryan Stewart wrote:

I'm trying to add the hibernate3-maven-plugin to a new project, but even though I've declared <version>2.2</version>, it keeps downloading and using 3.0-SNAPSHOT

My mistake--I had the plugin defined in a profiles/build instead of in build, and that profile wasn't active. Sorry for the noise.

hibernate3-maven-plugin stuck in 3.0-SNAPSHOT

2009-10-26T06:26:02Z

I'm trying to add the hibernate3-maven-plugin to a new project, but even though I've declared <version>2.2</version>, it keeps downloading and using 3.0-SNAPSHOT and giving me the following error. I don't know what it means, and I don't know why it insists on using 3.0-SNAPSHOT:

[INFO] One or more required plugin parameters are invalid/missing for 'hibernate3:hbm2ddl'

[0] Inside the definition for plugin 'hibernate3-maven-plugin' specify the following:

<configuration>
...
<hibernatetool>VALUE</hibernatetool>
</configuration>

-OR-

on the command line, specify: '-Dhibernatetool=VALUE'

Re: gwt-maven-plugin - Client can't find server in Jboss

2009-10-26T06:06:43Z

Solved, I just published the service where the client expects it to be:

<url-pattern>/es.company.gwtlogin.GWTLogin/GWTLoginService</url-pattern>

On Thu, Oct 22, 2009 at 9:33 AM, Ivan Martinez <supertrasgu@...> wrote:

> Hello all,
> I have an app with the following module definition:
>
> <?xml version="1.0" encoding="windows-1252"?>
> <module>
> 
> <inherits name="com.google.gwt.user.User"/>
> <inherits name="com.smartgwt.SmartGwt"/>
> <entry-point class="es.company.gwtlogin.client.GWTLogin"/>
> <servlet class="es.company.gwtlogin.server.GWTLoginServiceImpl"
> path="/GWTLoginService"/>
> </module>
>
> "web.xml" is as follows:
>
> <!DOCTYPE web-app PUBLIC
> "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> "http://java.sun.com/dtd/web-app_2_3.dtd" >
> <web-app>
> <display-name>GWT-Maven-Archetype</display-name>
> <servlet>
> <servlet-name>GWTLoginService</servlet-name>
> <servlet-class>es.company.gwtlogin.server.GWTLoginServiceImpl</servlet-class>
> </servlet>
> <servlet-mapping>
> <servlet-name>GWTLoginService</servlet-name>
> <url-pattern>/GWTLoginService</url-pattern>
> </servlet-mapping>
> <welcome-file-list>
> <welcome-file>index.html</welcome-file>
> </welcome-file-list>
> </web-app>
>
> "pom.xml" defines a final name as follows:
>
> ...
> <finalName>GWTLogin</finalName>
> ...
>
> This works fine when I debug in hosted mode, the URL of the app is:
>
> http://localhost:8888/es.company.gwtlogin.GWTLogin/GWTLogin.html
>
> The problem is when I package and deploy to JBoss, I open the app as follows:
>
> http://localhost:8080/GWTLogin
>
> Which re-directs to:
>
> http://localhost:8080/GWTLogin/es.company.gwtlogin.GWTLogin/GWTLogin.html
>
> But then when I try to invoke a method of the server from the client I
> get the following error:
>
> JBossWeb/2.0.1.GA - Informe de Error
> Estado HTTP 404 - /GWTLogin/es.company.gwtlogin.GWTLogin/GWTLoginService
> Informe de estado
> mensaje
> /GWTLogin/es.company.gwtlogin.GWTLogin/GWTLoginService
> descripción
> El recurso requerido
> (/GWTLogin/es.company.gwtlogin.GWTLogin/GWTLoginService) no está
> disponible.
>
> It says it can't find
> "/GWTLogin/es.company.gwtlogin.GWTLogin/GWTLoginService". I found the
> server actually exists in the following URL:
>
> http://localhost:8080/GWTLogin/GWTLoginService
>
> How can I make the client find the server?. I guess I have something
> wrong or missing in my web.xml.
>
> Thank you,
> Ivan
>

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

http://xircles.codehaus.org/manage_email

Re: unable to load resource with webstart-maven-plugin

2009-10-23T14:30:25Z

On Fri, Oct 23, 2009 at 12:11 PM, stevenmaring <steve.maring@...> wrote:

>>
>> <jnlp spec="1.0+" codebase="$$codebase" context="$$context"
>> href="$$name">
>> <information>
>> <title>Release Deployer WebStart</title>
>> <vendor>Name</vendor>
>> <homepage href="http://maven.apache.org"/>
>> <description>$project.Description</description>
>> <offline-allowed/>
>> </information>
>> <security>
>> <all-permissions/>
>> </security>
>> <resources>
>> <j2se version="1.5+"/>
>> <jar href="release-deployer.jar" version="1.0.0" main="true"/>
>> </resources>
>> <application-desc main-class="com.example.MyMain"/>
>> </jnlp>
>>
>>
>> Thanks,
>> Steve Maring

I can't help you with the theory about why this is failing but if you just want it to work... if you remove the version property from the jar element and reference the real jar name with the version, it should work. So change:

<jar href="release-deployer.jar" version="1.0.0" main="true"/>

to

<jar href="release-deployer-1.0.0.jar" main="true"/>

in your .jnlp file.

Also, this will be how the JNLP will be generated if you set

<outputJarVersions>false</outputJarVersions>

in the jnlp section of your pom.xml.

Andy