nicolas de loof
Hi folks,
we already discussed that in june but no action where taken
I've created http://jira.codehaus.org/browse/HAUS-2138 to get canonical git
repo for gwt-maven plugin hosted at codehaus
I'll then migrate the gwt-maven mojo to this repo. I didn't found a magic
recipe to get github two way mir
:
> > Sent: Thursday, September 29, 2011 6:24 PM
> > Subject: Re: [mojo-dev] [VOTE] Invite Jesse Farinacci as mojo committer
> >
> > +1
> >
> > /Anders
> >
> > On Thu, Sep 29, 2011 at 15:23, Julien Ponge
> > wrote:
> >> +1 as you
Vote passed with .. many +1 and no objection
I've released the staging repository
2011/9/30 Olivier Lamy
> +1 (don't miss to publish the web site :-) )
>
> 2011/9/29 nicolas de loof :
> > Hi folks,
> > last release was in june, time to release a new version of
es that I had seen posted
> here. If those issues have all been resolved, please accept my apologies and
> I will gladly update the wiki.
>
> Thanks again to Nicolas and the gwt-maven-plugin community for maintaining
> the plugin itself.
>
> /dmc
>
> On Thu, Sep 29, 2011 at
> I know they don't use maven themselve, so maybe they just don't care.
>>
>
> They're talking about moving GWT's build system from Ant to Maven:
> https://plus.google.com/110412141990454266397/posts/1jMpBuDRyMw
>
>
Good news, wait & see
ven-plugin and propose a working
archetype
>
> Thanks!
>
> On Thu, Sep 29, 2011 at 8:12 AM, nicolas de loof > wrote:
>
>> Hi folks,
>>
>> last release was in june, time to release a new version of gwt-maven,
>> especially with gwt 2.4 out
>>
>
Hi,
I'd like to invite Jesse Farinacci as a mojo committer, so that I won't have
anymore to merge his pull requests :P
He contributed already to various mojos for a while, time to let him join
the team
vote is opened for 72h
Hi folks,
last release was in june, time to release a new version of gwt-maven,
especially with gwt 2.4 out
staging repo :
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-002/
release note : http://jira.codehaus.org/browse/MGWT/fixforversion/17402
vote is opened for 72h
upgrade to gwt 2.4.0
Key: MGWT-316
URL: https://jira.codehaus.org/browse/MGWT-316
Project: Maven 2.x GWT Plugin
Issue Type: Task
Reporter: nicolas de loof
--
This message is automatically generated by
[
https://jira.codehaus.org/browse/MGWT-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-316.
Resolution: Fixed
Fix Version/s: 2.4.0
Assignee: nicolas de loof
> upgrade to gwt 2.
[
https://jira.codehaus.org/browse/MGWT-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-308.
Resolution: Fixed
Fix Version/s: 2.4.0
fixed by https://github.com/gwt-maven-plugin/gwt-maven
2011/8/29 Christopher Hunt
> On 30/08/2011, at 4:09 AM, Jesse McConnell wrote:
>
> > I think the github bit is part of the issue, also I think the release
> > process should be left up to the plugin at this point and mojo's ought
> > to do away with the whole vote, wait a couple of days, release
Right, I've released the staged repo
will try to fixe the site now
cheers,
Nicolas
2011/7/9 Thomas Broyer
> Oh no, it doesn't impact my +1! ;-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Codehaus Mojo gwt-maven-plugin Users" group.
> To view this discu
Right, this "what's new" is a manual process, we must improve this
Would you like to stop the release for this or can we wait for next one (in
one month or so) to get a better site design ?
2011/7/8 Thomas Broyer
> Oh, just saw that the "what's new in 2.3.0-1" doesn't match the release
> notes
I did the release form the github hosting repository
2011/7/8 Olivier Lamy
> Ditto !
> /me wonder where is the tag ?? cannot find it here :
> http://svn.codehaus.org/mojo/tags/
>
>
>
> 2011/7/7 Olivier Lamy :
> > +1
> >
> > 2011/7/6 nicolas de loof
That right, Nexus as a group for staging repos, so you can add it to a
profile in your settings for simplified testing when we push a release
2011/7/7 Fotos Georgiadis
> +1
>
> Tested the new version with two of our projects and everything looks ok.
>
> PS. I am not really familiar with the rele
As I promised, I've pushed a new release of gwt-maven-plugin to staging
--> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-003/
and we now have a release note :
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11860&version=17403
site is also unpdated (upload in progress
[
https://jira.codehaus.org/browse/MGWT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MGWT-301:
Assignee: nicolas de loof
> The plugin is too sensitive to changes in unrelated parts o
[
https://jira.codehaus.org/browse/MGWT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-301.
Resolution: Fixed
Fix Version/s: 2.3.0-1
patch applied
> The plugin is too sensitive to chan
>
>
>>
>> I am a bit unsure as to what is the expected gain wrt moving the
> /authorative/ repo to github. I've said this earlier;
> an authorative repo located at codehaus with mirroring to github is
> practically the same. Handling pull requests is the only
> difference I can think of but it sho
2011/6/23 Mark Struberg
> generally I'm
>
> +1 for moving the repos from SVN to GIT
>
> -1 for moving the repo from codehaus.org to github.
> Reason is that this would _heavily_ fragment this established community.
> Why not just setup a GIT repo at codehaus? This is pretty easy, I could
> volu
[
http://jira.codehaus.org/browse/MGWT-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270372#comment-270372
]
nicolas de loof commented on MGWT-300:
--
Would you like to contribute a fix ?
We have move
[
http://jira.codehaus.org/browse/MGWT-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270282#comment-270282
]
nicolas de loof commented on MGWT-299:
--
gwt-maven plugin only lanch the sdk compiler
[
http://jira.codehaus.org/browse/MGWT-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-298.
Resolution: Fixed
Fix Version/s: 2.3.0-1
> StringIndexOutOfBoundsException when call gwt:resour
[
http://jira.codehaus.org/browse/MGWT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-277.
Resolution: Fixed
Fixed, thx
> add new gwt compiler option : -dep
[
http://jira.codehaus.org/browse/MGWT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269887#action_269887
]
nicolas de loof commented on MGWT-277:
--
Would you like to provide a fix by yourself ? Ei
[
http://jira.codehaus.org/browse/MGWT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reopened MGWT-277:
--
> add new gwt compiler option : -deploy
> -
>
>
Right,
thanks guys, I've released the staged repo
Next release in few weeks (at most)
2011/6/8 nicolas de loof
> I promise, and I'm not joking :D
>
> 2011/6/8 Thomas Broyer
>
>> OK, cast my vote to a "0" then, as there are workarounds. But only i
[
http://jira.codehaus.org/browse/MGWT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-277.
Resolution: Fixed
Fix Version/s: (was: 2.2.0-1)
2.3.0-1
Assignee
I promise, and I'm not joking :D
2011/6/8 Thomas Broyer
> OK, cast my vote to a "0" then, as there are workarounds. But only if you
> promise to release more often ;-) (joking!)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Codehaus Mojo gwt-maven-plugin U
[
http://jira.codehaus.org/browse/MGWT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269803#action_269803
]
nicolas de loof commented on MGWT-186:
--
I've setup a job to check build with maven2 a
What if someone complains about another unresolved issue next week ? Shall
we postpone a release until everything gets fixed ?
I'd like to get more release on this plugin, with smaller changes. We can
plan a new release in few weeks, maybe even adopt a jenkins-like release
cycle, but the major com
[
http://jira.codehaus.org/browse/MGWT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MGWT-284:
-
Fix Version/s: 2.3.0-1
> Goal "gwt:eclipse" generates buggy launch
Does this mean you vote +1 for a release if I promise you we'll get a
release as soon as we have any significant bugfix ? :D
2011/6/7 Thomas Broyer
> -1 because of MGWT-277 (I mean, it's not worth doing a release if it's not
> in, IMO, particularly as/if it can be fixed quickly)
>
> Now that you
[
http://jira.codehaus.org/browse/MGWT-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MGWT-296:
-
Description: umbrella issue to track 2.4.0 SDK features/enhancements
> Support GWT
Support GWT 2.4
---
Key: MGWT-296
URL: http://jira.codehaus.org/browse/MGWT-296
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Reporter: nicolas de loof
--
This message is automatically generated by JIRA
That's right, I totally missed logging my WIP for GWT 2.3.0 support in Jira,
here it is : MGWT-295
2011/6/7 Fotos Georgiadis
>
> On Tuesday, June 7, 2011 3:00:49 PM UTC+3, nicolas.deloof wrote:
>>
>> Right, we can wait yet another 4 month before doing a release just to have
>> a larger change lo
[
http://jira.codehaus.org/browse/MGWT-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-295.
Resolution: Fixed
Fix Version/s: 2.3.0
> Support GWT 2.3
> ---
>
>
[
http://jira.codehaus.org/browse/MGWT-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MGWT-295:
Assignee: nicolas de loof
> Support GWT 2.3
> ---
>
> K
[
http://jira.codehaus.org/browse/MGWT-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269716#action_269716
]
nicolas de loof commented on MGWT-295:
--
Upgrade SDK dependencies to 2.3.0
Add dependencies
Support GWT 2.3
---
Key: MGWT-295
URL: http://jira.codehaus.org/browse/MGWT-295
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Affects Versions: 2.2.0
Reporter: nicolas de loof
--
This message is
Right, we can wait yet another 4 month before doing a release just to have a
larger change log,
or we can follow the best-practice to release often, and plan a new release
ASAP.
This release has some untracked feature / enhancement, I agree we should
better log into Jira what happens in code :
Th
Hi folks,
I just pushed a release for gwt-maven-plugin on
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-043/
let me know is anything is wrong
as usual, vote is open for 72h
[ ] +1 do it
[ ] 0 I don't care, I'm using gradle and gwt sucks
[ ] -1 don't release as is, because ...
[
http://jira.codehaus.org/browse/MGWT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269459#action_269459
]
nicolas de loof commented on MGWT-285:
--
gwt:compile run later in lifecycle but generating so
[
http://jira.codehaus.org/browse/MGWT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269275#action_269275
]
nicolas de loof commented on MGWT-285:
--
As generate-source phase occurs prior to reso
[
http://jira.codehaus.org/browse/MGWT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269251#action_269251
]
nicolas de loof commented on MGWT-284:
--
please do
> Goal "gwt:eclipse" gener
you just need to push
> upstream)
>
> On 30/05/2011, at 10:48 PM, Olivier Lamy wrote:
>
> > FYI, I have just created the organization maven-mojo
> > https://github.com/maven-mojo . (https://github.com/mojo was already
> > used).
> >
> > 2011/5/30 nicola
nderstand :-) )
>> So two solutions :
>> * move to github
>> * ask ben or bob to have a git repo @codehaus (AFAIK it's supported )
>>
>> Perso, I like git so why not :-)
>>
>> /Olivier
>>
>> Le 30 mai 2011 11:59, Arnaud Héritier a écrit :
&g
Hi folks,
I'll start preparation for a 2.3.0 release soon,
starting with this release, I'd like to move the canonical repo to gitHub to
encourage more contributions, either via pull-request or direct commit.
I'd like to follow the jenkins-way, with more releases (lets say, one per
month) and lowe
[
http://jira.codehaus.org/browse/MGWT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268117#action_268117
]
nicolas de loof commented on MGWT-292:
--
online doc for mojo is for latest code in svn.
Maybe
[
http://jira.codehaus.org/browse/MGWT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267656#action_267656
]
nicolas de loof commented on MGWT-292:
--
2.3.0 is a work in progress,
If you want to test
[
http://jira.codehaus.org/browse/MGWT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263697#action_263697
]
nicolas de loof commented on MGWT-284:
--
1st issue is fixed in SVN
for the 2nd one, I'm
[
http://jira.codehaus.org/browse/MGWT-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MGWT-284:
Assignee: nicolas de loof
> Goal "gwt:eclipse" generates buggy launch
[
http://jira.codehaus.org/browse/MGWT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261593#action_261593
]
nicolas de loof commented on MGWT-281:
--
Thats right, sorry to summarise the issue a wrong
[
http://jira.codehaus.org/browse/MGWT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261587#action_261587
]
nicolas de loof commented on MGWT-281:
--
This issue has allready been reported to Google Ecl
[
http://jira.codehaus.org/browse/MGWT-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-280.
Resolution: Fixed
Fix Version/s: 2.2.0-1
fixed in SVN at revision
> gwt-user.jar is needles
[
http://jira.codehaus.org/browse/MGWT-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MGWT-280:
Assignee: nicolas de loof
> gwt-user.jar is needlessly copied to the
[
http://jira.codehaus.org/browse/MGWT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259302#action_259302
]
nicolas de loof commented on MGWT-271:
--
Yes, I used your code form git and had no error
[
http://jira.codehaus.org/browse/MJS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259291#action_259291
]
nicolas de loof commented on MJS-37:
I'm not in favor of suffixing our releases with -b
[
http://jira.codehaus.org/browse/MGWT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259290#action_259290
]
nicolas de loof commented on MGWT-271:
--
I tried to reproduce your issue, works for me
(
Ap
[
http://jira.codehaus.org/browse/MGWT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258205#action_258205
]
nicolas de loof commented on MGWT-250:
--
Seems you're using GwtTestCase ?
gwt-maven don
[
http://jira.codehaus.org/browse/MGWT-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258204#action_258204
]
nicolas de loof commented on MGWT-257:
--
Can you please post the entire stacktrace ?
> gw
[
http://jira.codehaus.org/browse/MGWT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-269.
Resolution: Fixed
Fix Version/s: 2.2.1
Assignee: nicolas de loof
added ".ui.xm
[
http://jira.codehaus.org/browse/MGWT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-254.
Resolution: Fixed
Fix Version/s: 2.2.1
Assignee: nicolas de loof
fixed in svn at r13685
[
http://jira.codehaus.org/browse/MGWT-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258201#action_258201
]
nicolas de loof commented on MGWT-267:
--
What other mojo would you like to skip ?
> gwt:
[
http://jira.codehaus.org/browse/MGWT-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-259.
Resolution: Fixed
Fix Version/s: 2.2.1
Assignee: nicolas de loof
fixed in SVN at revision
[
http://jira.codehaus.org/browse/MGWT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258197#action_258197
]
nicolas de loof commented on MGWT-163:
--
I wonder I can't see the "-noserver"
[
http://jira.codehaus.org/browse/MGWT-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-247.
Resolution: Won't Fix
Sory to say we have no way to split the GWT compiler and GWT runtime classpath
[
http://jira.codehaus.org/browse/MGWT-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258195#action_258195
]
nicolas de loof commented on MGWT-258:
--
Can you please post the build log (as debug).
Is
[
http://jira.codehaus.org/browse/MGWT-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-207.
Resolution: Won't Fix
Fix Version/s: 2.2.0
Not confirmed with latest release.
Please re-open i
[
http://jira.codehaus.org/browse/MGWT-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258193#action_258193
]
nicolas de loof commented on MGWT-246:
--
You must import the project into Eclipse using m2ecl
[
http://jira.codehaus.org/browse/MGWT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-266.
Resolution: Fixed
Fix Version/s: 2.2.1
patch applied, thanks
> compileSourcesArtifacts ignored
[
http://jira.codehaus.org/browse/MGWT-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MGWT-93:
Fix Version/s: (was: 2.2.0)
2.2.1
> Serialization policy was not fo
[
http://jira.codehaus.org/browse/MGWT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MGWT-175:
-
Fix Version/s: (was: 2.2.0)
> Warnings from tests that are excluded during gwt:t
MGWT-175 is still open in Jira,
I suspect the issue was included in release note because we have set
"planned version" to next release, but never worked on it. We should not
plan for a fix release in such case.
2011/3/1 Fotos Georgiadis
> Nice.
>
> One minor caveat tho ... in the release notes i
I've released the gwt-maven-plugin 2.2.0, it will be synched to central in
few hours,
thanks a lot for testing
2011/2/22 nicolas de loof
> Hi,
>
> I'd like to push a release of GWT-maven plugin 2.2.0
> This release target GWT SDK 2.2.0
>
> We also h
Feb 22, 2011 at 10:04 AM, nicolas de loof
> wrote:
> > You can check the site and test the artifact
> > from
> http://people.apache.org/~nicolas/staging/org/codehaus/mojo/gwt-maven-plugin/2.2.0/
>
> Is there any reason we aren't following
> http://mojo.codehaus.org
gt;
> On Tue, Feb 22, 2011 at 16:04, nicolas de loof
> wrote:
>
>> Hi,
>>
>> I'd like to push a release of GWT-maven plugin 2.2.0
>> This release target GWT SDK 2.2.0
>>
>> We also have fixed some bugs :
>> http://jira.codehaus.org/browse/MGWT
The only reason is ... that I just missed this doc !
>
> Is there any reason we aren't following
> http://mojo.codehaus.org/development/performing-a-release.html to
> perform the staged release like other Mojo plugins? My team already
> has our MRM configured to pick up staged releases through th
Hi,
I'd like to push a release of GWT-maven plugin 2.2.0
This release target GWT SDK 2.2.0
We also have fixed some bugs :
http://jira.codehaus.org/browse/MGWT/fixforversion/17169
You can check the site and test the artifact from
http://people.apache.org/~nicolas/staging/org/codehaus/mojo/gwt-mav
[
http://jira.codehaus.org/browse/MGWT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-270.
Resolution: Fixed
> Support GWT 2.2
> ---
>
> K
[
http://jira.codehaus.org/browse/MGWT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MGWT-270:
-
Affects Version/s: (was: 2.2.0)
2.1.0
Fix Version/s: 2.2.0
> Supp
[
http://jira.codehaus.org/browse/MGWT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof reassigned MGWT-270:
Assignee: nicolas de loof
> Support GWT 2.2
> ---
>
> K
[
http://jira.codehaus.org/browse/MGWT-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-268.
Resolution: Won't Fix
Setting the eclipse classpath containers is not in the scope of
gwt-maven-p
[
http://jira.codehaus.org/browse/MGWT-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256735#action_256735
]
nicolas de loof commented on MGWT-268:
--
The new release will mostly only upgrade pl
[
http://jira.codehaus.org/browse/MGWT-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256728#action_256728
]
nicolas de loof commented on MGWT-268:
--
The SDK upgrade is planned for 2.2 release.
You
[
http://jira.codehaus.org/browse/MGWT-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256514#action_256514
]
nicolas de loof commented on MGWT-268:
--
did you repport this error on GWT tracker ?
(please
+1 to hots the plugin as a new Mojo contrib
+1 to invite Franck as Mojo Committer
Nicolas
2011/1/12
> Hello,
>
> In order to complete my last work on a sonar plugin called
> sonar-cxx-plugin. I
> developed a maven plugin called maven-cxx-plugin.
>
> This plugin contains 9 mojo that achieve foll
[
http://jira.codehaus.org/browse/MGWT-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-260.
Resolution: Won't Fix
The only way for the GWT configuration in Eclipse to match the POM parameters
+1
nice work Olivier
Nicolas
2010/12/3 Olivier Lamy
> Hello,
> I'd like to release Gwt Maven Plugin 2.1.0-1.
>
> Release Notes :
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11860&version=16878
>
> Staging Repo :
> https://nexus.codehaus.org/content/repositories/orgcodehausmoj
[
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245680#action_245680
]
nicolas de loof commented on MGWT-219:
--
I don't take it personally, but I don't li
[
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245672#action_245672
]
nicolas de loof commented on MGWT-219:
--
As a maven guy I'ma also disappointed about GWT
Inclue Google private changes into mojo plugin
--
Key: MGWT-229
URL: http://jira.codehaus.org/browse/MGWT-229
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Reporter: nicolas de
+1
Go go go
2010/11/2 Olivier Lamy
> Hi,
> I'd like to release Gwt Maven Plugin 2.1.0.
>
> We fixed 43 issues :
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=RJv_t0Y4KG&version=16732&styleName=Text&projectId=11860&Create=Create
>
> Staged repo is here :
> https://nexus.codehaus
[
http://jira.codehaus.org/browse/MGWT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-228.
Resolution: Not A Bug
Fix Version/s: 2.1.0
1.2 does not support gwt 2.1
a new 2.1 version is
+1
so that Olivier gets more time to work on maven3 support in hudson :)
2010/10/9 Olivier Lamy
> Hi,
> Mark has provided some good patches for the Tomcat Maven Plugin. (and
> I don't want to be alone to work on this mojo :-) ).
> So I propose Mark as a committer.
> Here my +1.
>
> Thanks,
> --
[
http://jira.codehaus.org/browse/MGWT-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-223.
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: nicolas de loof
Fixed by changing the
: eclipse Helios, m2eclipse
Reporter: nicolas de loof
m2eclipse project configuration fails with stacktrace when i18n is configured
{{
06/10/10 17:43:14 CEST: [ERROR] Exception in thread "main"
java.lang.NoClassDefFoundError: com/google/gwt/i18n/tools/I18NSync
06/10/10 17:43:14 CE
[
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-219.
Resolution: Won't Fix
Won't fix. Relying on classpath ordering is definitly a hack, Google MUST
1 - 100 of 560 matches
Mail list logo
