[ http://jira.codehaus.org/browse/MRM-49?page=all ]
Brett Porter closed MRM-49:
---
> Skeleton Unit tests for implementation of interfaces
>
>
> Key: MRM-49
> URL: http://jira.codehaus.org/br
[ http://jira.codehaus.org/browse/MRM-51?page=all ]
Edwin Punzalan closed MRM-51:
-
Assign To: John Tolentino
Resolution: Fixed
Fix Version: 1.0-alpha-1
Applied. Thanks.
> Mock objects and additional classes
>
[ http://jira.codehaus.org/browse/MNG-1730?page=all ]
Brett Porter updated MNG-1730:
--
Description:
svn is very stubborn about this. Basically you have to have the value in
match the url used to check it out.
Things that will fail:
- if you pass in a diff
maven-scm-plugin is now depending on plexus-utils-1.5-SNAPSHOT as well.
-D
On 12/1/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> I noticed that the release plugin now requires plexus-utils 1.0.5
> snapshot. This means that it will only work on Maven 2.0.1 (and recently
> bootstrapped at that).
End Time contains junk value when I forced a build to run
-
Key: CONTINUUM-496
URL: http://jira.codehaus.org/browse/CONTINUUM-496
Project: Continuum
Type: Bug
Components: Core system
Versions: 1.0.2
[ http://jira.codehaus.org/browse/MRM-51?page=all ]
John Tolentino updated MRM-51:
--
Component: reporting
Attachment: MRM-51-maven-repository-reports-standard.diff
There's a bug in the current version of Tortoise SVN create patch. Created a
new patch u
[ http://jira.codehaus.org/browse/MNG-986?page=all ]
Johnny R. Ruiz III closed MNG-986:
--
Resolution: Fixed
Fixed and Applied
> add configurable powered by logo
>
>
> Key: MNG-986
> URL: http://jir
Mock objects and additional classes
---
Key: MRM-51
URL: http://jira.codehaus.org/browse/MRM-51
Project: Maven Repository Manager
Type: Test
Reporter: John Tolentino
Attachments: MRM-51-maven-repository-reports-standard.patch
New
I noticed that the release plugin now requires plexus-utils 1.0.5
snapshot. This means that it will only work on Maven 2.0.1 (and recently
bootstrapped at that).
Is there an alternative?
Please be vigilant about backwards compatibility. We really need to get
plexus-utils out of the core...
- Bre
release plugin doesn't tag correctly with svn+ssh
-
Key: MNG-1730
URL: http://jira.codehaus.org/browse/MNG-1730
Project: Maven 2
Type: Bug
Components: maven-release-plugin
Reporter: Brett Porter
Assigned to: Br
[ http://jira.codehaus.org/browse/MNG-1730?page=all ]
Brett Porter updated MNG-1730:
--
Remaining Estimate: 30 minutes
Original Estimate: 30 minutes
> release plugin doesn't tag correctly with svn+ssh
> -
>
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/02-Dec-2005_12.30.53/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
[ http://jira.codehaus.org/browse/MNG-1336?page=all ]
Johnny R. Ruiz III closed MNG-1336:
---
Resolution: Fixed
Applied and Fixed
> the issue management report should handle more issue management systems
> ---
[ http://jira.codehaus.org/browse/MPANNOUNCEMENT-20?page=all ]
Lukas Theussl closed MPANNOUNCEMENT-20:
---
Resolution: Fixed
Fix Version: 1.4
Already fixed in SVN.
> Fatal Error [line 31, row 37]: Attribute "ant" bound to namespace
> "http
[ http://jira.codehaus.org/browse/MNG-1654?page=comments#action_52607 ]
Brett Porter commented on MNG-1654:
---
the artifact created in the jar plugin can have a handler created for it - the
default is to use extension = type, so its possible. But unless they
[ http://jira.codehaus.org/browse/MNG-1654?page=comments#action_52582 ]
John Casey commented on MNG-1654:
-
Won't these things need separate ArtifactHandlers and LifecycleMappings? At any
rate, the jar plugin's chosen extension only matters for the file creat
Checkout does not handle case where clientspec is unchanged
---
Key: SCM-94
URL: http://jira.codehaus.org/browse/SCM-94
Project: Maven SCM
Type: Bug
Components: maven-scm-provider-perforce
Versions: 1.0-
Fatal Error [line 31, row 37]: Attribute "ant" bound to namespace
"http://www.w3.org/2000/xmlns/"; was already specified for element "project"
-
Key
[ http://jira.codehaus.org/browse/MPDASHBOARD-34?page=comments#action_52591
]
Arnaud Heritier commented on MPDASHBOARD-34:
your patch will make the plugin compatible only with maven 1.1
the jelly tag util:replace bundled in maven 1.0.2 doesn't al
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051202.033001.txt
Unable to create schedule with year
---
Key: CONTINUUM-494
URL: http://jira.codehaus.org/browse/CONTINUUM-494
Project: Continuum
Type: Bug
Components: Web interface
Versions: 1.0.1
Reporter: Shinobu Kawai Yoshida
The
[ http://jira.codehaus.org/browse/MPXDOC-184?page=all ]
Lukas Theussl closed MPXDOC-184:
Resolution: Won't Fix
Closing as won't fix since it 's not an xdoc specific issue.Please open an
issue in the respective plugins if you still have problems wit
[ http://jira.codehaus.org/browse/MNG-1650?page=all ]
John Casey closed MNG-1650:
---
Resolution: Fixed
applied. thanks, Allan
> Maven Archiver should allow pom.xml and pom.properties to be excluded in the
> generated jar
>
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/01-Dec-2005_04.33.41/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
[ http://jira.codehaus.org/browse/MPSCM-70?page=all ]
Lukas Theussl moved MPXDOC-142 to MPSCM-70:
---
Key: MPSCM-70 (was: MPXDOC-142)
Project: maven-scm-plugin (was: maven-xdoc-plugin)
> Fix Anonymous Access with Maven
>
[ http://jira.codehaus.org/browse/MPA-28?page=comments#action_52587 ]
Brett Porter commented on MPA-28:
-
CLA received. Following up with Dan.
> Process Dan Tran
>
>
> Key: MPA-28
> URL: http://jira.codehaus.org/browse/MPA-2
Use quiet notation for Developers
-
Key: CONTINUUM-495
URL: http://jira.codehaus.org/browse/CONTINUUM-495
Project: Continuum
Type: Improvement
Components: Web interface
Versions: 1.0.1
Environment: maven 2.0
Reporter:
[ http://jira.codehaus.org/browse/SCM-88?page=all ]
mike perham updated SCM-88:
---
Attachment: scm.txt
maven-scm patch
> Add transparent support for locking providers
> -
>
> Key: SCM-88
> URL: http:
[ http://jira.codehaus.org/browse/SCM-88?page=all ]
mike perham updated SCM-88:
---
Attachment: release-plugin.txt
maven-release-plugin patch
> Add transparent support for locking providers
> -
>
> Key: SCM-88
[ http://jira.codehaus.org/browse/MPDASHBOARD-34?page=comments#action_52586
]
pkernevez commented on MPDASHBOARD-34:
--
See http://issues.apache.org/jira/browse/JELLY-224
> Cobertura aggregator don't support offline mode
> ---
Allow to add all developpers address in a notifier without duplicate
developpers addresses
--
Key: CONTINUUM-493
URL: http://jira.codehaus.org/browse/CONTINUUM-493
Project: Continuum
[ http://jira.codehaus.org/browse/MNG-1520?page=all ]
John Casey closed MNG-1520:
---
Resolution: Duplicate
> Excluding pom.properties and pom.xml from produced artifact
>
>
> Key: MNG-15
[ http://jira.codehaus.org/browse/MNG-1520?page=comments#action_52581 ]
John Casey commented on MNG-1520:
-
Use the MavenArchiveConfiguration.setAddMavenDescriptor(..) method. It would
look like:
...
org.apache.maven.plugins
maven-jar-plugin
2.1-SNA
[ http://jira.codehaus.org/browse/MNG-1650?page=all ]
John Casey closed MNG-1650:
---
Resolution: Duplicate
See MNG-1598
> Maven Archiver should allow pom.xml and pom.properties to be excluded in the
> generated jar
> --
[ http://jira.codehaus.org/browse/MPDASHBOARD-34?page=all ]
pkernevez updated MPDASHBOARD-34:
-
Attachment: MPDASHBOARD-34.patch
Add a patch. It consiste a the deletion of the DTD declaration before the
parsing of the Xml file.
> Cobertura aggregator do
[ http://jira.codehaus.org/browse/MNG-1650?page=all ]
John Casey reopened MNG-1650:
-
reopening to back out this patch. it's already implemented using the
MavenArchiveConfiguration.
> Maven Archiver should allow pom.xml and pom.properties to be excluded in
[ http://jira.codehaus.org/browse/SCM-88?page=comments#action_52577 ]
mike perham commented on SCM-88:
I would suggest also adding the override to the ClearCase provider but I did
not do it. I verified it works as expected with the Peforce provider.
> Add
[ http://jira.codehaus.org/browse/MNG-1728?page=all ]
Brett Porter closed MNG-1728:
-
Assign To: Brett Porter
Resolution: Duplicate
> Release versioning does not work with dependencyManagement
> --
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051202.024500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.024500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MRM-50?page=all ]
Edwin Punzalan closed MRM-50:
-
Resolution: Fixed
Fix Version: 1.0-alpha-1
Applied. Thanks!
> Abstraction of Reporting test cases
> ---
>
> Key: MRM-50
>
[ http://jira.codehaus.org/browse/SCM-91?page=all ]
Emmanuel Venisse closed SCM-91:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Done.
> Plexus manager refactoring
> --
>
> Key: SCM-91
> URL: http://ji
Create pom for checkstyle 4.0
-
Key: MEV-242
URL: http://jira.codehaus.org/browse/MEV-242
Project: Maven Evangelism
Type: Task
Reporter: Carlos Sanchez
Assigned to: Edwin Punzalan
I've already uploaded the jar
http://sourceforge.n
Velocity Tools update for 1.2
-
Key: MAVENUPLOAD-616
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-616
Project: maven-upload-requests
Type: Task
Reporter: Eric Merritt
http://jakarta.apache.org/velocity/tools/
This is just an u
[ http://jira.codehaus.org/browse/SCM-88?page=comments#action_52573 ]
mike perham commented on SCM-88:
I'm working on adding this right now.
> Add transparent support for locking providers
> -
>
> Key: SCM
[ http://jira.codehaus.org/browse/MNG-1725?page=comments#action_52598 ]
Brett Porter commented on MNG-1725:
---
I wonder if we need to do a plexus logging implementation of the commons
logger, and put that and the API in the root classloader? That just worrie
[ http://jira.codehaus.org/browse/SCM-94?page=all ]
Emmanuel Venisse closed SCM-94:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Applied.
> Checkout does not handle case where clientspec is unchanged
> -
[ http://jira.codehaus.org/browse/MEV-242?page=all ]
Edwin Punzalan closed MEV-242:
--
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours to reach central repo.
> Create pom for checkstyle 4.0
> -
>
> Key: MEV-24
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/01-Dec-2005_08.34.17/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051202.023000.txt
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.023000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.021500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051202.02.txt
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.02.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
It seems the zone can't reach anything at Sentex where codehaus is
haused. Investigating... if anyone is savvy in troubleshooting this
area, please let me know :)
Cheers,
Brett
Brett Porter wrote:
> not sure what was going on here - the zone can't resolve
> test.maven.codehaus.org which is the st
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.014500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051202.013000.txt
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.013000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.011500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
not sure what was going on here - the zone can't resolve
test.maven.codehaus.org which is the staging repo to avoid the sync delay.
I've added it to /etc/hosts in the interim.
- Brett
[EMAIL PROTECTED] wrote:
> Log:
> http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.004500.txt
>
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.004500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
John,
A better solution might be have the plugin set the c-logging system
property - see the Jetty6 plugin docs for an example.
- Brett
[EMAIL PROTECTED] wrote:
> Author: jdcasey
> Date: Thu Dec 1 08:59:24 2005
> New Revision: 350274
>
> URL: http://svn.apache.org/viewcvs?rev=350274&view=rev
>
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051202.003000.txt
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.001500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051202.00.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051201.224500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051201.223000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051201.213000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The checkstyle plugin for m1 has a 2.0 release from long time ago.
There won't be conflicts as m1 plugins don't go to m2 repos.
On 12/1/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> I've uploaded checkstyle 4.0 to the repo, and a jira issue was created
> to provide the pom needed MEV-242.
>
> On
The checkstyle plugin 2.0 already exists in m1. Which release will you
create to not create a conflict ?
Arnaud
On 12/1/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> I've uploaded checkstyle 4.0 to the repo, and a jira issue was created
> to provide the pom needed MEV-242.
>
> On 12/1/05, Fa
+1
Arnaud
On 12/1/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> Finally, It's fixed. Hopefully, I have the most comprensive girlfriend in
> the world. See you later.
>
> Cheers,
> Stéphane
>
> On 12/1/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> >
> > MNG-1723 was just discovered and con
I've uploaded checkstyle 4.0 to the repo, and a jira issue was created
to provide the pom needed MEV-242.
On 12/1/05, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
> Java 1.5 support alone really worth upgrading, I would prefer
> upgrading the dependency to checkstyle 4 before a release, new
> feat
use project.build.finalName for WTP context-root (if specified)
---
Key: MNG-1729
URL: http://jira.codehaus.org/browse/MNG-1729
Project: Maven 2
Type: Improvement
Components: maven-eclipse-plugin
Ver
[ http://jira.codehaus.org/browse/MNG-1070?page=comments#action_52565 ]
Joakim Erdfelt commented on MNG-1070:
-
Conversation on #maven about loading the settings.xml from the embedder.
jvanzyl: hi, in the embedder, why do a call to the resolve method use
Release versioning does not work with dependencyManagement
--
Key: MNG-1728
URL: http://jira.codehaus.org/browse/MNG-1728
Project: Maven 2
Type: Bug
Components: maven-release-plugin
Versions: 2.0.1
[ http://jira.codehaus.org/browse/SCM-92?page=all ]
Emmanuel Venisse closed SCM-92:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Applied. Thanks.
> Add working directory support to Perforce update command
>
Edit command fails where file is not in current directory
-
Key: SCM-93
URL: http://jira.codehaus.org/browse/SCM-93
Project: Maven SCM
Type: Bug
Components: maven-scm-provider-perforce
Versions: 1.0-beta
[ http://jira.codehaus.org/browse/MNG-1727?page=comments#action_52556 ]
Emmanuel Venisse commented on MNG-1727:
---
strange. In source we call scm.edit for each modified pom file (in writePom
method)
> useEditMode=true does not recurse
>
[ http://jira.codehaus.org/browse/MNG-1727?page=all ]
mike perham closed MNG-1727:
Resolution: Cannot Reproduce
Looks like it's a bug in my Perforce edit command.
> useEditMode=true does not recurse
> -
>
> Key:
[ http://jira.codehaus.org/browse/MNG-1650?page=comments#action_52554 ]
Emmanuel Venisse commented on MNG-1650:
---
This feature is already implemented, i added it 3 weeks ago.
In MavenArchiverConfiguration, we have the boolean addMavenDescriptor paramete
Vote results:
eclipse m2 plugin:
binding: +6 - committers: +4
(none of the open issues should be considered critical, most of them
are feature requests/enhancements and at the current status the m2
plugin is already more complete and stable than its m1 counterpart)
eclipse m1 plugin:
binding: +6
[ http://jira.codehaus.org/browse/MNG-1650?page=all ]
John Casey updated MNG-1650:
Complexity: Expert (was: Intermediate)
Remaining Estimate: 30 minutes
Original Estimate: 30 minutes
refactoring patch to avoid the requirement for an instanc
useEditMode=true does not recurse
-
Key: MNG-1727
URL: http://jira.codehaus.org/browse/MNG-1727
Project: Maven 2
Type: Bug
Components: maven-release-plugin
Versions: 2.0.1
Reporter: mike perham
I'm trying to release a
Apache Wiki wrote:
Dear Wiki user,
Please use the following space:
http://docs.codehaus.org/display/MAVENUSER/Home
Stuff in the ApacheWiki will not get integrated.
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the m
Java 1.5 support alone really worth upgrading, I would prefer
upgrading the dependency to checkstyle 4 before a release, new
features will come later.
fabrizio
On 12/1/05, John Casey <[EMAIL PROTECTED]> wrote:
> Agreed. Looking at it briefly, there are some new features that we'd
> have to wire
Agreed. Looking at it briefly, there are some new features that we'd
have to wire into the plugin in order to make it worthwhile. We'll leave
it for another release.
Cool with everyone?
-j
Dennis Lundberg wrote:
Checkstyle 4.0 is a major release that, among other things, include
(preliminary
yup, I never try this before. but teh checkout time will be very long for my chase since my legacy system has a lots of dead, seldomlyused,larged files.
I rather to stay on the dynamic view rather than snapshot view.
If your system is new and you are carefully organize your soure tree, snapsh
That is not true if you create a snapshot view. It can be in any
directory. I already implemented and tested this. You can then do a
'cleartool update' and that will update the snapshot view.
regards,
Wim2005/12/1, dan tran <[EMAIL PROTECTED]>:
After checkout, clearcase dictates to location of ch
Finally, It's fixed. Hopefully, I have the most comprensive girlfriend in
the world. See you later.
Cheers,
Stéphane
On 12/1/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> MNG-1723 was just discovered and confirmed. I will not have the time to
> fix it today and I am off till December 5th.
>
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll closed MNG-1723:
Resolution: Fixed
Fix Version: 2.0.1
Got access to SVN finally. Applied and fixed.
> Plugin configuration doesn't support .ejb3 and .par EJB modules
> -
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll updated MNG-1723:
-
Attachment: MNG-1723.patch
Patch. John, could you please apply it, I have issue with SVN on my local box.
> Plugin configuration doesn't support .ejb3 and .par EJB
Release plug-in did not add the tag to the end of tagBase
-
Key: MNG-1726
URL: http://jira.codehaus.org/browse/MNG-1726
Project: Maven 2
Type: Bug
Components: maven-release-plugin
Versions: 2.0
Envi
Checkstyle 4.0 is a major release that, among other things, include
(preliminary) support for Java 1.5 code constructs. It also requires
Java 1.4 to run. Changes have been made to the public API. My suggestion
would be to wait a while before updating the dependency until the impact
it has on th
Notifiers should be optional
Key: CONTINUUM-492
URL: http://jira.codehaus.org/browse/CONTINUUM-492
Project: Continuum
Type: Bug
Components: Core system
Versions: 1.0.1
Reporter: Matthew Beermann
Fix For: 1.0.2
Conti
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051201.183001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051201.183001.txt
[ http://jira.codehaus.org/browse/MPARTIFACT-61?page=comments#action_52546
]
Lukas Theussl commented on MPARTIFACT-61:
-
You're right, 1.5.2 should work with m102. Any chance that you (or anybody)
could confirm that it works on Windows with the lates
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051201.18.txt
[ http://jira.codehaus.org/browse/MPCHANGELOG-79?page=all ]
Lukas Theussl closed MPCHANGELOG-79:
Resolution: Duplicate
Fix Version: (was: 1.9)
You're right, you posted it in the wrong area, I moved it to the correct one
(MOJO), now you
+1
On 12/1/05, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
>
> +1
>
> fabrizio
>
> On 11/29/05, John Casey <[EMAIL PROTECTED]> wrote:
> > Hi everyone,
> >
> > I wanted to call a vote on releasing the next version of the checkstyle
> > plugin. I'm currently working on some major bugfixes, includin
1 - 100 of 155 matches
Mail list logo