The jira report on the site [1] doesn't match the fixed issues you've linked
to in jira [2]. Not a major thing, but a little bit weird.
I haven't checked the code, but I assume the jira report is crafted manually
instead of retrieved from jira.
/Anders
[1] http://mojo.codehaus.org/aspectj-maven-p
[
http://jira.codehaus.org/browse/MFINDBUGS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire closed MFINDBUGS-132.
-
Resolution: Fixed
Fix Version/s: 2.3.2
Try 2.3.2-SNAPSHOT
> Findbugs doesn't run on
[
http://jira.codehaus.org/browse/MFINDBUGS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257376#action_257376
]
Dave Meibusch commented on MFINDBUGS-120:
-
We see the same issue. Our classpath is generat
[
http://jira.codehaus.org/browse/MFINDBUGS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire updated MFINDBUGS-132:
--
Affects Version/s: (was: 2.3.2)
2.3.1
Assignee: Gar
Hi,
I'd like to release version 1.3.1 of the Aspectj Maven Plugin
This plugin handles AspectJ usage within MavenFunctionality provided is:
weaving of aspects (or existing aspects from libraries) with the test and/or
main classes, weaving of pre-existing jars and ajdoc reporting.We solved 4
is
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257352#action_257352
]
Mark Struberg commented on MSQL-69:
---
Hi Jochen!
I've now uploaded the latest 1.5-SNAPSHOT to the code
[
http://jira.codehaus.org/browse/MASPECTJ-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MASPECTJ-77:
---
Fix Version/s: (was: 1.3.1)
> Add javaagent option to configuration section
>
Greetings,
On Tue, Feb 22, 2011 at 10:47 AM, nicolas de loof
wrote:
> I've run the expected release process, the staged plugin is available at
> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-001/
> To avoid missunderstandings, I've removed the one at people.apache.org
I've test
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257345#action_257345
]
Jochen Stiepel commented on MSQL-69:
ah ok. no i didn't compile it myself.
can I provide more infor
Findbugs doesn't run on projects containing only test classes
-
Key: MFINDBUGS-132
URL: http://jira.codehaus.org/browse/MFINDBUGS-132
Project: Maven 2.x FindBugs Plugin
Issue Type:
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257292#action_257292
]
Mark Struberg commented on MSQL-69:
---
did you compile 1.5-SNAPSHOT yourself from source?
I have not dep
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257290#action_257290
]
Jochen Stiepel edited comment on MSQL-69 at 2/22/11 11:39 AM:
--
I tried 1.5-
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257290#action_257290
]
Jochen Stiepel commented on MSQL-69:
I tried 1.5-SHAPSHOT, and it is still consuming one single CPU
I've run the expected release process, the staged plugin is available at
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-001/
To avoid missunderstandings, I've removed the one at people.apache.org
2011/2/22 Jesse Farinacci
> First off, W00T! :-)
>
> On Tue, Feb 22, 2011 at 10:0
No, we allready choosed to align the plugin release to GWT SDK, and only use
-X for plugin upgrade between two SDK release (that should not occur often
as Google guys release faster that we do)
2011/2/22 Anders Hammar
> Shouldn't the versioning scheme be -?
>
> /Anders
>
>
> On Tue, Feb 22, 20
Shouldn't the versioning scheme be -?
/Anders
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/fixforversion/17169
>
>
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
First off, W00T! :-)
On Tue, 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/development/per
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
> ---
>
> Key: MGWT-270
> U
[
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
> Support G
[
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
> ---
>
> Key: MGWT-270
>
Support GWT 2.2
---
Key: MGWT-270
URL: http://jira.codehaus.org/browse/MGWT-270
Project: Maven 2.x GWT Plugin
Issue Type: Task
Affects Versions: 2.2.0
Reporter: jieryn
GWT 2.2 was released on February 14th, 2011
[
http://jira.codehaus.org/browse/MJBOSS-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257227#action_257227
]
Leiv Hellebo commented on MJBOSS-59:
I see why you don't want all that duplication. I'll argue for
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257216#action_257216
]
Mark Struberg commented on MSQL-69:
---
just 4 the record: I process a 34MB migrationdata.sql for MySQL a
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257213#action_257213
]
Mark Struberg commented on MSQL-69:
---
Jochen, can you please test my latest commit with your file? I've
[
http://jira.codehaus.org/browse/MSQL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned MSQL-69:
-
Assignee: Mark Struberg
> High CPU usage of org.codehaus.mojo.sql.SqlSplitter.containsSqlEnd
> ---
[
http://jira.codehaus.org/browse/MGWT-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257156#action_257156
]
skalimer0 edited comment on MGWT-268 at 2/22/11 4:19 AM:
-
I tried something...
[
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-plugin. On
29 matches
Mail list logo
