[jira] Created: (MNG-2255) Use a external XML Pull parser instead of plexus one
Use a external XML Pull parser instead of plexus one Key: MNG-2255 URL: http://jira.codehaus.org/browse/MNG-2255 Project: Maven 2 Type: Improvement Components: POM Versions: 2.0.4 Reporter: Carlos Sanchez To avoid maintaining the plexus XMLPullParser we should move to a standard implementation like StaX As mentioned in DOXIA-60: There's a performance white paper http://java.sun.com/performance/reference/whitepapers/StAX-1_0.pdf The best implementation seems to be http://woodstox.codehaus.org/ Another nice set of utilities at http://wiki.java.net/bin/view/Javawsxml/StaxUtilsProject The indentator could be used instead of the PrettyPrintXMLWriter -- 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-2256) Misleading documentation regarding configuration of java.utils.Properties
Misleading documentation regarding configuration of java.utils.Properties
-
Key: MNG-2256
URL: http://jira.codehaus.org/browse/MNG-2256
Project: Maven 2
Type: Bug
Components: Documentation: General
Reporter: James Talmage
Location:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
Snippet:
{quote}
Properties
This category covers any map which implements java.util.Properties. These
parameters are configured by including XML tags in the form value in
the parameter configuration.
{quote}
This lead me to believe I could set properties like this:
{quote}
propertyValue
.
{quote}
Instead I've found I need to do it like this:
{quote}
propertyName
propertyValue
.
{quote}
--
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-866) UISpec4J is an Open Source functional and/or unit testing library for Swing-based Java applications, built on top of the JUnit test harness.
UISpec4J is an Open Source functional and/or unit testing library for Swing-based Java applications, built on top of the JUnit test harness. Key: MAVENUPLOAD-866 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-866 Project: maven-upload-requests Type: Task Reporter: Sylvain Rousseau UISpec4J: Java GUI testing made simple! If you are writing a Swing application, you will appreciate UISpec4J above all for its simplicity: UISpec4J's APIs are designed to hide as much as possible the complexity of Swing, resulting in easy to write and easy to read test scripts. This is especially true when comparing UISpec4J tests with those produced using Swing or low-level, event-based testing libraries. -- 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-867) slf4j 1.0 sources
slf4j 1.0 sources - Key: MAVENUPLOAD-867 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-867 Project: maven-upload-requests Type: Task Reporter: fabrizio giustina The following bundles contain source jars for the slf4j 1.0 release. Binary jars are the same actually stored in the ibiblio repo, poms are the same + the addition of project url and license name/url that were missing in the original ones http://magnolia.sourceforge.net/bundles/slf4j-jcl-1.0-bundle.jar http://magnolia.sourceforge.net/bundles/slf4j-jdk14-1.0-bundle.jar http://magnolia.sourceforge.net/bundles/slf4j-log4j12-1.0-bundle.jar http://magnolia.sourceforge.net/bundles/slf4j-log4j13-1.0-bundle.jar http://magnolia.sourceforge.net/bundles/slf4j-nop-1.0-bundle.jar http://magnolia.sourceforge.net/bundles/slf4j-simple-1.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEPLOY-31) deploy-file: Custom description in generated pom
deploy-file: Custom description in generated pom Key: MDEPLOY-31 URL: http://jira.codehaus.org/browse/MDEPLOY-31 Project: Maven 2.x Deploy Plugin Type: Improvement Reporter: Fabian Bauschulte It would be very helpful during "deploy-file" to pass a custom description (in the command line) to the generated pom. If an artefact has no dependencies there is normally no need to write a pom except for the description. -- 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: (MDEPLOY-31) deploy-file: Custom description in generated pom
[ http://jira.codehaus.org/browse/MDEPLOY-31?page=all ] Fabian Bauschulte updated MDEPLOY-31: - Attachment: MDEPLOY-31-maven-deploy-plugin.patch > deploy-file: Custom description in generated pom > > > Key: MDEPLOY-31 > URL: http://jira.codehaus.org/browse/MDEPLOY-31 > Project: Maven 2.x Deploy Plugin > Type: Improvement > Reporter: Fabian Bauschulte > Attachments: MDEPLOY-31-maven-deploy-plugin.patch > > > It would be very helpful during "deploy-file" to pass a custom description > (in the command line) to the generated pom. If an artefact has no > dependencies there is normally no need to write a pom except for the > description. -- 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: (MPECLIPSE-117) Add the ability to specify source exclusions
Add the ability to specify source exclusions Key: MPECLIPSE-117 URL: http://jira.codehaus.org/browse/MPECLIPSE-117 Project: maven-eclipse-plugin Type: New Feature Reporter: James Mitchell Priority: Minor Attachments: srcExclusions-patch.zip When source files contain scm information (**/.svn/** or **/CVS/**), which is pretty much a given, there's currently no way to specify that those directories be excluded except through the GUI. This isn't so much of a problem except that the next time a change is needed and this plugin is ran, it will overwrite this exclusion and will force me to exclude it, by hand, again. The above case is the driving reason why I decided to get involved and help out. So, I have written everything (I think) that is needed for this enhancement including, adding to the javadoc, creating a new test that verifies this enhancement, and fully testing this with my own projects (many of them @ Struts). If there is anything else I need to do as far as site documentation, please tell me where it is and I'll add it. This is my first patch to Maven. If this sucks, please don't ignore it, just say 'it sucks, no thanks" and I'll go about working on something else. Thanks so much for your attention. -- James Mitchell -- 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: (MAVENUPLOAD-867) slf4j 1.0 sources
[ http://jira.codehaus.org/browse/MAVENUPLOAD-867?page=comments#action_64385 ] Carlos Sanchez commented on MAVENUPLOAD-867: as it's modification, can you put them in a zip as they'd be in the repo? > slf4j 1.0 sources > - > > Key: MAVENUPLOAD-867 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-867 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > > > The following bundles contain source jars for the slf4j 1.0 release. > Binary jars are the same actually stored in the ibiblio repo, poms are the > same + the addition of project url and license name/url that were missing in > the original ones > http://magnolia.sourceforge.net/bundles/slf4j-jcl-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-jdk14-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-log4j12-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-log4j13-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-nop-1.0-bundle.jar > http://magnolia.sourceforge.net/bundles/slf4j-simple-1.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist
M2 Plugin Breaks Content Assist --- Key: MNGECLIPSE-113 URL: http://jira.codehaus.org/browse/MNGECLIPSE-113 Project: Maven 2.x Extension for Eclipse Type: Bug Versions: 0.0.5 Environment: Fedora Core 4 JDK 1.5.0_06 Eclipse3.2 Reporter: Todd Orr Assigned to: Eugene Kuleshov Downloaded fresh eclipse. Set up existing mvn project in eclipse. Ensured that compiler was at 5.0 and jre was jdk5 in eclipse. Downloaded maven plugin 0.05. Enabled plugin on project (dependencies resolved). However, when ever I try to use content assist I get the error "Content Assist" did not complete normally. Please see the log for more information. Reason: java.lang.NullPointerException If I disable the m2 plugin, I can then use content assist without incident. Below are the log entries for attempting to use content assist only: !ENTRY org.eclipse.jdt.ui 4 2 2006-04-29 11:37:23.787 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jdt.ui". !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(org.eclipse.jdt.internal.core.OpenableElementInfo, java.util.Map) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStructure(org.eclipse.jdt.internal.core.OpenableElementInfo, org.eclipse.core.runtime.IProgressMonitor, java.util.Map, org.eclipse.core.resources.IResource) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.Openable.generateInfos(java.lang.Object, java.util.HashMap, org.eclipse.core.runtime.IProgressMonitor) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(java.lang.Object, org.eclipse.core.runtime.IProgressMonitor) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(org.eclipse.core.runtime.IProgressMonitor) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo() (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaElement.getChildren() (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(org.eclipse.jdt.internal.core.JavaProject) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(org.eclipse.jdt.internal.core.JavaProject, org.eclipse.jdt.core.ICompilationUnit[]) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(org.eclipse.jdt.core.ICompilationUnit[]) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, org.eclipse.jdt.core.ICompilationUnit[]) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, org.eclipse.jdt.core.WorkingCopyOwner) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.core.CancelableNameEnvironment.CancelableNameEnvironment(org.eclipse.jdt.internal.core.JavaProject, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.jdt.core.runtime.IProgressMonitor) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(org.eclipse.jdt.internal.compiler.env.ICompilationUnit, org.eclipse.jdt.core.IJavaProject, org.eclipse.jdt.core.dom.NodeSearcher, java.util.Map, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor) (Unknown Source) at org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(org.eclipse.core.runtime.IProgressMonitor) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.core.dom.ASTParser.createAST(org.eclipse.core.runtime.IProgressMonitor) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider$1.run() (Unknown Source) at org.eclipse.core.internal.runtime.InternalPlatform.run(org.eclipse.core.runtime.ISafeRunnable) (/usr/lib/gcj/eclipse/org.eclipse.core.runtime_3.1.1.jar.so) at org.eclipse.core.runtime.Platform.run(org.eclipse.core.runtime.ISafeRunnable) (Unknown Source) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.createAST(org.eclipse.jdt.core.IJavaElement, org.eclipse.core.runtime.IProgressMonitor) (Unknown Source) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST(org.eclipse.jdt.core.IJavaElement, org.eclipse.jdt.internal.ui.javaeditor.ASTProvider$WAIT_FLAG, org.eclipse.core.runtime.IProgressMonitor) (Unknown Source) a
[jira] Commented: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist
[ http://jira.codehaus.org/browse/MNGECLIPSE-113?page=comments#action_64386 ] Eugene Kuleshov commented on MNGECLIPSE-113: I doubt this is a plugin issue, especially because there is no plugin classes in your stack trace. Loking at the stack trace it seems you are using Eclipse compiled into something native with gcj. We don't have such configuration around, so unfortunately you are on your own here. I haven't heard complains about plugin running on Eclipse 3.1, but you can ask in user mail list just in case. What I can suggest is to try to get some plain PDE project (PDE is also using custom class patch container) and see if content assist is working there. Another plugin to try is Necessitas (container for ivy dependencies). If those two does not work, you'll have to fill an issue to whoever build that gcj'ed Eclipse. But if they do work, then you'll have to debug trough our plugin using your own configuration. Actually put a breakpoint in JarPackageFragmentRoot and see what is going on around. > M2 Plugin Breaks Content Assist > --- > > Key: MNGECLIPSE-113 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-113 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.5 > Environment: Fedora Core 4 > JDK 1.5.0_06 > Eclipse3.2 > Reporter: Todd Orr > Assignee: Eugene Kuleshov > > > Downloaded fresh eclipse. Set up existing mvn project in eclipse. Ensured > that compiler was at 5.0 and jre was jdk5 in eclipse. Downloaded maven > plugin 0.05. Enabled plugin on project (dependencies resolved). However, when > ever I try to use content assist I get the error > "Content Assist" did not complete normally. Please see the log for more > information. > Reason: > java.lang.NullPointerException > If I disable the m2 plugin, I can then use content assist without incident. > Below are the log entries for attempting to use content assist only: > !ENTRY org.eclipse.jdt.ui 4 2 2006-04-29 11:37:23.787 > !MESSAGE Problems occurred when invoking code from plug-in: > "org.eclipse.jdt.ui". > !STACK 0 > java.lang.NullPointerException >at > org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(org.eclipse.jdt.internal.core.OpenableElementInfo, > java.util.Map) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStructure(org.eclipse.jdt.internal.core.OpenableElementInfo, > org.eclipse.core.runtime.IProgressMonitor, java.util.Map, > org.eclipse.core.resources.IResource) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.Openable.generateInfos(java.lang.Object, > java.util.HashMap, org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(java.lang.Object, > org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaElement.getElementInfo(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.JavaElement.getElementInfo() > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.JavaElement.getChildren() > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(org.eclipse.jdt.internal.core.JavaProject) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProject.newNameLookup(org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.WorkingCopyOwner) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.CancelableNameEnvironment.CancelableNameEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.WorkingCopyOwner, > org.eclipse.jdt.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(org.eclipse.jdt.internal.compiler.env.ICompilationUnit, > org.eclipse.jdt.core.I
[jira] Commented: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist
[ http://jira.codehaus.org/browse/MNGECLIPSE-113?page=comments#action_64388 ] Todd Orr commented on MNGECLIPSE-113: - This has been cleared up by changing the vm that eclipse was using in its configuration. The default install of fedora creates a link in /usr/bin that points to gcj. I changed that to point to the new jdk and all is well. Thanks. > M2 Plugin Breaks Content Assist > --- > > Key: MNGECLIPSE-113 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-113 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.5 > Environment: Fedora Core 4 > JDK 1.5.0_06 > Eclipse3.2 > Reporter: Todd Orr > Assignee: Eugene Kuleshov > > > Downloaded fresh eclipse. Set up existing mvn project in eclipse. Ensured > that compiler was at 5.0 and jre was jdk5 in eclipse. Downloaded maven > plugin 0.05. Enabled plugin on project (dependencies resolved). However, when > ever I try to use content assist I get the error > "Content Assist" did not complete normally. Please see the log for more > information. > Reason: > java.lang.NullPointerException > If I disable the m2 plugin, I can then use content assist without incident. > Below are the log entries for attempting to use content assist only: > !ENTRY org.eclipse.jdt.ui 4 2 2006-04-29 11:37:23.787 > !MESSAGE Problems occurred when invoking code from plug-in: > "org.eclipse.jdt.ui". > !STACK 0 > java.lang.NullPointerException >at > org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(org.eclipse.jdt.internal.core.OpenableElementInfo, > java.util.Map) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStructure(org.eclipse.jdt.internal.core.OpenableElementInfo, > org.eclipse.core.runtime.IProgressMonitor, java.util.Map, > org.eclipse.core.resources.IResource) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.Openable.generateInfos(java.lang.Object, > java.util.HashMap, org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(java.lang.Object, > org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaElement.getElementInfo(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.JavaElement.getElementInfo() > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.JavaElement.getChildren() > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(org.eclipse.jdt.internal.core.JavaProject) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProject.newNameLookup(org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.WorkingCopyOwner) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.CancelableNameEnvironment.CancelableNameEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.WorkingCopyOwner, > org.eclipse.jdt.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(org.eclipse.jdt.internal.compiler.env.ICompilationUnit, > org.eclipse.jdt.core.IJavaProject, org.eclipse.jdt.core.dom.NodeSearcher, > java.util.Map, org.eclipse.jdt.core.WorkingCopyOwner, > org.eclipse.core.runtime.IProgressMonitor) (Unknown Source) >at > org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.core.dom.ASTParser.createAST(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider$1.run() (Unknown > Source) >at > org.eclipse.core.internal.runtime.InternalPlatform.run(org.eclipse.core.runtime.ISafeRunnab
[jira] Closed: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist
[ http://jira.codehaus.org/browse/MNGECLIPSE-113?page=all ] Todd Orr closed MNGECLIPSE-113: --- Resolution: Won't Fix > M2 Plugin Breaks Content Assist > --- > > Key: MNGECLIPSE-113 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-113 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.5 > Environment: Fedora Core 4 > JDK 1.5.0_06 > Eclipse3.2 > Reporter: Todd Orr > Assignee: Eugene Kuleshov > > > Downloaded fresh eclipse. Set up existing mvn project in eclipse. Ensured > that compiler was at 5.0 and jre was jdk5 in eclipse. Downloaded maven > plugin 0.05. Enabled plugin on project (dependencies resolved). However, when > ever I try to use content assist I get the error > "Content Assist" did not complete normally. Please see the log for more > information. > Reason: > java.lang.NullPointerException > If I disable the m2 plugin, I can then use content assist without incident. > Below are the log entries for attempting to use content assist only: > !ENTRY org.eclipse.jdt.ui 4 2 2006-04-29 11:37:23.787 > !MESSAGE Problems occurred when invoking code from plug-in: > "org.eclipse.jdt.ui". > !STACK 0 > java.lang.NullPointerException >at > org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(org.eclipse.jdt.internal.core.OpenableElementInfo, > java.util.Map) (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStructure(org.eclipse.jdt.internal.core.OpenableElementInfo, > org.eclipse.core.runtime.IProgressMonitor, java.util.Map, > org.eclipse.core.resources.IResource) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.Openable.generateInfos(java.lang.Object, > java.util.HashMap, org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(java.lang.Object, > org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaElement.getElementInfo(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.JavaElement.getElementInfo() > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.core.JavaElement.getChildren() > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(org.eclipse.jdt.internal.core.JavaProject) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.JavaProject.newNameLookup(org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.ICompilationUnit[]) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.SearchableEnvironment.SearchableEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.WorkingCopyOwner) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.internal.core.CancelableNameEnvironment.CancelableNameEnvironment(org.eclipse.jdt.internal.core.JavaProject, > org.eclipse.jdt.core.WorkingCopyOwner, > org.eclipse.jdt.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(org.eclipse.jdt.internal.compiler.env.ICompilationUnit, > org.eclipse.jdt.core.IJavaProject, org.eclipse.jdt.core.dom.NodeSearcher, > java.util.Map, org.eclipse.jdt.core.WorkingCopyOwner, > org.eclipse.core.runtime.IProgressMonitor) (Unknown Source) >at > org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at > org.eclipse.jdt.core.dom.ASTParser.createAST(org.eclipse.core.runtime.IProgressMonitor) > (/usr/lib/gcj/eclipse/org.eclipse.jdt.core_3.1.1.jar.so) >at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider$1.run() (Unknown > Source) >at > org.eclipse.core.internal.runtime.InternalPlatform.run(org.eclipse.core.runtime.ISafeRunnable) > (/usr/lib/gcj/eclipse/org.eclipse.core.runtime_3.1.1.jar.so) >at > org.eclipse.core.runtime.Platform.run(org.eclipse.core.runtime.ISafeRunnable) > (Unknown Source) >at > org.eclipse.jdt.internal.ui.javaeditor.ASTPr
[jira] Commented: (MJAR-39) Maven Sets Manifest Attribute Values to Multi-Line Strings
[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_64389 ] Steven Coco commented on MJAR-39: - This issue is related to MJAR-39 in that since it sets the Specification-Title element by default to the POM's element, it easily can create an invalid Manifest. > Maven Sets Manifest Attribute Values to Multi-Line Strings > -- > > Key: MJAR-39 > URL: http://jira.codehaus.org/browse/MJAR-39 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Specification-Title Tester.zip > > > Maven will set a Manifest attribute's value to a multi-line string, > which results in an invalid Manifest. > By default, on its own, Maven adds a Specification-Title attribute to > the Manifest, and sets its value to the POM's element. If this > is a multi-line value in the POM, Maven will insert it unchanged: and yield > an invalid Manifest. Maven then can't even load the jar that it just created > itself! > I have filed another bug relating to the fact that it should not insert > such an attribute by default: MJAR-38 -- 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: (MWAR-34) Maven Puts Arbitrary Extension Definition in WAR Manifest by Default.
Maven Puts Arbitrary Extension Definition in WAR Manifest by Default. - Key: MWAR-34 URL: http://jira.codehaus.org/browse/MWAR-34 Project: Maven 2.x War Plugin Type: Bug Environment: Maven version: 2.0.4 Microsoft Windows XP [Version 5.1.2600] Reporter: Steven Coco Priority: Blocker Attachments: Maven War Manifest Tester.zip I'm using the latest Maven release. When I build my project, the resulting War file's Manifest contains an Extension-Name attribute along with Specification and Implementation attributes. The POM contains no mention that this project is a Java optional package - an "extension" (or an extension of any other kind); nor any specification or implementation information. What's more: it is not in fact possible to define such an optional package using a War archive. Maven should not do any of this by default. Maven should not include any of these Manifest asttributes unless they are explicitly declared. It appears as if there is a misunderstanding on the meaning of these Manifest attributes. This is the same issue as reported in MJAR-38; and as in that issue, the name Maven uses for the extension name is the POM's which is not even a UID. This is also related to the issue reported in MJAR-39 in that Maven uses the value of the POM's element as the value for the Specification-Title attribute; and if this is a multi-line value, Maven winds up creating an invalid Manifest. I have marked this issue as a Blocker since there is no way to prevent Maven from merging these attributes into the final Manifest. -- 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: (MJAR-39) Maven Sets Manifest Attribute Values to Multi-Line Strings
[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_64390 ] Steven Coco commented on MJAR-39: - This behavior is also happening in the War creation; and there are even more problems there. I have filed an issue on that: MWAR-34. > Maven Sets Manifest Attribute Values to Multi-Line Strings > -- > > Key: MJAR-39 > URL: http://jira.codehaus.org/browse/MJAR-39 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Specification-Title Tester.zip > > > Maven will set a Manifest attribute's value to a multi-line string, > which results in an invalid Manifest. > By default, on its own, Maven adds a Specification-Title attribute to > the Manifest, and sets its value to the POM's element. If this > is a multi-line value in the POM, Maven will insert it unchanged: and yield > an invalid Manifest. Maven then can't even load the jar that it just created > itself! > I have filed another bug relating to the fact that it should not insert > such an attribute by default: MJAR-38 -- 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: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_64391 ] Steven Coco commented on MJAR-38: - This issue is related to MJAR-39 and MWAR-34 in that since it sets the Specification-Title element by default to the POM's element, it easily can create an invalid Manifest. > Maven Puts Arbitrary Extension Definition in JAR Manifest by Default. > - > > Key: MJAR-38 > URL: http://jira.codehaus.org/browse/MJAR-38 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Extension-Name Tester.zip > > > I'm using the latest Maven release. When I build my project, the > resulting Jar file's manifest contains an Extension-Name attribute along with > Specification and Implementation attributes. The POM contains no mention > that this project is a Java optional package -- an "extension" (or an > extension of any other kind). > I don't know why Maven is doing that. > If Maven is doing this by default for some reason, it absolutely > shouldn't. Maven should not identify my Jar as an optional package unless I > explicitly say so. Jars are only extensions if explicitly created as such. > The name it uses for the extension name is the POM's . > That's not even a UID! -- 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: (MJAR-39) Maven Sets Manifest Attribute Values to Multi-Line Strings
[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_64392 ] Steven Coco commented on MJAR-39: - Oops: the first comment I made, which appears redundant with a self-reference, was intended for another issue. Sorry. > Maven Sets Manifest Attribute Values to Multi-Line Strings > -- > > Key: MJAR-39 > URL: http://jira.codehaus.org/browse/MJAR-39 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Specification-Title Tester.zip > > > Maven will set a Manifest attribute's value to a multi-line string, > which results in an invalid Manifest. > By default, on its own, Maven adds a Specification-Title attribute to > the Manifest, and sets its value to the POM's element. If this > is a multi-line value in the POM, Maven will insert it unchanged: and yield > an invalid Manifest. Maven then can't even load the jar that it just created > itself! > I have filed another bug relating to the fact that it should not insert > such an attribute by default: MJAR-38 -- 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: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.
[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_64393 ] Steven Coco commented on MJAR-38: - I should have marked this as a Blocker since there is no way to prevent Maven from merging these attributes into the final Manifest. I downloaded SVN in an attempt to make a patch for these issues, but I had problems with the server and cannot afford the needed time to make a fix. > Maven Puts Arbitrary Extension Definition in JAR Manifest by Default. > - > > Key: MJAR-38 > URL: http://jira.codehaus.org/browse/MJAR-38 > Project: Maven 2.x Jar Plugin > Type: Bug > Versions: 2.0 > Environment: Maven version: 2.0.4 > Microsoft Windows XP [Version 5.1.2600] > Reporter: Steven Coco > Attachments: Jar Extension-Name Tester.zip > > > I'm using the latest Maven release. When I build my project, the > resulting Jar file's manifest contains an Extension-Name attribute along with > Specification and Implementation attributes. The POM contains no mention > that this project is a Java optional package -- an "extension" (or an > extension of any other kind). > I don't know why Maven is doing that. > If Maven is doing this by default for some reason, it absolutely > shouldn't. Maven should not identify my Jar as an optional package unless I > explicitly say so. Jars are only extensions if explicitly created as such. > The name it uses for the extension name is the POM's . > That's not even a UID! -- 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] Closed: (MSUREFIRE-57) Forking documentation improvement to help with class loader constrainst issues
[ http://jira.codehaus.org/browse/MSUREFIRE-57?page=all ] Brett Porter closed MSUREFIRE-57: - Assign To: Brett Porter Resolution: Fixed Fix Version: 2.1.4 > Forking documentation improvement to help with class loader constrainst issues > -- > > Key: MSUREFIRE-57 > URL: http://jira.codehaus.org/browse/MSUREFIRE-57 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.1.3 > Environment: maven 2.0.2 > Reporter: Ben Gidley > Assignee: Brett Porter > Priority: Minor > Fix For: 2.1.4 > Attachments: maven-surefire-plugin-374325.patch > > > With (for example) JAXB2 forking surefire causes a > java.lang.LinkageError: loader constraints violated when linking > javax/xml/namespace/QName class > This is because by default when forking an Isolated class loader is used. > this can be resovled by turning child delegation on. > The documentation does not mention this and should be improved. -- 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: (SUREFIRE-35) refine use of assertion enablement
[ http://jira.codehaus.org/browse/SUREFIRE-35?page=all ] Brett Porter updated SUREFIRE-35: - Fix Version: 2.0 > refine use of assertion enablement > -- > > Key: SUREFIRE-35 > URL: http://jira.codehaus.org/browse/SUREFIRE-35 > Project: surefire > Type: Improvement > Versions: 2.0 > Reporter: Brett Porter > Assignee: Jason van Zyl > Fix For: 2.0 > > > Currently, the assertions are correctly enabled on the classloader when not > forking. However, when forking, setting them on the classloader didn't work, > so -ea is passed in to the forked process. > This is not harmful, though if there were assertions in the surefire provider > or its dependencies (eg, testng), they would be checked unnecessarily. -- 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] Closed: (SUREFIRE-37) System properties not working during forking [surefire-testng branch, patch attached]
[ http://jira.codehaus.org/browse/SUREFIRE-37?page=all ] Brett Porter closed SUREFIRE-37: Assign To: Brett Porter (was: Jason van Zyl) Resolution: Fixed applied, thanks > System properties not working during forking [surefire-testng branch, patch > attached] > - > > Key: SUREFIRE-37 > URL: http://jira.codehaus.org/browse/SUREFIRE-37 > Project: surefire > Type: Bug > Reporter: Christian Schulte > Assignee: Brett Porter > Fix For: 2.0 > Attachments: systemproperties.patch > > > Hi, > just started to try the surefire-testng branch and the maven-surefire-testng > plugin. When setting system properties to the ForkConfiguration a new > Properties instance is created taking the properties as the defaults. When > this properties are written to disk using properties.store() the defaults are > not written to disk. The attached patch changes > ForkConfiguration.setSystemProperties( systemProperties) from > this.systemProperties = new Properties( systemProperties ) to > this.systemProperties = (Properties) systemProperties.clone() and makes > system properties work during forking. -- 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-624) automatic parent versioning
[ http://jira.codehaus.org/browse/MNG-624?page=comments#action_64409 ] Arik Kfir commented on MNG-624: --- two more cents: imo the algoritm should do the following: (in specified order) 1. if a version is given, resolve it from reactor/repository 2. otherwise, if a path is given, use that 3. otherwise, if the project has an SCM, retrieve it from the scm (using same tag/branch/etc) 4. error > automatic parent versioning > --- > > Key: MNG-624 > URL: http://jira.codehaus.org/browse/MNG-624 > Project: Maven 2 > Type: Improvement > Components: Inheritence and Interpolation > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Blocker > Fix For: 2.1 > > Original Estimate: 4 hours > Remaining: 4 hours > > (this may be bumped to 2.1 or even made WON't FIX as it is contentious - see > MNG-521) > currently, you have to specify the parent version when extending which makes > a project stand alone very easily, but has the drawback of being a > maintainance problem when you start development on a new version. Tools can > help, but it would be nice not to have to rely on them. > One alternative is to allow the parent version to be omitted, and when it is > it is assumed you want the latest. The parent is used from the reactor or the > universal source directory. IT may also be read from a LATEST in the > repository though this is contentious - it may be better to simply fail in > that environment and require builds be in a known checkout structure for > building individual projects. > This also introduces the need for tool support to populate the version on > release and deployment for reproducibility. -- 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: (MASSEMBLY-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=all ]
Dan Tran updated MASSEMBLY-89:
--
Fix Version: 2.1
Environment: xp
> outputFileNameMapping broken
>
>
> Key: MASSEMBLY-89
> URL: http://jira.codehaus.org/browse/MASSEMBLY-89
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Environment: xp
> Reporter: Dan Tran
> Priority: Critical
> Fix For: 2.1
>
>
> Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
> all dependency aritifacts into assembly without the version
> Here is an exmple
>
>
>
> ${artifactId}.${extension}
>
>
> After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
> a single file ${artifactId}.${extention}
--
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: (MASSEMBLY-89) outputFileNameMapping broken
outputFileNameMapping broken
Key: MASSEMBLY-89
URL: http://jira.codehaus.org/browse/MASSEMBLY-89
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.1
Reporter: Dan Tran
Priority: Critical
Fix For: 2.1
Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place all
dependency aritifacts into assembly without the version
Here is an exmple
${artifactId}.${extension}
After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to a
single file ${artifactId}.${extention}
--
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-1330) direct support for mock classes
[ http://jira.codehaus.org/browse/MNG-1330?page=comments#action_64410 ] Arik Kfir commented on MNG-1330: I disagree - there are too many source dirs already, and the test-jar works perfectly...no need to complicate things, IMO. > direct support for mock classes > --- > > Key: MNG-1330 > URL: http://jira.codehaus.org/browse/MNG-1330 > Project: Maven 2 > Type: New Feature > Versions: 2.0 > Reporter: Jorg Heymans > Fix For: 2.1 > > > a element of some sort would allow projects to easily > deal with mock classes. > At the moment you would have to create a separate module myproject-mocks and > include it as a dependency in your project. -- 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: (MCHANGELOG-35) Wrong time format, unable to be parsed by cvs
Wrong time format, unable to be parsed by cvs - Key: MCHANGELOG-35 URL: http://jira.codehaus.org/browse/MCHANGELOG-35 Project: Maven 2.x Changelog Plugin Type: Bug Reporter: Carlos Sanchez >From th log [INFO] Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvs -q log -d '"2006-03-30T19:21:58-0800<2006-04-30T20:21:58-0700"' The date parsing fails in cvs cvs [log aborted]: Can't parse date/time: '2006-03-30T19:21:58-0800 -- 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: (MCHANGELOG-35) Wrong time format, unable to be parsed by cvs
[ http://jira.codehaus.org/browse/MCHANGELOG-35?page=all ] Carlos Sanchez updated MCHANGELOG-35: - Version: 2.0 Fix Version: 2.0 > Wrong time format, unable to be parsed by cvs > - > > Key: MCHANGELOG-35 > URL: http://jira.codehaus.org/browse/MCHANGELOG-35 > Project: Maven 2.x Changelog Plugin > Type: Bug > Versions: 2.0 > Reporter: Carlos Sanchez > Fix For: 2.0 > > > From th log > [INFO] Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvs -q log -d > '"2006-03-30T19:21:58-0800<2006-04-30T20:21:58-0700"' > The date parsing fails in cvs > cvs [log aborted]: Can't parse date/time: '2006-03-30T19:21:58-0800 -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
cannot run junit testcases from within Eclipse -- Key: MNGECLIPSE-114 URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 Project: Maven 2.x Extension for Eclipse Type: Bug Environment: OSX, Eclipse 3.2RC1 Reporter: Torsten Curdt Assigned to: Eugene Kuleshov Dependencies seem to get ignored when running junit testcases from within Eclipse. I just get an exception: java.lang.NoClassDefFoundError: junit/framework/TestListener The junit jar is listed through the maven dependencies though. When I add it by hand (add external jar) junit starts up but then I am missing my other dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64411 ] Eugene Kuleshov commented on MNGECLIPSE-114: Torsten, would you mind to attach your Eclipse project here (or something we can test with) and provide step by step instructions on what exactly you are doing. PS: btw, what a small world... :-) > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: tests.tgz workspace.tgz > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64414 ] Eugene Kuleshov commented on MNGECLIPSE-114: Ok, great. But how are you running this stuff? And just in case, what Eclipse version you are running? And on what JRE? > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: eclipse.png > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: run.png > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png, tests.tgz, workspace.tgz > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Eugene Kuleshov updated MNGECLIPSE-114: --- Attachment: (was: tests.tgz) > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Eugene Kuleshov updated MNGECLIPSE-114: --- Attachment: (was: workspace.tgz) > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64416 ] Eugene Kuleshov commented on MNGECLIPSE-114: Apparently your attachment haven't had any code. So, I checked out project from SVN and were able to run some tests. It worked for me as a single project (starting from trunk folter) as well as several projects like in your layout. Though I am running on Windows and I had to turn offline mode off and build this stuff from command line "mvn install" in order to get poms into the local repository. So, it is either something in your setup or OS X thing. Can you try to delete launch configuration and run that test again using "Run As... / JUnit test" menu , say, on the project node. Then do to the Debug perspective and open properties for java process. It should show you the command line used by junit runner and you should be able to see junit jars up there. > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64417 ] Torsten Curdt commented on MNGECLIPSE-114: -- >From the command line test are running fine for me as well. Started with a fresh launch config and this is what gets called: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -classpath /Users/tcurdt/dev/jakarta/commons-jci/tests/target/classes:/Users/tcurdt/dev/jakarta/commons-jci/core/target/classes:/Users/tcurdt/.m2/repository/commons-collections/commons-collections/3.1/commons-collections-3.1.jar:/Users/tcurdt/.m2/repository/commons-io/commons-io/1.1/commons-io-1.1.jar:/Users/tcurdt/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar:/Users/tcurdt/.m2/repository/commons-logging/commons-logging-api/1.0.4/commons-logging-api-1.0.4.jar:/Applications/eclipse-SDK-3.2RC1/plugins/org.eclipse.jdt.junit_3.2.0.v20060412-1600/junitsupport.jar:/Applications/eclipse-SDK-3.2RC1/plugins/org.eclipse.jdt.junit.runtime_3.2.0.v20060412-1600/junitruntime.jar org.eclipse.jdt.internal.junit.runner.RemoteTestRunner -version 3 -port 59767 -testNameFile /tmp/testNames33471.txt No junit jar! And other dependencies are missing, too! The test subproject also depends on all the compiler modules and they have dependencies to the compiler implementations. They are not in the path either. > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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-2257) Failed to parse pom.xml when set to 1.5 source and target
Failed to parse pom.xml when set to 1.5 source and target - Key: MNG-2257 URL: http://jira.codehaus.org/browse/MNG-2257 Project: Maven 2 Type: Bug Components: POM Versions: 2.0.4 Environment: java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode) Cygwin on Windows XP Reporter: Hanson Char Attachments: mvn.log, pom.xml mvn failed to parse a simple pom which is set to use jdk 1.5 source and target -- 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-2257) Failed to parse pom.xml when set to 1.5 source and target
[ http://jira.codehaus.org/browse/MNG-2257?page=comments#action_64418 ] Hanson Char commented on MNG-2257: -- The mvn.log was generated when I typed: mvn compile | tee mvn.log > Failed to parse pom.xml when set to 1.5 source and target > - > > Key: MNG-2257 > URL: http://jira.codehaus.org/browse/MNG-2257 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0.4 > Environment: java version "1.5.0_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode) > Cygwin on Windows XP > Reporter: Hanson Char > Attachments: mvn.log, pom.xml > > > mvn failed to parse a simple pom which is set to use jdk 1.5 source and target -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64419 ] Eugene Kuleshov commented on MNGECLIPSE-114: What can I say. You'll have to show me your eclipse projects. Try to zip them up, but make sure they are in the archive (especially .classpath and .project for all projects). I don't need stuff from within .metadata One more thing. Open up m2 console clear it, run Project / Clean... for your java projects and check that there is no errors. Open Type dialog (Ctrl-Shift-T) should also show junit classes from jars located in m2 repository. Which means m2 classpath container is working fine. > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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-2257) Failed to parse pom.xml when set to 1.5 source and target
[ http://jira.codehaus.org/browse/MNG-2257?page=comments#action_64421 ] Wendy Smoak commented on MNG-2257: -- This probably would have been better directed to the user list than the issue tracker. The reason for the failure is that the (singular) element for maven-compiler-plugin is missing. You have: // It should be: /// It's interesting that the error message mentions / rather than the real cause of the problem. > Failed to parse pom.xml when set to 1.5 source and target > - > > Key: MNG-2257 > URL: http://jira.codehaus.org/browse/MNG-2257 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0.4 > Environment: java version "1.5.0_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode) > Cygwin on Windows XP > Reporter: Hanson Char > Attachments: mvn.log, pom.xml > > > mvn failed to parse a simple pom which is set to use jdk 1.5 source and target -- 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-2257) Failed to parse pom.xml when set to 1.5 source and target
[ http://jira.codehaus.org/browse/MNG-2257?page=comments#action_64420 ] Wayne Fay commented on MNG-2257: This is just a bad pom. You're missing a node inside the node to contain the artifactId, configuration, etc nodes. > Failed to parse pom.xml when set to 1.5 source and target > - > > Key: MNG-2257 > URL: http://jira.codehaus.org/browse/MNG-2257 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0.4 > Environment: java version "1.5.0_06" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) > Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode) > Cygwin on Windows XP > Reporter: Hanson Char > Attachments: mvn.log, pom.xml > > > mvn failed to parse a simple pom which is set to use jdk 1.5 source and target -- 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: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse
[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: commons-jci.tgz > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Environment: OSX, Eclipse 3.2RC1 > Reporter: Torsten Curdt > Assignee: Eugene Kuleshov > Attachments: commons-jci.tgz, eclipse.png, run.png > > > Dependencies seem to get ignored when running junit testcases from within > Eclipse. I just get an exception: > java.lang.NoClassDefFoundError: junit/framework/TestListener > The junit jar is listed through the maven dependencies though. When I add it > by hand (add external jar) junit starts up but then I am missing my other > dependencies. -- 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
