[jira] Closed: (MNG-1610) locale parameter causes javadoc to fail
[ http://jira.codehaus.org/browse/MNG-1610?page=all ] Allan Ramirez closed MNG-1610: -- Resolution: Duplicate Duplicate of MNG-1163 > locale parameter causes javadoc to fail > --- > > Key: MNG-1610 > URL: http://jira.codehaus.org/browse/MNG-1610 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Versions: 2.0 > Environment: Maven 2.0, maven-javadoc-plugin v2.0-beta-2 > Reporter: Anuerin Diaz > Assignee: Allan Ramirez > > > Using the following configuration > >org.apache.maven.plugins >maven-javadoc-plugin > > en_US > > > the javadoc execution fails with: > [INFO] An error has occurred in JavaDocs report generation. > Embedded error: Exit code: 1 - javadoc: option -locale must be first on the > command line. -- 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: (MNG-1163) option -locale must be first on the command line.
[ http://jira.codehaus.org/browse/MNG-1163?page=comments#action_53543 ] Allan Ramirez commented on MNG-1163: javadoc plugin release is now on its way :D > option -locale must be first on the command line. > - > > Key: MNG-1163 > URL: http://jira.codehaus.org/browse/MNG-1163 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Versions: 2.0-beta-3 > Environment: Windows XP > Reporter: Martin Desruisseaux > Assignee: Brett Porter > Priority: Minor > Fix For: 2.0 (RC) > > > Providing a parameter currently cause a javadoc failure because the > maven-javadoc-plugin put the -locale option after some other options like > -encoding. According the javadoc tool documentation > (http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#locale), > the -locale parameter must be first. -- 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] Closed: (MNG-1644) parent pom = child pom results in stack overflow error
[ http://jira.codehaus.org/browse/MNG-1644?page=all ] Edwin Punzalan closed MNG-1644: --- Assign To: Edwin Punzalan Resolution: Fixed > parent pom = child pom results in stack overflow error > -- > > Key: MNG-1644 > URL: http://jira.codehaus.org/browse/MNG-1644 > Project: Maven 2 > Type: Improvement > Versions: 2.0 > Reporter: Jorg Heymans > Assignee: Edwin Punzalan > Fix For: 2.0.3 > > > Though it's a stupid thing to do, if you define > > > excalibur > excalibur > 1.0 > > 4.0.0 > excalibur > excalibur > 1.0 > Excalibur Components > pom > > .. ... > > you get : > d:\src\excalibur-trunk>mvn > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.StackOverflowError > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Mon Nov 21 18:29:03 CET 2005 > [INFO] Final Memory: 1M/4M > [INFO] > > A better error message would be nice here. -- 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] Closed: (MNG-1510) site-embedded report mode check always returns true
[ http://jira.codehaus.org/browse/MNG-1510?page=all ] Allan Ramirez closed MNG-1510: -- Resolution: Fixed Done > site-embedded report mode check always returns true > --- > > Key: MNG-1510 > URL: http://jira.codehaus.org/browse/MNG-1510 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Versions: 2.0 > Reporter: Shinobu Kawai Yoshida > Assignee: Allan Ramirez > Attachments: MNG-1510.patch > > > o.a.m.p.javadoc.JavadocReport#executeReport > Line 685: if ( !javadocDirectory.equals( getOutputDirectory() ) ) > javadocDirectory is a File and getOutputDirectory() is a String. This will > never return false. -- 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: (MNG-1832) built-in property containing current timestamp
[ http://jira.codehaus.org/browse/MNG-1832?page=comments#action_53539 ]
Piotr Bzdyl commented on MNG-1832:
--
It would be very helpful in filling some properties files to get built-time at
the artifact runtime to identify the version. It would be also helpful to have
property with the current checkout revision (ie. ${scm.currentRevision}). Then
I could use in the resources.properties:
app.builtOn=${timestamp}
app.scmVersion=${scm.currentRevision}
I can use $Revision$ or $LastChangedRevision$ because I would have to remember
to modify and commit that properties file before building.
> built-in property containing current timestamp
> --
>
> Key: MNG-1832
> URL: http://jira.codehaus.org/browse/MNG-1832
> Project: Maven 2
> Type: New Feature
> Versions: 2.0.1
> Reporter: Michal Stochmialek
>
>
> Current timestamp (time or date) is often used while filtering resources or
> creating manifest in ant builds. There is no equivalent in maven.
--
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: (MNG-1689) Only print relocation warnings in standard output for the current pom
[ http://jira.codehaus.org/browse/MNG-1689?page=all ] Edwin Punzalan updated MNG-1689: Attachment: MNG-1689-maven-project.patch > Only print relocation warnings in standard output for the current pom > - > > Key: MNG-1689 > URL: http://jira.codehaus.org/browse/MNG-1689 > Project: Maven 2 > Type: Improvement > Components: Logging > Versions: 2.0 > Reporter: Carlos Sanchez > Assignee: Edwin Punzalan > Fix For: 2.0.3 > Attachments: MNG-1689-maven-project.patch > > > Relocation warnings of transitive dependencies shouldn't be printed in > standard output because people gets confused, ask questions and try to change > other people poms although they work correctly > We should only print the warnings of the current pom so the author can > improve it. -- 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: (MNG-1854) display summary information including number of compiler errors when compiler plugin fails.
display summary information including number of compiler errors when compiler plugin fails. --- Key: MNG-1854 URL: http://jira.codehaus.org/browse/MNG-1854 Project: Maven 2 Type: New Feature Components: maven-compiler-plugin Versions: 2.0.1 Reporter: John Casey Priority: Minor -- 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: (MNG-1853) Evaluate project variables within assembly descriptors
Evaluate project variables within assembly descriptors
--
Key: MNG-1853
URL: http://jira.codehaus.org/browse/MNG-1853
Project: Maven 2
Type: Improvement
Components: maven-assembly-plugin
Versions: 2.0.1
Reporter: Travis Carlson
Currently any project variables (for example ${basedir}, ${artifact}, etc.) are
ignored within the assembly descriptor.
--
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: (MNG-1578) mvn assembly:assembly fails if there is no target directory already present
[ http://jira.codehaus.org/browse/MNG-1578?page=comments#action_53536 ] Travis Carlson commented on MNG-1578: - A workaround for this is to change the module's from "pom" to "jar", even if the empty jar produced is ignored. This will force the target directory to be created. > mvn assembly:assembly fails if there is no target directory already present > --- > > Key: MNG-1578 > URL: http://jira.codehaus.org/browse/MNG-1578 > Project: Maven 2 > Type: Bug > Components: maven-assembly-plugin > Reporter: Matthew Pocock > Priority: Minor > Attachments: MNG1578.patch > > > I have a module that is of type pom. Its job is to agregate a set of > dependencies. I want to build a distribution from these, so I tried the > assembly plugin. I did get it to work. However, on the way I got this error: > [INFO] [assembly:assembly] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error creating assembly: > /home/nmrp3/devel/derkholm/bjv2/trunk/clis/cli/target isn't a directory. > A build for a pom project doesn't make a target directory. But, > assembly:assembly requires one. I've made the directory manually and now the > assembly builds just fine. The stack-trace is below. I've modified my > assembly descriptor file to not mention target/** at all, and it now builds > just fine without the target directory being present. > The path of least suprise for the end-user would be to behave as if there > were no files to find if target is absent and a search is done within target > for files. > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error creating > assembly: /home/nmrp3/devel/derkholm/bjv2/trunk/clis/cli/target isn't a > directory. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:544) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:452) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:243) > 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating > assembly: /home/nmrp3/devel/derkholm/bjv2/trunk/clis/cli/target isn't a > directory. > at > org.apache.maven.plugin.assembly.AssemblyMojo.execute(AssemblyMojo.java:173) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > ... 16 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: > /home/nmrp3/devel/derkholm/bjv2/trunk/clis/cli/target isn't a directory. > at > org.codehaus.plexus.archiver.AbstractArchiver.addDirectory(AbstractArchiver.java:125) > at > org.apache.maven.plugin.assembly.AssemblyMojo.addDirectory(AssemblyMojo.java:377) > at > org.apache.maven.plugin.assembly.AssemblyMojo.processFileSets(AssemblyMojo.java:459) > at > org.apache.maven.plugin.assembly.AssemblyMojo.createArchive(AssemblyMojo.java:209) > at > org.apache.maven.plugin.assembly.AssemblyMojo.execute(AssemblyMojo.java:165) > ... 18 more > [INFO] > > [INFO] Total time: 8 seconds > [INFO] Finished at: Tue Nov 15 16:03:51 GMT 2005 > [INFO] Final Memory: 3M/6M > [INFO] >
[jira] Commented: (MNG-1734) In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory
[ http://jira.codehaus.org/browse/MNG-1734?page=comments#action_53535 ]
Travis Carlson commented on MNG-1734:
-
Actually I think the path is relative to the current working directory (i.e.,
the directory from which the "mvn" command was executed. This means the
workaround is to either base your paths on the root and always execute "mvn"
from the root, OR base your paths on the sub-project (the way they _should_ be)
and always execute "mvn" from within the sub-project.
> In a multi-module build, assembly descriptor paths are not project-relative,
> but erraneously relative to the parent project directory
> -
>
> Key: MNG-1734
> URL: http://jira.codehaus.org/browse/MNG-1734
> Project: Maven 2
> Type: Bug
> Components: maven-assembly-plugin
> Versions: 2.0
> Environment: WinXP SP2
> Maven 2
> Reporter: Michael Böckling
>
>
> When I try to perform a multi-module build executed in a build-only
> (packaging=pom) parent project ("AAH-1-Genius-Build"), assembly fails. I
> defined an assembly:assembly execution bound to the "install" phase in the
> "AAH-1-Genius-TpmMonitor" sub-project using my own descriptor. Maven finds
> the descriptor, but the (relative) paths in the descriptor are not expanded
> against the "AAH-1-Genius-TpmMonitor" sub-project, but against the
> "AAH-1-Genius-Build" parent-project, which of course stops the build.
> The last line of the error log below shouldnt be
> "C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\src\extern", it should
> be "C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-TpmMonitor\src\extern"!
> I also tried using ${basedir} and such, but unfortunately those variables
> don't get expanded. I also tried activating "includeBaseDirectory" in the
> descriptor, hoping it would prepend the current project path to the
> descriptor paths (I had to guess since its not documented...), but no luck.
> Beside the obvious bug concerning project directory, I really think maven
> vars should be expanded.
> Error log:
> [INFO] [assembly:assembly {execution: prepare-assembly}]
> [INFO] Expanding:
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1
> -Genius-BusinessLib\target\aah-genius-business-lib-1.0-SNAPSHOT.jar into
> C:\DEVE
> LOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1-Genius-TpmMonitor\target
> \assembly\work\aah-genius-business-lib-1.0-SNAPSHOT
> [INFO] Expanding:
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1
> -Genius-MappingLib\target\aah-genius-mapping-lib-1.0-SNAPSHOT.jar into
> C:\DEVELO
> PMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1-Genius-TpmMonitor\target\a
> ssembly\work\aah-genius-mapping-lib-1.0-SNAPSHOT
> [INFO]
> -
> ---
> [ERROR] BUILD ERROR
> [INFO]
> -
> ---
> [INFO] Error creating assembly
> Embedded error:
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\src\extern
> isn't a directory.
> [INFO]
> -
--
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-641) Upload beandoc-0.7.0 to ibiblio
Upload beandoc-0.7.0 to ibiblio --- Key: MAVENUPLOAD-641 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-641 Project: maven-upload-requests Type: Task Reporter: Matt Raible Please upload beandoc - it's a wicked tool that allows you to create javadoc-like reports for your Spring context files. -- 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: (MAVENUPLOAD-637) Please upload Struts HTML Taglib 1.2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-637?page=comments#action_53532 ] Yann Le Du commented on MAVENUPLOAD-637: Filed in Struts : http://issues.apache.org/bugzilla/show_bug.cgi?id=37927 > Please upload Struts HTML Taglib 1.2.4 > -- > > Key: MAVENUPLOAD-637 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-637 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > -- 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: (MPJAVADOC-51) Allow javadoc report to be surpressed
[ http://jira.codehaus.org/browse/MPJAVADOC-51?page=comments#action_53531 ] Arnaud Heritier commented on MPJAVADOC-51: -- you can call "maven javadoc". Isn't it what you want ? > Allow javadoc report to be surpressed > - > > Key: MPJAVADOC-51 > URL: http://jira.codehaus.org/browse/MPJAVADOC-51 > Project: maven-javadoc-plugin > Type: Improvement > Reporter: Phil Steitz > > > It would be nice to be able to generate apidocs without the javadoc report > being added to the project web site. -- 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: (MNG-1852) The maven-ear-plugin does not support SAR files.
The maven-ear-plugin does not support SAR files. Key: MNG-1852 URL: http://jira.codehaus.org/browse/MNG-1852 Project: Maven 2 Type: Bug Components: maven-ear-plugin Versions: 2.0 Environment: Maven 2.0.1, maven-ear-plugin 2.0, Windows XP. Reporter: Jay Stramel Building an ear file will fail if the ear file requires a SAR file as one of it's components. -- 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] Closed: (MNG-1850) Error: Duplicate project ID found in pom
[ http://jira.codehaus.org/browse/MNG-1850?page=all ] John Casey closed MNG-1850: --- Resolution: Duplicate Fix Version: 2.0.2 duplicate of MNG-1851. Closing this, because the other one has details embedded in the description, rather than on an external site. > Error: Duplicate project ID found in pom > > > Key: MNG-1850 > URL: http://jira.codehaus.org/browse/MNG-1850 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Versions: 2.0.1 > Reporter: Chad Berghorst > Assignee: John Casey > Priority: Blocker > Fix For: 2.0.2 > > > With the 2.0.1 release of the Ant tasks, we are experiencing the same issue > as described in this user list e-mail: > http://www.nabble.com/-m2.0.1-antlib-error---Duplicate-project-ID-found-in-pom.-t736287.html > However, we seem to get the error even if we do not specify a parent POM. -- 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-640) Please upload Struts Tiles Taglib 1.2.4
Please upload Struts Tiles Taglib 1.2.4 --- Key: MAVENUPLOAD-640 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-640 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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-639) Please upload Struts Nested Taglib 1.2.4
Please upload Struts Nested Taglib 1.2.4 Key: MAVENUPLOAD-639 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-639 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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: (MAVENUPLOAD-637) Please upload Struts HTML Taglib 1.2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-637?page=comments#action_53522 ] Carlos Sanchez commented on MAVENUPLOAD-637: You should ask first to struts developers to put it in the maven repository at apache > Please upload Struts HTML Taglib 1.2.4 > -- > > Key: MAVENUPLOAD-637 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-637 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > -- 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-638) Please upload Struts Logic Taglib 1.2.4
Please upload Struts Logic Taglib 1.2.4 --- Key: MAVENUPLOAD-638 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-638 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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-637) Please upload Struts HTML Taglib 1.2.4
Please upload Struts HTML Taglib 1.2.4 -- Key: MAVENUPLOAD-637 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-637 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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-636) Please upload Struts Bean Taglib 1.2.4
Please upload Struts Bean Taglib 1.2.4 -- Key: MAVENUPLOAD-636 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-636 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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: (MNG-1851) "Duplicate project ID found" message with maven-artifact-ant-2.0.1
"Duplicate project ID found" message with maven-artifact-ant-2.0.1 -- Key: MNG-1851 URL: http://jira.codehaus.org/browse/MNG-1851 Project: Maven 2 Type: Bug Components: Ant tasks Versions: 2.0.1 Reporter: John Casey Assigned to: John Casey Priority: Blocker Fix For: 2.0.2 from the original email: I tried upgrading my Maven 2 Ant Tasks' JAR tonight, and after doing so, I'm getting the following error: foxxy:~/dev/equinox mraible$ ant war Buildfile: build.xml init: [artifact:dependencies] An error has occurred while processing the Maven artifact tasks. [artifact:dependencies] Diagnosis: [artifact:dependencies] [artifact:dependencies] Unable to build project: /Users/mraible/Work/equinox/pom.xml [artifact:dependencies] Duplicate project ID found in /Users/mraible/Work/equinox/pom.xml BUILD FAILED /Users/mraible/Work/equinox/build.xml:27: Unable to build project: /Users/mraible/Work/equinox/pom.xml Total time: 2 seconds foxxy:~/dev/equinox mraible$ I haven't been able to find the "duplicate project id" the error is referring to. The strange thing is if I run "mvn package" on my project, everything works fine with Maven 2.0.1. If I revert my maven-artifact-ant-2.0.1-dep.jar to maven-artifact-ant-2.0-dep.jar, everything works as expected. Here's how I declare the Maven Ant tasks in my build.xml: Here's line 27 of build.xml: Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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] Closed: (MPJAVADOC-65) add a properties to jxr and javadoc plugins to be able to disable reports that are not needed (Test Xref, JavaDoc Warnings Report)
[ http://jira.codehaus.org/browse/MPJAVADOC-65?page=all ] Lukas Theussl closed MPJAVADOC-65: -- Resolution: Fixed Fix Version: 1.8 > add a properties to jxr and javadoc plugins to be able to disable reports > that are not needed (Test Xref, JavaDoc Warnings Report) > -- > > Key: MPJAVADOC-65 > URL: http://jira.codehaus.org/browse/MPJAVADOC-65 > Project: maven-javadoc-plugin > Type: Improvement > Environment: Windows XP > Reporter: Tigran Antonyan > Priority: Trivial > Fix For: 1.8 > > > I don't need some of the reports that are generated by default, i.e. Test > Xref and JavaDoc Warning Report (this is always empty in my case) so I would > prefer to have a way of specifying the reports that I don't need (this will > save me some time generating the reports as well). > -Tigran Antonyan -- 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: (MNG-1850) Error: Duplicate project ID found in pom
Error: Duplicate project ID found in pom Key: MNG-1850 URL: http://jira.codehaus.org/browse/MNG-1850 Project: Maven 2 Type: Bug Components: Ant tasks Versions: 2.0.1 Reporter: Chad Berghorst Priority: Blocker With the 2.0.1 release of the Ant tasks, we are experiencing the same issue as described in this user list e-mail: http://www.nabble.com/-m2.0.1-antlib-error---Duplicate-project-ID-found-in-pom.-t736287.html However, we seem to get the error even if we do not specify a parent POM. -- 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]
Re: [vote] Release Maven 2.0.1-1 critical bugfix version
On Wed, 2005-12-14 at 15:23 -0500, John Casey wrote: > I'm not too interested in which version number we use; I only suggested > this notation since it's definitely a lot smaller than what we did for > 2.0.1, and what we've got slated for 2.0.2...that, and it's meant to > modify the 2.0.1 release so it'll work. > > 2.0.2 is fine with me. I can push the other stuff off to 2.0.3. > > What about the vote? +1 for 2.0.2 -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-629) Jini version 2.1 final starter kit jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-629?page=all ] Carlos Sanchez closed MAVENUPLOAD-629: -- Assign To: Carlos Sanchez Resolution: Fixed > Jini version 2.1 final starter kit jars > --- > > Key: MAVENUPLOAD-629 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-629 > Project: maven-upload-requests > Type: Bug > Reporter: Chris Sterling > Assignee: Carlos Sanchez > > > http://daredskin.homedns.org/checkconfigurationfile-2.1-bundle.jar > http://daredskin.homedns.org/checkser-2.1-bundle.jar > http://daredskin.homedns.org/classdep-2.1-bundle.jar > http://daredskin.homedns.org/classserver-2.1-bundle.jar > http://daredskin.homedns.org/computedigest-2.1-bundle.jar > http://daredskin.homedns.org/computehttpmdcodebase-2.1-bundle.jar > http://daredskin.homedns.org/destroy-2.1-bundle.jar > http://daredskin.homedns.org/envcheck-2.1-bundle.jar > http://daredskin.homedns.org/group-2.1-bundle.jar > http://daredskin.homedns.org/jarwrapper-2.1-bundle.jar > http://daredskin.homedns.org/jini-core-2.1-bundle.jar > http://daredskin.homedns.org/jini-ext-2.1-bundle.jar > http://daredskin.homedns.org/jini-starterkit-2.1-bundle.jar > http://daredskin.homedns.org/jini-start-examples-2.1-bundle.jar > http://daredskin.homedns.org/jsk-lib-2.1-bundle.jar > http://daredskin.homedns.org/jsk-platform-2.1-bundle.jar > http://daredskin.homedns.org/jsk-resources-2.1-bundle.jar > http://daredskin.homedns.org/sun-util-2.1-bundle.jar > http://daredskin.homedns.org/tools-2.1-bundle.jar > http://www.jini.org/ > This is as close to a team link that I could find: > http://www.jini.org/Contrib_Award/index.html > Jini version 2.1 specifications and reference implementations are licensed > under the Apache 2.0 license. I think it would be great to have the Jini base > jars in the Maven repository to support a Maven Jini Plug-in, > (http://maven-jini-plugin.jini.org/) that is going version 1.1. Thank you. -- 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] Closed: (MEV-260) [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid.
[ http://jira.codehaus.org/browse/MEV-260?page=all ] Carlos Sanchez closed MEV-260: -- Assign To: Carlos Sanchez Resolution: Fixed > [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid. > -- > > Key: MEV-260 > URL: http://jira.codehaus.org/browse/MEV-260 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Matt Brozowski > Assignee: Carlos Sanchez > > > [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid. It will be > ignored for artifact resolution. Reason: Parse error reading POM. Reason: > expected START_TAG or END_TAG not TEXT (position: TEXT seen > ...pom For some reason the plexus-compiler-api has packaging 'pom' this package > produces a jar file. > The line pom should be removed. > (NOTE: This is different that the previous bug I wrote about the parent being > NOT packaged as pom) -- 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] Closed: (MAVENUPLOAD-633) Please Upload Registry CDC
[ http://jira.codehaus.org/browse/MAVENUPLOAD-633?page=all ] Carlos Sanchez closed MAVENUPLOAD-633: -- Assign To: Carlos Sanchez Resolution: Fixed > Please Upload Registry CDC > -- > > Key: MAVENUPLOAD-633 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-633 > Project: maven-upload-requests > Type: Task > Reporter: Shane Isbell > Assignee: Carlos Sanchez > > > http://prdownloads.sourceforge.net/jvending/registry-cdc-1.0.0-bundle.jar?download > http://jvending.sourceforge.net/registry-cdc > http://jvending.sourceforge.net/registry-cdc/team-list.html > Registry-CDC provides a registry function for storing and finding data, in > particular configuration information. Please upload. -- 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: (MPJAVADOC-51) Allow javadoc report to be surpressed
[ http://jira.codehaus.org/browse/MPJAVADOC-51?page=comments#action_53513 ] Lukas Theussl commented on MPJAVADOC-51: I'm not sure what you mean here, but you could just leave away the maven-javadoc-plugin from the project.xml? > Allow javadoc report to be surpressed > - > > Key: MPJAVADOC-51 > URL: http://jira.codehaus.org/browse/MPJAVADOC-51 > Project: maven-javadoc-plugin > Type: Improvement > Reporter: Phil Steitz > > > It would be nice to be able to generate apidocs without the javadoc report > being added to the project web site. -- 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: (MAVENUPLOAD-635) upload hibernate-annotations-3.1beta7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-635?page=comments#action_53511 ] Carlos Sanchez commented on MAVENUPLOAD-635: If you don't provide a bundle this will have to wait > upload hibernate-annotations-3.1beta7 > - > > Key: MAVENUPLOAD-635 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-635 > Project: maven-upload-requests > Type: Wish > Reporter: Juan F. Codagnone > > > Now that hibernate 3.1 is in ibliblio (MAVENUPLOAD-630) it would nice to have > hibernate-annotations-3.1beta7 (beta5 worked against rc but not with final). > (i compiled and have it in my local repository, but it would nice for > completness. -- 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] Closed: (MAVENUPLOAD-634) Upload M9 "cayenne" and "cayenne-nodeps" bundles
[ http://jira.codehaus.org/browse/MAVENUPLOAD-634?page=all ] Carlos Sanchez closed MAVENUPLOAD-634: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload M9 "cayenne" and "cayenne-nodeps" bundles > > > Key: MAVENUPLOAD-634 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-634 > Project: maven-upload-requests > Type: Task > Reporter: Andrus Adamchik > Assignee: Carlos Sanchez > > > This is a request to upload new Cayenne release bundles (we are already on > Ibiblio - see MAVENUPLOAD-565) > Two bundle URLs: > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-1.2M9-bundle.jar > http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-nodeps-1.2M9-bundle.jar > 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] Closed: (MPJAVADOC-21) Can't generate javadoc in directories with whitspace
[ http://jira.codehaus.org/browse/MPJAVADOC-21?page=all ] Lukas Theussl closed MPJAVADOC-21: -- Resolution: Won't Fix The ant bug (#16871 ) has been fixed in ant-1.6. > Can't generate javadoc in directories with whitspace > > > Key: MPJAVADOC-21 > URL: http://jira.codehaus.org/browse/MPJAVADOC-21 > Project: maven-javadoc-plugin > Type: Bug > Environment: Windows > Reporter: Hugo Palma > > > Since rc2 i haven't been able to generate any javadoc at all for my projects. > All my projects are in a directory that has whitespaces in them and this > seems to be the problem. > For example, for a project that i have in "C:\Documents and > Settings\in000101\My Documents\Projectos\SocketClient" when i try to generate > the javadoc i get: > xdoc:init: > [mkdir] Created dir: C:\Documents and Settings\in000101\My > Documents\Project > os\SocketClient\target\generated-xdocs > [mkdir] Created dir: C:\Documents and Settings\in000101\My > Documents\Project > os\SocketClient\target\docs > maven-javadoc-plugin:report: > [mkdir] Created dir: C:\Documents and Settings\in000101\My > Documents\Project > os\SocketClient\target\docs\apidocs > [mkdir] Created dir: C:\Documents and Settings\in000101\My > Documents\Project > os\SocketClient\target\javadoc > [javadoc] Generating Javadoc > [javadoc] Javadoc execution > [javadoc] javadoc: Illegal package name: "C:\Documents" > [javadoc] javadoc: Illegal package name: "Settings\in000101\My" > [javadoc] javadoc: File not found: > "Documents\Projectos\SocketClient\src\jav > a\pt\euro2004\sdk\DataEventHandler.java" > [javadoc] javadoc: Illegal package name: "C:\Documents" > [javadoc] javadoc: Illegal package name: "Settings\in000101\My" > [javadoc] javadoc: File not found: > "Documents\Projectos\SocketClient\src\jav > a\pt\euro2004\sdk\GenevaAdapter.java" > [javadoc] javadoc: Illegal package name: "C:\Documents" > [javadoc] Loading source files for package and... > [javadoc] Loading source files for package and... > [javadoc] Loading source files for package and... > [javadoc] 9 errors > [javadoc] 3 warnings > [javadoc] javadoc: Illegal package name: "Settings\in000101\My" > [javadoc] javadoc: File not found: > "Documents\Projectos\SocketClient\src\jav > a\pt\euro2004\sdk\SocketManager.java" > [javadoc] javadoc: warning - No source files for package and > [javadoc] javadoc: warning - No source files for package and > [javadoc] javadoc: warning - No source files for package and > BUILD SUCCESSFUL > Total time: 5 seconds > Finished at: Thu Mar 25 15:14:53 GMT 2004 > I repeat, this has only started to happen upon the upgrade to rc2. -- 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: (MPJAVADOC-53) "maven javadoc clean" fails
[ http://jira.codehaus.org/browse/MPJAVADOC-53?page=comments#action_53509 ] Lukas Theussl commented on MPJAVADOC-53: I cannot reproduce this, neither with m102 nor m11b3. I will close this issue unless somebody re-confirms. > "maven javadoc clean" fails > --- > > Key: MPJAVADOC-53 > URL: http://jira.codehaus.org/browse/MPJAVADOC-53 > Project: maven-javadoc-plugin > Type: Bug > Versions: 1.7 > Environment: WinXP, Win2000 Pro and Maven 1.0.2 > Reporter: Andrei Szabo > Priority: Minor > > > If one runs "maven javadoc" and "maven clean" afterwards, everything works as > expected. However, if one uses "maven javadoc clean" the build fails w/ an > error message. > Very easy to reproduce; use: > a. >maven genapp > b. >maven javadoc clean > The build fails with something along the lines: > > clean:clean: > [delete] Deleting directory E:\Code\MavenDummyTest\target > BUILD FAILED > File.. C:\Documents and > Settings\Andrei\.maven\cache\maven-clean-plugin-1.3\plugin.jelly > Element... ant:delete > Line.. 30 > Column 43 > Unable to delete file E:\Code\MavenDummyTest\target\javadoc\report.txt > Total time: 15 seconds > Finished at: Sat Apr 02 12:38:16 EEST 2005 > Issuing "maven clean" right after "maven javadoc clean" does succesfully > remove the file in question, namely "report.txt". -- 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] Closed: (SCM-108) JDK 1.5 code
[ http://jira.codehaus.org/browse/SCM-108?page=all ] Dan Tran closed SCM-108: Resolution: Fixed Fix Version: 1.0-beta-3 applied and thanks > JDK 1.5 code > > > Key: SCM-108 > URL: http://jira.codehaus.org/browse/SCM-108 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-clearcase > Reporter: mike perham > Assignee: Dan Tran > Fix For: 1.0-beta-3 > Attachments: clearcase-108.patch > > > [INFO] Compilation failure > D:\apache\maven-scm\maven-scm-providers\maven-scm-provider-clearcase\src\main\java\org\apache\maven\ > scm\provider\clearcase\repository\ClearCaseScmProviderRepository.java:[113,31] > cannot resolve symbol > symbol : method toURI () > location: class java.net.URL -- 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
[jira] Created: (MAVENUPLOAD-635) upload hibernate-annotations-3.1beta7
upload hibernate-annotations-3.1beta7 - Key: MAVENUPLOAD-635 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-635 Project: maven-upload-requests Type: Wish Reporter: Juan F. Codagnone Now that hibernate 3.1 is in ibliblio (MAVENUPLOAD-630) it would nice to have hibernate-annotations-3.1beta7 (beta5 worked against rc but not with final). (i compiled and have it in my local repository, but it would nice for completness. -- 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]
Re: svn commit: r357051 - in /maven/maven-1/plugins/trunk/javadoc: plugin.properties xdocs/changes.xml xdocs/properties.xml
I followed the advice at MPJAVADOC-66, I don't know if it can lead to problems? I checked the ant documentation and didn't find anything that would warn against it. And is 512 really such an awful lot? I thought my laptop was old... -Lukas Brett Porter wrote: Are you sure that's a good idea? That's an aweful lot of memory. - Brett [EMAIL PROTECTED] wrote: Author: ltheussl Date: Thu Dec 15 10:15:34 2005 New Revision: 357051 URL: http://svn.apache.org/viewcvs?rev=357051&view=rev Log: PR: MPJAVADOC-66 The maxmemory property is set to 512m by default. Modified: maven/maven-1/plugins/trunk/javadoc/plugin.properties maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml Modified: maven/maven-1/plugins/trunk/javadoc/plugin.properties URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/plugin.properties?rev=357051&r1=357050&r2=357051&view=diff == --- maven/maven-1/plugins/trunk/javadoc/plugin.properties (original) +++ maven/maven-1/plugins/trunk/javadoc/plugin.properties Thu Dec 15 10:15:34 2005 @@ -38,7 +38,7 @@ #specify an alternate locale #maven.javadoc.locale = en_US -#maven.javadoc.maxmemory= +maven.javadoc.maxmemory = 512m #maven.javadoc.mode.online = #maven.javadoc.offlineLinks = Modified: maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml?rev=357051&r1=357050&r2=357051&view=diff == --- maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml Thu Dec 15 10:15:34 2005 @@ -27,6 +27,7 @@ + The maxmemory property is set to 512m by default. StringIndexOutOfBoundsException on parsing the files. Files package.html and overview.html are not copied when source modifications are used. Added maven.javadoc.failonerror property. Modified: maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml?rev=357051&r1=357050&r2=357051&view=diff == --- maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml (original) +++ maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml Thu Dec 15 10:15:34 2005 @@ -89,7 +89,7 @@ Specifies the maximum Java heap size to be used when launching the javadoc executable. Some JVMs refer to this property as -the -Xmx parameter. +the -Xmx parameter. Defaults to 512m. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJAVADOC-62) maven.javadoc.customtags cannot handle dashes (-)
[ http://jira.codehaus.org/browse/MPJAVADOC-62?page=all ] Lukas Theussl closed MPJAVADOC-62: -- Resolution: Won't Fix Documented in properties.xml. > maven.javadoc.customtags cannot handle dashes (-) > - > > Key: MPJAVADOC-62 > URL: http://jira.codehaus.org/browse/MPJAVADOC-62 > Project: maven-javadoc-plugin > Type: Bug > Versions: 1.7 > Reporter: Felipe Leme > > > Due to that famous JEXL limitation, if a custom tag has dashes, such tag will > be ignored by the plugin. For instance, even if I set: > myTag.ejb.interface_method.enabled=false > myTag.ejb.interface_method.name=ejb.interface-method > myTag.ejb.interface_method.description=ejbdoclet tag > myTag.ejb.interface_method.scope=all > maven.javadoc.customtags=myTag.ejb.interface_method > I get: > [javadoc] bla-bla-blaBean.java:241: warning - @ejb.interface-method is an > unknown tag. > I think this issue has been fixed in most recent versions of commons-jexl; > not sure how we can apply them to the plugin though (it might be necessary to > fix it at the maven 1.x core level). -- 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]
Re: svn commit: r357051 - in /maven/maven-1/plugins/trunk/javadoc:plugin.properties xdocs/changes.xml xdocs/properties.xml
It is a maximum, so there really shouldn't be a problem in most cases -- I think the intended goal is to simply avoid failures due to having too small of a value. Just my .02, -- Eric On Thu, 2005-12-15 at 11:18, Brett Porter wrote: > Are you sure that's a good idea? That's an aweful lot of memory. > > - Brett > > [EMAIL PROTECTED] wrote: > > Author: ltheussl > > Date: Thu Dec 15 10:15:34 2005 > > New Revision: 357051 > > > > URL: http://svn.apache.org/viewcvs?rev=357051&view=rev > > Log: > > PR: MPJAVADOC-66 > > The maxmemory property is set to 512m by default. > > > > Modified: > > maven/maven-1/plugins/trunk/javadoc/plugin.properties > > maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml > > maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml > > > > Modified: maven/maven-1/plugins/trunk/javadoc/plugin.properties > > URL: > > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/plugin.properties?rev=357051&r1=357050&r2=357051&view=diff > > == > > --- maven/maven-1/plugins/trunk/javadoc/plugin.properties (original) > > +++ maven/maven-1/plugins/trunk/javadoc/plugin.properties Thu Dec 15 > > 10:15:34 2005 > > @@ -38,7 +38,7 @@ > > > > #specify an alternate locale > > #maven.javadoc.locale = en_US > > -#maven.javadoc.maxmemory= > > +maven.javadoc.maxmemory = 512m > > > > #maven.javadoc.mode.online = > > #maven.javadoc.offlineLinks = > > > > Modified: maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml > > URL: > > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml?rev=357051&r1=357050&r2=357051&view=diff > > == > > --- maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml (original) > > +++ maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml Thu Dec 15 > > 10:15:34 2005 > > @@ -27,6 +27,7 @@ > > > > > > > > + The > > maxmemory property is set to 512m by default. > > > issue="MPJAVADOC-61">StringIndexOutOfBoundsException on parsing the > > files. > >Files > > package.html and overview.html are not copied when source modifications are > > used. > >Added > > maven.javadoc.failonerror property. > > > > Modified: maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml > > URL: > > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml?rev=357051&r1=357050&r2=357051&view=diff > > == > > --- maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml (original) > > +++ maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml Thu Dec 15 > > 10:15:34 2005 > > @@ -89,7 +89,7 @@ > > > > Specifies the maximum Java heap size to be used when launching > > the javadoc executable. Some JVMs refer to this property as > > -the -Xmx parameter. > > +the -Xmx parameter. Defaults to 512m. > > > > > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Continuum refactoring
On Wed, 2005-12-14 at 14:58 -0800, Carlos Sanchez wrote: > On 12/14/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > > I still disagree with splitting up the ContinuumStore into a set of > > DAOs. I've never seen the advantage of having a single DAO for each > > domain object. > > They will be reusable in other applicaitons. If we're thinking about > creting other applications, like repository manager, we'll share a lot > of common objects between them. I have yet to see an example of this idea working in real life. I understand that you'd want to manage different sets of objects, but like in Continuum the Project and Build objects are to tightly coupled that you can't possibly store Project objects in one database and the Build objects in another. -- Trygve
Re: svn commit: r357051 - in /maven/maven-1/plugins/trunk/javadoc: plugin.properties xdocs/changes.xml xdocs/properties.xml
Are you sure that's a good idea? That's an aweful lot of memory. - Brett [EMAIL PROTECTED] wrote: > Author: ltheussl > Date: Thu Dec 15 10:15:34 2005 > New Revision: 357051 > > URL: http://svn.apache.org/viewcvs?rev=357051&view=rev > Log: > PR: MPJAVADOC-66 > The maxmemory property is set to 512m by default. > > Modified: > maven/maven-1/plugins/trunk/javadoc/plugin.properties > maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml > maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml > > Modified: maven/maven-1/plugins/trunk/javadoc/plugin.properties > URL: > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/plugin.properties?rev=357051&r1=357050&r2=357051&view=diff > == > --- maven/maven-1/plugins/trunk/javadoc/plugin.properties (original) > +++ maven/maven-1/plugins/trunk/javadoc/plugin.properties Thu Dec 15 10:15:34 > 2005 > @@ -38,7 +38,7 @@ > > #specify an alternate locale > #maven.javadoc.locale = en_US > -#maven.javadoc.maxmemory= > +maven.javadoc.maxmemory = 512m > > #maven.javadoc.mode.online = > #maven.javadoc.offlineLinks = > > Modified: maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml > URL: > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml?rev=357051&r1=357050&r2=357051&view=diff > == > --- maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml (original) > +++ maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml Thu Dec 15 10:15:34 > 2005 > @@ -27,6 +27,7 @@ > > > > + The > maxmemory property is set to 512m by default. > issue="MPJAVADOC-61">StringIndexOutOfBoundsException on parsing the > files. >Files > package.html and overview.html are not copied when source modifications are > used. >Added > maven.javadoc.failonerror property. > > Modified: maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml > URL: > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml?rev=357051&r1=357050&r2=357051&view=diff > == > --- maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml (original) > +++ maven/maven-1/plugins/trunk/javadoc/xdocs/properties.xml Thu Dec 15 > 10:15:34 2005 > @@ -89,7 +89,7 @@ > > Specifies the maximum Java heap size to be used when launching > the javadoc executable. Some JVMs refer to this property as > -the -Xmx parameter. > +the -Xmx parameter. Defaults to 512m. > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-260) [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid.
[WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid. -- Key: MEV-260 URL: http://jira.codehaus.org/browse/MEV-260 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Matt Brozowski [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: expected START_TAG or END_TAG not TEXT (position: TEXT seen ...pompom should be removed. (NOTE: This is different that the previous bug I wrote about the parent being NOT packaged as pom) -- 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] Closed: (MPJAVADOC-66) change default mem settings
[ http://jira.codehaus.org/browse/MPJAVADOC-66?page=all ] Lukas Theussl closed MPJAVADOC-66: -- Resolution: Fixed Fix Version: 1.8 > change default mem settings > --- > > Key: MPJAVADOC-66 > URL: http://jira.codehaus.org/browse/MPJAVADOC-66 > Project: maven-javadoc-plugin > Type: Sub-task > Reporter: geoff simpson > Fix For: 1.8 > > > can i suggest that the max jvm memory defaults are increased -- 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] Closed: (MNG-1826) deploy with url file:/// doesn't write fully pom
[ http://jira.codehaus.org/browse/MNG-1826?page=all ] Brett Porter closed MNG-1826: - Resolution: Won't Fix > deploy with url file:/// doesn't write fully pom > > > Key: MNG-1826 > URL: http://jira.codehaus.org/browse/MNG-1826 > Project: Maven 2 > Type: Bug > Components: maven-deploy-plugin > Versions: 2.0.1 > Environment: solaris and windows > Reporter: Olivier Lamy > Priority: Blocker > Attachments: pom.xml, split-tars-1.5-SNAPSHOT.pom > > > Hi, > I try deploying with an url like file:///. > I note the deployed pom is not fully write in the repository (missing content > and not correct xml) > In attached files : the pom and the generated one. > If you use the sftp deploy from my machine to the server it's ok -- 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] Reopened: (MNG-1826) deploy with url file:/// doesn't write fully pom
[ http://jira.codehaus.org/browse/MNG-1826?page=all ] Brett Porter reopened MNG-1826: --- > deploy with url file:/// doesn't write fully pom > > > Key: MNG-1826 > URL: http://jira.codehaus.org/browse/MNG-1826 > Project: Maven 2 > Type: Bug > Components: maven-deploy-plugin > Versions: 2.0.1 > Environment: solaris and windows > Reporter: Olivier Lamy > Priority: Blocker > Attachments: pom.xml, split-tars-1.5-SNAPSHOT.pom > > > Hi, > I try deploying with an url like file:///. > I note the deployed pom is not fully write in the repository (missing content > and not correct xml) > In attached files : the pom and the generated one. > If you use the sftp deploy from my machine to the server it's ok -- 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]
Re: [vote] Release Maven 2.0.1-1 critical bugfix version
I was initially confused by this, but now that I understand its a full Maven release, I'm +1. I agree with 2.0.2. Note that the branch needs to have its versions converted - it was copied directly from the previous tag so the versions are not snapshots. Perhaps the part of the release plugin that does that could be factored into something exposed by another mojo? release:changeVersion, for example. We need to fix the reporting API as well. I'm working on it. I'd like to suggest we take a little more time to test the solutions in place for these issues so that the release can stand up for the next month or so before the next scheduled release. - Brett John Casey wrote: > Hi all, > > If you've been watching this list, the users list, or JIRA, I'm sure > you've noticed that we managed to introduce some new bugs in 2.0.1. > Some of these are critical, and will block the use of this version. > > What I'd like to do is release a bugfix version, 2.0.1-1, to address > these critical issues. I've opened a new version on the Maven roadmap > in JIRA (http://jira.codehaus.org/browse/MNG) to track these. > Currently there are two, and I don't expect that number to climb much > more. > > Please note, this release is only for critical bugs. We're not going > to be fixing anything that we can limp along without for a bit longer. > > Because of the hurried nature of this vote, this email thread will > undoubtedly serve as a mechanism for determining which issues are > critical to release here; I will make sure JIRA reflects this discussion. > > Here is my +1. > > Sincerely, > > John > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1819) StringIndexOutOfBoundsException when running maven
[ http://jira.codehaus.org/browse/MNG-1819?page=all ] John Casey closed MNG-1819: --- Resolution: Fixed * If an environment variable line contains '=', then it will be parsed normally. * If it doesn't contain '=', and it is not the first envar to be parsed, this entire line will be joined to the value from the last envar, using a '\n' as the join character * Otherwise, it will ignore the line. > StringIndexOutOfBoundsException when running maven > -- > > Key: MNG-1819 > URL: http://jira.codehaus.org/browse/MNG-1819 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Environment: win xp, cygwin > Reporter: Dan Diephouse > Assignee: John Casey > Fix For: 2.0.2 > > > Just trying out 2.0.1 and I am getting this message below. any ideas? > $ mvn.bat > [WARNING] Failed to initialize environment variable resolver. Skipping > environment substitution in settings. > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -1 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 >at java.lang.String.substring(String.java:1768) >at > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:188) >at > org.codehaus.plexus.util.interpolation.EnvarBasedValueSource.(EnvarBasedValueSource.java:16) >at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:86) >at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:725) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:632) >at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) >at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) >at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) >at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Mon Dec 12 16:50:03 PST 2005 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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: (MNG-1779) properties not being replaced before being passed to plugins (specificaly the surefire plugin)
[ http://jira.codehaus.org/browse/MNG-1779?page=all ]
John Casey updated MNG-1779:
Fix Version: 2.0.3
> properties not being replaced before being passed to plugins (specificaly the
> surefire plugin)
> --
>
> Key: MNG-1779
> URL: http://jira.codehaus.org/browse/MNG-1779
> Project: Maven 2
> Type: Bug
> Components: Plugins and Lifecycle, Plugin API, maven-surefire-plugin
> Versions: 2.0.1
> Reporter: Bill Dudney
> Assignee: John Casey
> Fix For: 2.0.3
> Attachments: foo-root.tar.gz, transcript.txt
>
>
> in the attached foo-root proj run mvn package from foo-root and you will see
> that ${project.build.directory} is not substituted but
> ${project.x.build.directory} is.
> I spent a bit of time chatting with jdcasey on irc on Dec-07-2005 about this
> issue if that helps.
--
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: (MNG-1831) Assembly plugin should have the option not to repeat the build process every
[ http://jira.codehaus.org/browse/MNG-1831?page=comments#action_53500 ]
Gilles Scokart commented on MNG-1831:
-
For me it's even worse: I have an infinite loop when I bind the assembly plugin
to the package phase.
It seems to have other persons having the same problem. Some people thing it's
normal, and some said it has been fixed on svn:
See
http://www.nabble.com/forum/ViewPost.jtp?post=1419487&framed=y
http://www.nabble.com/forum/ViewPost.jtp?post=1942171&framed=y
http://www.nabble.com/forum/ViewPost.jtp?post=1869242&framed=y
> Assembly plugin should have the option not to repeat the build process every
>
>
>
> Key: MNG-1831
> URL: http://jira.codehaus.org/browse/MNG-1831
> Project: Maven 2
> Type: Improvement
> Components: maven-assembly-plugin
> Versions: 2.0.1
> Environment: Windows XP
> Reporter: Allan Ramirez
> Attachments: log.txt
>
>
> I configured my assembly plugin like this
>
> org.apache.maven.plugins
> maven-assembly-plugin
>
>
> 1
> package
>
>assembly
>
>
>src/main/descriptors/bin.xml
>${project.build.finalName}-bin
>
>
>
> 2
> package
>
> assembly
>
>
> src/main/descriptors/src.xml
> ${project.build.finalName}-src
>
>
>
> 3
> package
>
> assembly
>
>
>jar-with-dependencies
>
>
>
>
> When I command "mvn install", maven will build the whole project first then
> do the executions. But I noticed that every execution, It rebuilds the
> project upto package phase. Is this the correct behavior?
--
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: (MAVENUPLOAD-633) Please Upload Registry CDC
[ http://jira.codehaus.org/browse/MAVENUPLOAD-633?page=comments#action_53499 ] Shane Isbell commented on MAVENUPLOAD-633: -- Perhaps a simpler way for authentication is just to e-mail to the address listed within the domain registry about this upload and I will respond. > Please Upload Registry CDC > -- > > Key: MAVENUPLOAD-633 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-633 > Project: maven-upload-requests > Type: Task > Reporter: Shane Isbell > > > http://prdownloads.sourceforge.net/jvending/registry-cdc-1.0.0-bundle.jar?download > http://jvending.sourceforge.net/registry-cdc > http://jvending.sourceforge.net/registry-cdc/team-list.html > Registry-CDC provides a registry function for storing and finding data, in > particular configuration information. Please upload. -- 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: (MAVENUPLOAD-633) Please Upload Registry CDC
[ http://jira.codehaus.org/browse/MAVENUPLOAD-633?page=comments#action_53497 ] Shane Isbell commented on MAVENUPLOAD-633: -- The domain entry of my control of the domain name is at: http://reports.internic.net/cgi/whois?whois_nic=jvending.org&type=domain. If you look under the software requirements section at the top of the article http://java.sys-con.com/read/44695.htm?CFID=79377&CFTOKEN=5BC1C795-12A0-B52A-9E6811D4D9902F6A, you will see my name and the reference to http://sourceforge.net/projects/jvending. I believe this link between my name in the official domain name registry for org.jvending and my name on the article and a reference to sourceforge jvending site should complete a reasonable authentication. If not, let me know. > Please Upload Registry CDC > -- > > Key: MAVENUPLOAD-633 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-633 > Project: maven-upload-requests > Type: Task > Reporter: Shane Isbell > > > http://prdownloads.sourceforge.net/jvending/registry-cdc-1.0.0-bundle.jar?download > http://jvending.sourceforge.net/registry-cdc > http://jvending.sourceforge.net/registry-cdc/team-list.html > Registry-CDC provides a registry function for storing and finding data, in > particular configuration information. Please upload. -- 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: (MNG-1849) maven-model Extension.hashCode() throws NPE if groupId or artifactId is null
[ http://jira.codehaus.org/browse/MNG-1849?page=all ] David Hawkins updated MNG-1849: --- Attachment: MNG-1849-maven-model.patch > maven-model Extension.hashCode() throws NPE if groupId or artifactId is null > - > > Key: MNG-1849 > URL: http://jira.codehaus.org/browse/MNG-1849 > Project: Maven 2 > Type: Bug > Versions: 2.0.2 > Reporter: David Hawkins > Attachments: MNG-1849-maven-model.patch > > > org.apache.maven.model.Extension.hashCode() throws NullPointerException if > the groupId or artifactId is null. > There was null checking on version, but not on groupId or artifactId so this > patch adds it. -- 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: (MNG-1849) maven-model Extension.hashCode() throws NPE if groupId or artifactId is null
maven-model Extension.hashCode() throws NPE if groupId or artifactId is null - Key: MNG-1849 URL: http://jira.codehaus.org/browse/MNG-1849 Project: Maven 2 Type: Bug Versions: 2.0.2 Reporter: David Hawkins org.apache.maven.model.Extension.hashCode() throws NullPointerException if the groupId or artifactId is null. There was null checking on version, but not on groupId or artifactId so this patch adds it. -- 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: (MAVENUPLOAD-629) Jini version 2.1 final starter kit jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-629?page=comments#action_53494 ] Chris Sterling commented on MAVENUPLOAD-629: Thanks, Carlos. The following include zip files: http://daredskin.homedns.org/jini-starterkit-2.1-bundle.jar http://daredskin.homedns.org/jini-start-examples-2.1-bundle.jar In the future I will notifiy in my original request that these are zip files. > Jini version 2.1 final starter kit jars > --- > > Key: MAVENUPLOAD-629 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-629 > Project: maven-upload-requests > Type: Bug > Reporter: Chris Sterling > > > http://daredskin.homedns.org/checkconfigurationfile-2.1-bundle.jar > http://daredskin.homedns.org/checkser-2.1-bundle.jar > http://daredskin.homedns.org/classdep-2.1-bundle.jar > http://daredskin.homedns.org/classserver-2.1-bundle.jar > http://daredskin.homedns.org/computedigest-2.1-bundle.jar > http://daredskin.homedns.org/computehttpmdcodebase-2.1-bundle.jar > http://daredskin.homedns.org/destroy-2.1-bundle.jar > http://daredskin.homedns.org/envcheck-2.1-bundle.jar > http://daredskin.homedns.org/group-2.1-bundle.jar > http://daredskin.homedns.org/jarwrapper-2.1-bundle.jar > http://daredskin.homedns.org/jini-core-2.1-bundle.jar > http://daredskin.homedns.org/jini-ext-2.1-bundle.jar > http://daredskin.homedns.org/jini-starterkit-2.1-bundle.jar > http://daredskin.homedns.org/jini-start-examples-2.1-bundle.jar > http://daredskin.homedns.org/jsk-lib-2.1-bundle.jar > http://daredskin.homedns.org/jsk-platform-2.1-bundle.jar > http://daredskin.homedns.org/jsk-resources-2.1-bundle.jar > http://daredskin.homedns.org/sun-util-2.1-bundle.jar > http://daredskin.homedns.org/tools-2.1-bundle.jar > http://www.jini.org/ > This is as close to a team link that I could find: > http://www.jini.org/Contrib_Award/index.html > Jini version 2.1 specifications and reference implementations are licensed > under the Apache 2.0 license. I think it would be great to have the Jini base > jars in the Maven repository to support a Maven Jini Plug-in, > (http://maven-jini-plugin.jini.org/) that is going version 1.1. Thank you. -- 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-634) Upload M9 "cayenne" and "cayenne-nodeps" bundles
Upload M9 "cayenne" and "cayenne-nodeps" bundles Key: MAVENUPLOAD-634 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-634 Project: maven-upload-requests Type: Task Reporter: Andrus Adamchik This is a request to upload new Cayenne release bundles (we are already on Ibiblio - see MAVENUPLOAD-565) Two bundle URLs: http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-1.2M9-bundle.jar http://objectstyle.org/downloads/cayenne/maven-bundles/cayenne-nodeps-1.2M9-bundle.jar 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: (SCM-108) JDK 1.5 code
[ http://jira.codehaus.org/browse/SCM-108?page=all ] Wim Deblauwe updated SCM-108: - Attachment: clearcase-108.patch > JDK 1.5 code > > > Key: SCM-108 > URL: http://jira.codehaus.org/browse/SCM-108 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-clearcase > Reporter: mike perham > Attachments: clearcase-108.patch > > > [INFO] Compilation failure > D:\apache\maven-scm\maven-scm-providers\maven-scm-provider-clearcase\src\main\java\org\apache\maven\ > scm\provider\clearcase\repository\ClearCaseScmProviderRepository.java:[113,31] > cannot resolve symbol > symbol : method toURI () > location: class java.net.URL -- 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
[jira] Commented: (MNG-1819) StringIndexOutOfBoundsException when running maven
[ http://jira.codehaus.org/browse/MNG-1819?page=comments#action_53491 ] Emmanuel Venisse commented on MNG-1819: --- the workaround is to modify all environment variables with carriage return. > StringIndexOutOfBoundsException when running maven > -- > > Key: MNG-1819 > URL: http://jira.codehaus.org/browse/MNG-1819 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Environment: win xp, cygwin > Reporter: Dan Diephouse > Assignee: John Casey > Fix For: 2.0.2 > > > Just trying out 2.0.1 and I am getting this message below. any ideas? > $ mvn.bat > [WARNING] Failed to initialize environment variable resolver. Skipping > environment substitution in settings. > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -1 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 >at java.lang.String.substring(String.java:1768) >at > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:188) >at > org.codehaus.plexus.util.interpolation.EnvarBasedValueSource.(EnvarBasedValueSource.java:16) >at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:86) >at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:725) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:632) >at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) >at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) >at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) >at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Mon Dec 12 16:50:03 PST 2005 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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: (MNG-1819) StringIndexOutOfBoundsException when running maven
[ http://jira.codehaus.org/browse/MNG-1819?page=comments#action_53490 ] ruel loehr commented on MNG-1819: - Is there a workaround in the immediate timeframe? Or how can i get the fix? > StringIndexOutOfBoundsException when running maven > -- > > Key: MNG-1819 > URL: http://jira.codehaus.org/browse/MNG-1819 > Project: Maven 2 > Type: Bug > Versions: 2.0.1 > Environment: win xp, cygwin > Reporter: Dan Diephouse > Assignee: John Casey > Fix For: 2.0.2 > > > Just trying out 2.0.1 and I am getting this message below. any ideas? > $ mvn.bat > [WARNING] Failed to initialize environment variable resolver. Skipping > environment substitution in settings. > [INFO] Scanning for projects... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] String index out of range: -1 > [INFO] > > [INFO] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 >at java.lang.String.substring(String.java:1768) >at > org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:188) >at > org.codehaus.plexus.util.interpolation.EnvarBasedValueSource.(EnvarBasedValueSource.java:16) >at > org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:86) >at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:725) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:632) >at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:304) >at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274) >at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) >at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) >at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: < 1 second > [INFO] Finished at: Mon Dec 12 16:50:03 PST 2005 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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: (MNG-1848) Cannot execute "mvn clean" on plugins
Cannot execute "mvn clean" on plugins - Key: MNG-1848 URL: http://jira.codehaus.org/browse/MNG-1848 Project: Maven 2 Type: Bug Components: Reactor and workspace Versions: 2.0.1 Reporter: Grzegorz Slowikowski Priority: Minor "mvn clean" on plugins trunk throws error. Eclipse plugin uses Surefire in its pom, and in the reactor Surefire is prior to Eclipse, but "clean" does not create Surefire artifact. Workaround is to "install" Surefire first, and then "clean" all plugins ;-) Eclipse plugin pom: ... maven-surefire-plugin **/Abstract*TestCase.java **/EclipsePluginMasterProjectTest.java ... Execution log: ... [INFO] [INFO] Building Maven Eclipse Plugin [INFO]task-segment: [clean] [INFO] [DEBUG] Skipping disabled repository central [DEBUG] maven-surefire-plugin: using locally installed snapshot [DEBUG] Trying repository snapshots Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefire-plugin-2.1.2-SNAPSHOT.jar [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) [DEBUG] Skipping disabled repository central [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) at org.apache.maven.plugin.DefaultPluginManager.veri
[jira] Commented: (MAVENUPLOAD-633) Please Upload Registry CDC
[ http://jira.codehaus.org/browse/MAVENUPLOAD-633?page=comments#action_53487 ] Carlos Sanchez commented on MAVENUPLOAD-633: You need proof of controlling the jvending.org domain to upload to that groupid Next time use direct download url as bundle url http://surfnet.dl.sourceforge.net/sourceforge/jvending/registry-cdc-1.0.0-bundle.jar > Please Upload Registry CDC > -- > > Key: MAVENUPLOAD-633 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-633 > Project: maven-upload-requests > Type: Task > Reporter: Shane Isbell > > > http://prdownloads.sourceforge.net/jvending/registry-cdc-1.0.0-bundle.jar?download > http://jvending.sourceforge.net/registry-cdc > http://jvending.sourceforge.net/registry-cdc/team-list.html > Registry-CDC provides a registry function for storing and finding data, in > particular configuration information. Please upload. -- 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] Closed: (MAVENUPLOAD-632) Upload antlr-2.7.6-rc1 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-632?page=all ] Carlos Sanchez closed MAVENUPLOAD-632: -- Assign To: Carlos Sanchez Resolution: Fixed Uploaded as 2.7.6rc1 (as they call it) Fixed hibernate pom > Upload antlr-2.7.6-rc1 to ibiblio > - > > Key: MAVENUPLOAD-632 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-632 > Project: maven-upload-requests > Type: Task > Reporter: Matt Raible > Assignee: Carlos Sanchez > > > Hibernate 3.1 depends on antlr 2.7.6 RC1 -- 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] Closed: (MAVENUPLOAD-631) Upload cglib-2.1.3 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-631?page=all ] Carlos Sanchez closed MAVENUPLOAD-631: -- Assign To: Carlos Sanchez Resolution: Won't Fix Already there as 2.1_3 (that's how they call it) I've fixed the hibernate pom > Upload cglib-2.1.3 to ibiblio > - > > Key: MAVENUPLOAD-631 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-631 > Project: maven-upload-requests > Type: Task > Reporter: Matt Raible > Assignee: Carlos Sanchez > > > Hibernate 3.1 depends on cglib 2.1.3 -- 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] Closed: (MAVENUPLOAD-630) Upload hibernate-3.1 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-630?page=all ] Carlos Sanchez closed MAVENUPLOAD-630: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload hibernate-3.1 to ibiblio > --- > > Key: MAVENUPLOAD-630 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-630 > Project: maven-upload-requests > Type: Task > Reporter: Matt Raible > Assignee: Carlos Sanchez > > > Please upload the latest release of Hibernate to ibiblio. -- 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: (MAVENUPLOAD-629) Jini version 2.1 final starter kit jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-629?page=comments#action_53484 ] Carlos Sanchez commented on MAVENUPLOAD-629: please point out which of them are zips so I can upload them manually > Jini version 2.1 final starter kit jars > --- > > Key: MAVENUPLOAD-629 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-629 > Project: maven-upload-requests > Type: Bug > Reporter: Chris Sterling > > > http://daredskin.homedns.org/checkconfigurationfile-2.1-bundle.jar > http://daredskin.homedns.org/checkser-2.1-bundle.jar > http://daredskin.homedns.org/classdep-2.1-bundle.jar > http://daredskin.homedns.org/classserver-2.1-bundle.jar > http://daredskin.homedns.org/computedigest-2.1-bundle.jar > http://daredskin.homedns.org/computehttpmdcodebase-2.1-bundle.jar > http://daredskin.homedns.org/destroy-2.1-bundle.jar > http://daredskin.homedns.org/envcheck-2.1-bundle.jar > http://daredskin.homedns.org/group-2.1-bundle.jar > http://daredskin.homedns.org/jarwrapper-2.1-bundle.jar > http://daredskin.homedns.org/jini-core-2.1-bundle.jar > http://daredskin.homedns.org/jini-ext-2.1-bundle.jar > http://daredskin.homedns.org/jini-starterkit-2.1-bundle.jar > http://daredskin.homedns.org/jini-start-examples-2.1-bundle.jar > http://daredskin.homedns.org/jsk-lib-2.1-bundle.jar > http://daredskin.homedns.org/jsk-platform-2.1-bundle.jar > http://daredskin.homedns.org/jsk-resources-2.1-bundle.jar > http://daredskin.homedns.org/sun-util-2.1-bundle.jar > http://daredskin.homedns.org/tools-2.1-bundle.jar > http://www.jini.org/ > This is as close to a team link that I could find: > http://www.jini.org/Contrib_Award/index.html > Jini version 2.1 specifications and reference implementations are licensed > under the Apache 2.0 license. I think it would be great to have the Jini base > jars in the Maven repository to support a Maven Jini Plug-in, > (http://maven-jini-plugin.jini.org/) that is going version 1.1. Thank you. -- 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: (SCM-116) scm:update doesn't iterate through multi-projects
[ http://jira.codehaus.org/browse/SCM-116?page=comments#action_53483 ] David Boden commented on SCM-116: - Makes sense. However, I now understand that you are supposed to be able to have parent pom files that are not in the root directory of the multiproject. You're supposed to be able to have the aggregator pom.xml in a subdirectory and then refer to: ../module1 ../module2 If it is Maven 2's aim to support this scenario then it is desirable for the SCM plugin to cope with it. > scm:update doesn't iterate through multi-projects > - > > Key: SCM-116 > URL: http://jira.codehaus.org/browse/SCM-116 > Project: Maven SCM > Type: Bug > Versions: 1.0-beta-2 > Reporter: David Boden > > > scm:update doesn't iterate through projects > > C:\dev\CDSSS>mvn scm:update > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] SalesStation ss_base_shared > [INFO] SalesStation cds_ss_shared > [INFO] SalesStation ss_offering_shared > [INFO] SalesStation ss_base_applet > [INFO] SalesStation sales_station_lib > [INFO] SalesStation ss_offering_lib > [INFO] SalesStation sales_station_applet > [INFO] SalesStation cds_ss_applet > [INFO] SalesStation cds_ss_lib > [INFO] SalesStation SS webapp > [INFO] SalesStation FET_S webapp (contains images) > [INFO] SalesStation CDSSS webapp > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > [INFO] Building SalesStation CDSSS webapp > [INFO]task-segment: [scm:update] (aggregator-style) > [INFO] > > [INFO] [scm:update] > [INFO] Executing: cvs -f -q update -d > [INFO] Working directory: C:\dev\CDSSS > [WARNING] Unknown status: '? '. > [WARNING] Unknown status: 'M '. > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 5 seconds > [INFO] Finished at: Thu Dec 15 10:38:24 GMT 2005 > [INFO] Final Memory: 3M/7M > [INFO] > > C:\dev\CDSSS> > > Any reason why it doesn't iterate? I'm using Maven 2.0.1 and SCM version > 1.0-beta-2. 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
[jira] Created: (MNG-1847) Incorrect configuration merging when using multiple executions of antrun
Incorrect configuration merging when using multiple executions of antrun
Key: MNG-1847
URL: http://jira.codehaus.org/browse/MNG-1847
Project: Maven 2
Type: Bug
Versions: 2.0, 2.0.1
Environment: windows xp, maven 2.0
Reporter: Michal Stochmialek
Attachments: testcase.zip
I've encovered strange behaviour of maven while merging configuration. I've
prepared two test cases.
The first one shows how executions from different phases and profiles are
incorrectly merged. One antrun execution is in main build element in package
phase. Second antrun execution is in 'foo' profile in validation phase. When
running mvn using this profile with default goal (validate), maven is merging
two antrun executions (but not completely).
4.0.0
testcase
test2
1.0
maven-antrun-plugin
package
main build
run
foo
validate
maven-antrun-plugin
validate
Foo profile
run
C:\test2>mvn -Pfoo
[INFO] Scanning for projects...
[INFO]
[INFO] Building Unnamed - testcase:test2:jar:1.0
[INFO]task-segment: [validate]
[INFO]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Foo profile
[mkdir] Created dir: P:\maven\testcase\test2\fooo
[delete] Deleting directory P:\maven\testcase\test2\fooo
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Dec 15 15:43:23 CET 2005
[INFO] Final Memory: 2M/4M
[INFO]
The second testcase shows how different executions of antrun are incorrectly
merged. There are two different antrun executions. One in compile phase and one
in package phase. They should 'echo' different messages, but they DON'T.
4.0.0
testcase
test1
test1
1.0
package
maven-antrun-plugin
compile
main build / compile phase
run
maven-antrun-plugin
package
main build / package phase
run
c:\test1>mvn
[INFO] Scanning for projects...
[INFO]
[INFO] Building test1
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] main build / compile phase
[INFO] Executed tasks
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: P:\maven\testcase\test1\target\test1-1.0.jar
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] main build / compile phase
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Dec 15 15:36:03 CET 2005
[INFO] Final Memory: 3M/7M
[INFO]
I've attached both poms.
--
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: (SCM-116) scm:update doesn't iterate through multi-projects
[ http://jira.codehaus.org/browse/SCM-116?page=comments#action_53482 ] mike perham commented on SCM-116: - I think it is assumed that when you update the root of a multi-project, the SCM updates everything underneath that directory, including all subprojects. > scm:update doesn't iterate through multi-projects > - > > Key: SCM-116 > URL: http://jira.codehaus.org/browse/SCM-116 > Project: Maven SCM > Type: Bug > Versions: 1.0-beta-2 > Reporter: David Boden > > > scm:update doesn't iterate through projects > > C:\dev\CDSSS>mvn scm:update > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] SalesStation ss_base_shared > [INFO] SalesStation cds_ss_shared > [INFO] SalesStation ss_offering_shared > [INFO] SalesStation ss_base_applet > [INFO] SalesStation sales_station_lib > [INFO] SalesStation ss_offering_lib > [INFO] SalesStation sales_station_applet > [INFO] SalesStation cds_ss_applet > [INFO] SalesStation cds_ss_lib > [INFO] SalesStation SS webapp > [INFO] SalesStation FET_S webapp (contains images) > [INFO] SalesStation CDSSS webapp > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > [INFO] Building SalesStation CDSSS webapp > [INFO]task-segment: [scm:update] (aggregator-style) > [INFO] > > [INFO] [scm:update] > [INFO] Executing: cvs -f -q update -d > [INFO] Working directory: C:\dev\CDSSS > [WARNING] Unknown status: '? '. > [WARNING] Unknown status: 'M '. > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 5 seconds > [INFO] Finished at: Thu Dec 15 10:38:24 GMT 2005 > [INFO] Final Memory: 3M/7M > [INFO] > > C:\dev\CDSSS> > > Any reason why it doesn't iterate? I'm using Maven 2.0.1 and SCM version > 1.0-beta-2. 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
[jira] Updated: (MEV-259) commons-net 1.4.1 invalid pom
[ http://jira.codehaus.org/browse/MEV-259?page=all ] Tomislav Stojcevich updated MEV-259: Attachment: commons-net-1.4.1.pom > commons-net 1.4.1 invalid pom > - > > Key: MEV-259 > URL: http://jira.codehaus.org/browse/MEV-259 > Project: Maven Evangelism > Type: Bug > Reporter: Tomislav Stojcevich > Attachments: commons-net-1.4.1.pom > > > The pom is the old maven 1 pom. > 1.4.1 was a minor release. I diffed the maven 1 poms (1.4.0 to 1.4.1) and it > looks like a version number change is all that is required. -- 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: (MEV-259) commons-net 1.4.1 invalid pom
commons-net 1.4.1 invalid pom - Key: MEV-259 URL: http://jira.codehaus.org/browse/MEV-259 Project: Maven Evangelism Type: Bug Reporter: Tomislav Stojcevich The pom is the old maven 1 pom. 1.4.1 was a minor release. I diffed the maven 1 poms (1.4.0 to 1.4.1) and it looks like a version number change is all that is required. -- 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: (MNG-1576) PMD does not work on dutch locale
[ http://jira.codehaus.org/browse/MNG-1576?page=comments#action_53477 ] Jose Gonzalez Gomez commented on MNG-1576: -- Same for es_ES > PMD does not work on dutch locale > - > > Key: MNG-1576 > URL: http://jira.codehaus.org/browse/MNG-1576 > Project: Maven 2 > Type: Bug > Components: maven-pmd-plugin > Reporter: Wim Deblauwe > > > I get the following error when running mvn site with pmd report enabled: > [ERROR] FATAL ERROR > [INFO] > > [INFO] Can't find bundle for base name pmd-report, locale nl_NL > [INFO] > > [INFO] Trace > java.util.MissingResourceException: Can't find bundle for base name > pmd-report, locale nl_NL > at > java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:837) > at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:806) > at java.util.ResourceBundle.getBundle(ResourceBundle.java:700) > at org.apache.maven.plugin.pmd.PmdReport.getBundle(PmdReport.java:232) > at org.apache.maven.plugin.pmd.PmdReport.getName(PmdReport.java:82) > at > org.apache.maven.plugins.site.ReportComparator.compare(ReportComparator.java:40) > at java.util.Arrays.mergeSort(Arrays.java:1284) > at java.util.Arrays.sort(Arrays.java:1223) > at java.util.Collections.sort(Collections.java:159) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:240) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: 10 seconds > [INFO] Finished at: Tue Nov 15 14:42:35 CET 2005 > [INFO] Final Memory: 9M/16M > [INFO] > > regards, > Wim -- 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]
Re: [vote] Release Maven 2.0.1-1 critical bugfix version
On Thu, 15 Dec 2005, Jason van Zyl wrote: +1! > John Casey wrote: > > I'm not too interested in which version number we use; I only suggested > > this notation since it's definitely a lot smaller than what we did for > > 2.0.1, and what we've got slated for 2.0.2...that, and it's meant to > > modify the 2.0.1 release so it'll work. > > > > 2.0.2 is fine with me. I can push the other stuff off to 2.0.3. > > > > What about the vote? > > +1 > > > -j > > > > Jason van Zyl wrote: > > > >> John Casey wrote: > >> > >>> Hi all, > >>> > >>> If you've been watching this list, the users list, or JIRA, I'm sure > >>> you've noticed that we managed to introduce some new bugs in 2.0.1. > >>> Some of these are critical, and will block the use of this version. > >>> > >>> What I'd like to do is release a bugfix version, 2.0.1-1, to address > >>> these critical issues. I've opened a new version on the Maven roadmap > >>> in JIRA (http://jira.codehaus.org/browse/MNG) to track these. > >>> Currently there are two, and I don't expect that number to climb much > >>> more. > >> > >> > >> I think the version should be 2.0.2. It is a patch release > >> effectively. I know this means pushing out all the JIRA issues to a > >> 2.0.3. I just did this with surefire where a bug slipped in and I > >> think major.minor.patch is more consistent. > >> > >>> Please note, this release is only for critical bugs. We're not going > >>> to be fixing anything that we can limp along without for a bit longer. > >>> > >>> Because of the hurried nature of this vote, this email thread will > >>> undoubtedly serve as a mechanism for determining which issues are > >>> critical to release here; I will make sure JIRA reflects this > >>> discussion. > >>> > >>> Here is my +1. > >>> > >>> Sincerely, > >>> > >>> John > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > > jvz. > > Jason van Zyl > jason at maven.org > http://maven.apache.org > > First, the taking in of scattered particulars under one Idea, > so that everyone understands what is being talked about ... Second, > the separation of the Idea into parts, by dividing it at the joints, > as nature directs, not breaking any limb in half as a bad carver might. > >-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1826) deploy with url file:/// doesn't write fully pom
[ http://jira.codehaus.org/browse/MNG-1826?page=all ] Olivier Lamy closed MNG-1826: - Resolution: Fixed bad plexus-utils in local repository. > deploy with url file:/// doesn't write fully pom > > > Key: MNG-1826 > URL: http://jira.codehaus.org/browse/MNG-1826 > Project: Maven 2 > Type: Bug > Components: maven-deploy-plugin > Versions: 2.0.1 > Environment: solaris and windows > Reporter: Olivier Lamy > Priority: Blocker > Attachments: pom.xml, split-tars-1.5-SNAPSHOT.pom > > > Hi, > I try deploying with an url like file:///. > I note the deployed pom is not fully write in the repository (missing content > and not correct xml) > In attached files : the pom and the generated one. > If you use the sftp deploy from my machine to the server it's ok -- 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: (MNG-1846) Use of 'severity' attribute in module configuration file causes UnsupportedOperationException
Use of 'severity' attribute in module configuration file causes UnsupportedOperationException - Key: MNG-1846 URL: http://jira.codehaus.org/browse/MNG-1846 Project: Maven 2 Type: Bug Components: maven-checkstyle-plugin Versions: 2.0.2, 2.0 Environment: Windows XP, J2SDK 1.4.2_10, maven-checkstyle-plugin 2.0-beta-2-SNAPSHOT, Maven 2.0.2-SNAPSHOT Reporter: Nick Giles Attachments: trace.txt When I provide the Checkstyle plugin with a customised config file, it causes it to crash unpleasantly when generating the report. It appears that this is due to calling the 'remove' method on Arrays$ArrayList, which doesn't implement the method. The call is actually removing the 'severity' property from the list of columns before going on to process the rest. Wrapping the list in an actual ArrayList (java.util.ArrayList) solves the problem. To replicate, add your-rules.xml to the plugin configuration, and ensure that at least two modules in your-rules.xml have the severity property set, something like: http://www.puppycrawl.com/dtds/configuration_1_2.dtd";> -- 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] Closed: (SCM-110) Perforce should force sync
[ http://jira.codehaus.org/browse/SCM-110?page=all ] Emmanuel Venisse closed SCM-110: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. > Perforce should force sync > -- > > Key: SCM-110 > URL: http://jira.codehaus.org/browse/SCM-110 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Reporter: mike perham > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: force2.txt > > > It's not pretty but it's the only way to get sync to work when files could be > deleted from the filesystem (e.g. mvn clean). -- 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
[jira] Commented: (MNG-1835) Ability to specify more than 1 check configuration file and file sets for each of these configurations
[ http://jira.codehaus.org/browse/MNG-1835?page=comments#action_53473 ] Fabrice BELLINGARD commented on MNG-1835: - Well, I don't want to have multiple reports, but only one. So I don't know if that would be possible, but as you said, there could be multiple Checkstyle runs, one for each check configuration file associated to its File set. And the results would be gathered into one single report. > Ability to specify more than 1 check configuration file and file sets for > each of these configurations > -- > > Key: MNG-1835 > URL: http://jira.codehaus.org/browse/MNG-1835 > Project: Maven 2 > Type: Improvement > Components: maven-checkstyle-plugin > Reporter: Fabrice BELLINGARD > > > I'm using Eclipse Checkstyle Plug-in, and there's a functionnality I enjoy a > lot: the ability to specify as many check configuration files as I want for a > projet, and to tell which file sets those configurations should be run on. > And as I use this functionnality extensively, I'd love to have it also in the > Maven Checkstyle Plug-in :o) > To get a look at what the Eclipse plugin does: > http://eclipse-cs.sourceforge.net/advanced_file_sets.html -- 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]
