[jira] Updated: (MAVEN-1671) Project class doens't have setVersions() method.
[ http://jira.codehaus.org/browse/MAVEN-1671?page=all ] dion gillard updated MAVEN-1671: Attachment: maven1671-patch.txt > Project class doens't have setVersions() method. > > > Key: MAVEN-1671 > URL: http://jira.codehaus.org/browse/MAVEN-1671 > Project: Maven > Type: Bug > Components: model > Versions: 1.1-beta-1 > Reporter: Milos Kleint > Priority: Blocker > Fix For: 1.1-beta-3 > Attachments: maven1671-patch.txt > > > Project class doens't have setVersions() method. it did have it in 1.0.2. > set as blocker as it's a backward compatibility issue and is causing problems > in mevenide. > thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1671) Project class doens't have setVersions() method.
[ http://jira.codehaus.org/browse/MAVEN-1671?page=comments#action_55589 ] dion gillard commented on MAVEN-1671: - the removing revision is 122411, sorry > Project class doens't have setVersions() method. > > > Key: MAVEN-1671 > URL: http://jira.codehaus.org/browse/MAVEN-1671 > Project: Maven > Type: Bug > Components: model > Versions: 1.1-beta-1 > Reporter: Milos Kleint > Priority: Blocker > Fix For: 1.1-beta-3 > > > Project class doens't have setVersions() method. it did have it in 1.0.2. > set as blocker as it's a backward compatibility issue and is causing problems > in mevenide. > thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1671) Project class doens't have setVersions() method.
[ http://jira.codehaus.org/browse/MAVEN-1671?page=comments#action_55588 ] dion gillard commented on MAVEN-1671: - Revision 122339 has setVersions(List) and Revision 122478 removed it. The change was committed by brett on 2004-09-21 and the commit message was: "use maven-model-1.1-SNAPSHOT" Any ideas Brett? The Model class has the setVersions(List) method. > Project class doens't have setVersions() method. > > > Key: MAVEN-1671 > URL: http://jira.codehaus.org/browse/MAVEN-1671 > Project: Maven > Type: Bug > Components: model > Versions: 1.1-beta-1 > Reporter: Milos Kleint > Priority: Blocker > Fix For: 1.1-beta-3 > > > Project class doens't have setVersions() method. it did have it in 1.0.2. > set as blocker as it's a backward compatibility issue and is causing problems > in mevenide. > thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1658) Maven jelly set tag setValue() should take an Object not a String
[ http://jira.codehaus.org/browse/MAVEN-1658?page=all ] dion gillard updated MAVEN-1658: Attachment: maven1658-patch.txt > Maven jelly set tag setValue() should take an Object not a String > - > > Key: MAVEN-1658 > URL: http://jira.codehaus.org/browse/MAVEN-1658 > Project: Maven > Type: Improvement > Components: jelly/ant integration > Versions: 1.1-beta-1 > Reporter: Jason Dillon > Fix For: 1.1-beta-3 > Attachments: maven1658-patch.txt > > > org.apache.maven.jelly.tags.maven.SetTag.setValue() currently takes a String, > when it should really take an Object. > Because it takes a string it is impossible to say, pass a List to a plugin > (like for example to pass a plugin the results of a rector run). > Simply changing "value" from a String to an Object resolves this problem and > makes the and tags 10x more useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-662) Some Findbugs jars are corrupt
Some Findbugs jars are corrupt -- Key: MAVENUPLOAD-662 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-662 Project: maven-upload-requests Type: Bug Reporter: dion gillard Some of the jars uploaded/synched to http://www.ibiblio.org/maven/findbugs/jars/ are corrupt: a) coreplugin-0.9.4.jar b) findbugs-ant-0.9.4.jar c) findbugsGUI-0.9.4.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (MPSCM-58) v1.5 is not compatible with 1.4.1
[ http://jira.codehaus.org/browse/MPSCM-58?page=all ] dion gillard resolved MPSCM-58: --- Resolution: Fixed Fix Version: (was: 1.5.1) 1.5 Problem was caused by the adding of the "-d" option to the update command. This broke CVSNT 2.0.12a. Fixed by upgrading to a later version of CVSNT. > v1.5 is not compatible with 1.4.1 > - > > Key: MPSCM-58 > URL: http://jira.codehaus.org/browse/MPSCM-58 > Project: maven-scm-plugin > Type: Bug > Versions: 1.5 > Reporter: dion gillard > Priority: Critical > Fix For: 1.5 > > > Using v1.5 as shipped with Maven 1-1-beta-1, we recieve the following errors > when running scm:update-project: > ---8<- > [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:DRPCommon > > scm:update > [echo] Updating from SCM > [INFO] Executing: cvs -f -q update -d > [INFO] Working directory: > D:\CruiseControl\build\checkouts\Deployment\..\DRPCommon > > Provider message > The cvs command failed. > > Command output > cvs update: move away Java > Source/au/com/suttons/drp/copier/BackendCopier.java; it is in the way > cvs update: move away Java Source/au/com/suttons/drp/copier/Copier.java; it > is in the way > cvs update: move away Java > Source/au/com/suttons/drp/copier/WebAppCopier.java; it is in the way > cvs update: move away xdocs/images/STAR Project Logo 1.gif; it is in the way > cvs update: move away xdocs/images/id_suttons_logo.gif; it is in the way > > >8--- > Simply replacing 1.5 with 1.4.1 gives us a working scm with no errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1638) Post goals in plugins only seem to run once
[ http://jira.codehaus.org/browse/MAVEN-1638?page=comments#action_43073 ] dion gillard commented on MAVEN-1638: - Yes it works in 1.0.2. Should it? I'll work on a reproducible test case when I have time. > Post goals in plugins only seem to run once > --- > > Key: MAVEN-1638 > URL: http://jira.codehaus.org/browse/MAVEN-1638 > Project: maven > Type: Bug > Components: plugin manager > Versions: 1.1-beta-1 > Environment: Win2k, Maven 1.1-beta 1 installed > Reporter: dion gillard > Fix For: 1.1-beta-2 > > > I have a reactored build which creates many EJB jars via ejb:install-snapshot > The was5 plugin from sourceforge is installed and it has a postGoal defined > on ejb:ejb. > Out of several EJB projects that are built during the reactored build, only > the first EJB project has the postGoal executed, it is skipped for the other > EJB projects -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPSCM-58) v1.5 is not compatible with 1.4.1
[ http://jira.codehaus.org/browse/MPSCM-58?page=comments#action_42364 ] dion gillard commented on MPSCM-58: --- Also, after deleting the files being complained about and checking them out again (using cvs checkout), the same error is displayed. > v1.5 is not compatible with 1.4.1 > - > > Key: MPSCM-58 > URL: http://jira.codehaus.org/browse/MPSCM-58 > Project: maven-scm-plugin > Type: Bug > Versions: 1.5 > Reporter: dion gillard > Priority: Critical > > > Using v1.5 as shipped with Maven 1-1-beta-1, we recieve the following errors > when running scm:update-project: > ---8<- > [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:DRPCommon > > scm:update > [echo] Updating from SCM > [INFO] Executing: cvs -f -q update -d > [INFO] Working directory: > D:\CruiseControl\build\checkouts\Deployment\..\DRPCommon > > Provider message > The cvs command failed. > > Command output > cvs update: move away Java > Source/au/com/suttons/drp/copier/BackendCopier.java; it is in the way > cvs update: move away Java Source/au/com/suttons/drp/copier/Copier.java; it > is in the way > cvs update: move away Java > Source/au/com/suttons/drp/copier/WebAppCopier.java; it is in the way > cvs update: move away xdocs/images/STAR Project Logo 1.gif; it is in the way > cvs update: move away xdocs/images/id_suttons_logo.gif; it is in the way > > >8--- > Simply replacing 1.5 with 1.4.1 gives us a working scm with no errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPSCM-58) v1.5 is not compatible with 1.4.1
[ http://jira.codehaus.org/browse/MPSCM-58?page=comments#action_42361 ] dion gillard commented on MPSCM-58: --- Is there going to be anything done about this issue? > v1.5 is not compatible with 1.4.1 > - > > Key: MPSCM-58 > URL: http://jira.codehaus.org/browse/MPSCM-58 > Project: maven-scm-plugin > Type: Bug > Versions: 1.5 > Reporter: dion gillard > Priority: Critical > > > Using v1.5 as shipped with Maven 1-1-beta-1, we recieve the following errors > when running scm:update-project: > ---8<- > [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:DRPCommon > > scm:update > [echo] Updating from SCM > [INFO] Executing: cvs -f -q update -d > [INFO] Working directory: > D:\CruiseControl\build\checkouts\Deployment\..\DRPCommon > > Provider message > The cvs command failed. > > Command output > cvs update: move away Java > Source/au/com/suttons/drp/copier/BackendCopier.java; it is in the way > cvs update: move away Java Source/au/com/suttons/drp/copier/Copier.java; it > is in the way > cvs update: move away Java > Source/au/com/suttons/drp/copier/WebAppCopier.java; it is in the way > cvs update: move away xdocs/images/STAR Project Logo 1.gif; it is in the way > cvs update: move away xdocs/images/id_suttons_logo.gif; it is in the way > > >8--- > Simply replacing 1.5 with 1.4.1 gives us a working scm with no errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1638) Post goals in plugins only seem to run once
Post goals in plugins only seem to run once --- Key: MAVEN-1638 URL: http://jira.codehaus.org/browse/MAVEN-1638 Project: maven Type: Bug Components: plugin manager Versions: 1.1-beta-1 Environment: Win2k, Maven 1.1-beta 1 installed Reporter: dion gillard I have a reactored build which creates many EJB jars via ejb:install-snapshot The was5 plugin from sourceforge is installed and it has a postGoal defined on ejb:ejb. Out of several EJB projects that are built during the reactored build, only the first EJB project has the postGoal executed, it is skipped for the other EJB projects -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1625) Maven 1.1-b1: NoSuchMethodError: Dependency.setProperties()
[ http://jira.codehaus.org/browse/MAVEN-1625?page=comments#action_42043 ] dion gillard commented on MAVEN-1625: - I've got the same issue. Has there been a release of the artifact plugin? > Maven 1.1-b1: NoSuchMethodError: Dependency.setProperties() > --- > > Key: MAVEN-1625 > URL: http://jira.codehaus.org/browse/MAVEN-1625 > Project: maven > Type: Bug > Components: core > Versions: 1.1-beta-1 > Reporter: fabrizio giustina > Fix For: 1.1-beta-2 > > > Trying maven 1.1-b1 on an existing project, working with maven 1.0.2, I get a > NoSuchMethodError if the pom contains a dependency with properties. > The project.xml seems to be valid according to the 3.0 schema, but with this > dependency defined: > > openmind > openutils > 1.0-dev > jar > > true > > > I get this error: > jar:install: > [echo] Installing... > Uploading to faber/jars/faber-dataobjects-1.0.jar: > (342K) > BUILD FAILED > java.lang.NoSuchMethodError: > org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V > at > org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.java:124) > at > org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.java:57) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInstall(DefaultArtifactDeployer.java:174) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(DefaultArtifactDeployer.java:143) > at > org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java:160) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180) > at > org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:102) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:79) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) > at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109) > at org.apache.maven.werkz.Goal.fire(Goal.java:656) > at org.apache.maven.werkz.Goal.attain(Goal.java:592) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693) > at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) > at org.apache.maven.cli.App.doMain(App.java:511) > at org.apache.maven.cli.App.main(App.java:1258) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > removing > > true > > makes maven 1.1 happy and everything works as expected. The same happens on > different projects, jar:install only works after removing all the > tags -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPSCM-58) v1.5 is not compatible with 1.4.1
v1.5 is not compatible with 1.4.1 - Key: MPSCM-58 URL: http://jira.codehaus.org/browse/MPSCM-58 Project: maven-scm-plugin Type: Bug Versions: 1.5 Reporter: dion gillard Priority: Critical Using v1.5 as shipped with Maven 1-1-beta-1, we recieve the following errors when running scm:update-project: ---8<- [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:DRPCommon scm:update [echo] Updating from SCM [INFO] Executing: cvs -f -q update -d [INFO] Working directory: D:\CruiseControl\build\checkouts\Deployment\..\DRPCommon Provider message The cvs command failed. Command output cvs update: move away Java Source/au/com/suttons/drp/copier/BackendCopier.java; it is in the way cvs update: move away Java Source/au/com/suttons/drp/copier/Copier.java; it is in the way cvs update: move away Java Source/au/com/suttons/drp/copier/WebAppCopier.java; it is in the way cvs update: move away xdocs/images/STAR Project Logo 1.gif; it is in the way cvs update: move away xdocs/images/id_suttons_logo.gif; it is in the way >8--- Simply replacing 1.5 with 1.4.1 gives us a working scm with no errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-414) Dumbster 1.6 release
Dumbster 1.6 release Key: MAVENUPLOAD-414 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-414 Project: maven-upload-requests Type: Task Reporter: dion gillard http://www.multitask.com.au/dumbster-1.6-bundle.jar http://sourceforge.net/projects/dumbster http://prdownloads.sourceforge.net/dumbster/dumbster1.6-all.zip?download Dumbster is a mock SMTP server. This is release 1.6 compiled against the 1.3 JDK. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1629) Ugly error message when JDK 1.3 is set for JAVA_HOME
[ http://jira.codehaus.org/browse/MAVEN-1629?page=comments#action_41663 ] dion gillard commented on MAVEN-1629: - Either that or check java -version in the shell scripts/batch file, as long as the end-user has a better experience. > Ugly error message when JDK 1.3 is set for JAVA_HOME > > > Key: MAVEN-1629 > URL: http://jira.codehaus.org/browse/MAVEN-1629 > Project: maven > Type: Bug > Components: cli > Versions: 1.1-beta-1 > Environment: JAVA_HOME set to a 1.3 JDK > Reporter: dion gillard > Priority: Minor > > > Is there some nicer message that can be produced than this? > C:\source\wsad\workspace\Deployment>maven > Exception in thread "main" java.lang.UnsupportedClassVersionError: > org/apache/maven/cli/App (Unsupported major.minor version 48.0) > at java.lang.ClassLoader.defineClass0(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:488) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:106) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:243) > at java.net.URLClassLoader.access$100(URLClassLoader.java:51) > at java.net.URLClassLoader$1.run(URLClassLoader.java:190) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:183) > at java.lang.ClassLoader.loadClass(ClassLoader.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:250) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:190) > at com.werken.forehead.Forehead.setupEntry(Forehead.java:298) > at com.werken.forehead.Forehead.config(Forehead.java:256) > at com.werken.forehead.Forehead.config(Forehead.java:131) > at com.werken.forehead.Forehead.main(Forehead.java:579) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1629) Ugly error message when JDK 1.3 is set for JAVA_HOME
Ugly error message when JDK 1.3 is set for JAVA_HOME Key: MAVEN-1629 URL: http://jira.codehaus.org/browse/MAVEN-1629 Project: maven Type: Bug Components: cli Versions: 1.1-beta-1 Environment: JAVA_HOME set to a 1.3 JDK Reporter: dion gillard Priority: Minor Is there some nicer message that can be produced than this? C:\source\wsad\workspace\Deployment>maven Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/maven/cli/App (Unsupported major.minor version 48.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:488) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:106) at java.net.URLClassLoader.defineClass(URLClassLoader.java:243) at java.net.URLClassLoader.access$100(URLClassLoader.java:51) at java.net.URLClassLoader$1.run(URLClassLoader.java:190) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:183) at java.lang.ClassLoader.loadClass(ClassLoader.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:250) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:190) at com.werken.forehead.Forehead.setupEntry(Forehead.java:298) at com.werken.forehead.Forehead.config(Forehead.java:256) at com.werken.forehead.Forehead.config(Forehead.java:131) at com.werken.forehead.Forehead.main(Forehead.java:579) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-406) Upload JasperReports 0.6.7
Upload JasperReports 0.6.7 -- Key: MAVENUPLOAD-406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-406 Project: maven-upload-requests Type: Task Reporter: dion gillard JasperReports 0.6.7 jar http://jasperreports.sourceforge.net This is a new version of the existing project jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
