[jira] Commented: (MSUREFIRE-131) Surefire-JUnit does not recognize "suite"-methods
[ http://jira.codehaus.org/browse/MSUREFIRE-131?page=comments#action_72234
]
Brett Porter commented on MSUREFIRE-131:
Jochen - you mean it can't be reproduced, or the patch no longer applies?
> Surefire-JUnit does not recognize "suite"-methods
> -
>
> Key: MSUREFIRE-131
> URL: http://jira.codehaus.org/browse/MSUREFIRE-131
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Philip Gerlach
> Fix For: 2.3
>
> Attachments: commons-events-pom.xml,
> maven-surefire-junit-trunk-412516.patch
>
>
> Since Surefire-JUnit doesn't support JUnit4 yet, i tried to use a
> "suite"-method like
> --
> public static junit.framework.Test suite() {
>return new junit.framework.JUnit4TestAdapter(Foo.class);
> }
> -
> to run it, but Surefire-JUnit did not recognize these methods and treated
> them like PojoTests what obviously lead to TestFailures.
> So I fetched the source code from the repository and searched for the
> problem. I found two if-conditons in JUnitTestSet and JUnitDirectoryTestSuite
> that did not test for the "suite"-mechanism, so I wrote a new static method
> to test for this situation and integrated it in the if-conditions.
> Now the "suite"-methods work for my JUnit4 Tests and should do also for
> others ;-)
> The patch is attached.
> P.S. Since this it is the first time, I'm trying to bugfix something for an
> open source-project, please just let me know, if I have done something wrong
> with this process.
--
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-1029) fit-1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1029?page=comments#action_72233 ] Mauro Talevi commented on MAVENUPLOAD-1029: --- Sorry, had misunderstood them! Here is the bundle. http://agilesque.net/dist/fit/jars/fit-1.1-bundle.jar > fit-1.1 > > > Key: MAVENUPLOAD-1029 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1029 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Mauro Talevi > Assigned To: Carlos Sanchez > > Please upload fit-1.1.jar with POM > > 4.0.0 > fit > fit > Fit > 1.1 > > -- 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-1044) Cojen 1.1.4 bundle upload
Cojen 1.1.4 bundle upload - Key: MAVENUPLOAD-1044 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1044 Project: maven-upload-requests Issue Type: Task Reporter: Brian S O'Neill Cojen is a Java library which makes it easy to dynamically generate and inject Java bytecode. I am listed as lead developer "broneill" on the team-list page. http://cojen.sourceforge.net/team-list.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
[jira] Commented: (MSUREFIRE-131) Surefire-JUnit does not recognize "suite"-methods
[ http://jira.codehaus.org/browse/MSUREFIRE-131?page=comments#action_72232
]
Jochen Wiedmann commented on MSUREFIRE-131:
---
For whatever reason, this problem doesn't seem to apply to version 2.3-SNAPSHOT
of the maven-surefire-plugin.
> Surefire-JUnit does not recognize "suite"-methods
> -
>
> Key: MSUREFIRE-131
> URL: http://jira.codehaus.org/browse/MSUREFIRE-131
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Philip Gerlach
> Fix For: 2.3
>
> Attachments: commons-events-pom.xml,
> maven-surefire-junit-trunk-412516.patch
>
>
> Since Surefire-JUnit doesn't support JUnit4 yet, i tried to use a
> "suite"-method like
> --
> public static junit.framework.Test suite() {
>return new junit.framework.JUnit4TestAdapter(Foo.class);
> }
> -
> to run it, but Surefire-JUnit did not recognize these methods and treated
> them like PojoTests what obviously lead to TestFailures.
> So I fetched the source code from the repository and searched for the
> problem. I found two if-conditons in JUnitTestSet and JUnitDirectoryTestSuite
> that did not test for the "suite"-mechanism, so I wrote a new static method
> to test for this situation and integrated it in the if-conditions.
> Now the "suite"-methods work for my JUnit4 Tests and should do also for
> others ;-)
> The patch is attached.
> P.S. Since this it is the first time, I'm trying to bugfix something for an
> open source-project, please just let me know, if I have done something wrong
> with this process.
--
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-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72226 ] Andrew Williams commented on MAVENUPLOAD-1032: -- I have updated the pom in the bundle (new version at the same URL) org.schwering is correct, go to http://schwering.org/ and click on "~chs" - you will see IRCLib listed... > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- 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: (MSUREFIRE-158) Add Parameter that the output of the test to System.out only appears in the surefire logfiles
[ http://jira.codehaus.org/browse/MSUREFIRE-158?page=comments#action_72225 ] Brett Porter commented on MSUREFIRE-158: have you tried this with trunk (ie, built it yourself?) - this is what you've indicated by a fix version of 2.3 but I'm not sure if that's what you meant. It should be fixed there, but maybe I'm misunderstanding what you wanted. > Add Parameter that the output of the test to System.out only appears in the > surefire logfiles > - > > Key: MSUREFIRE-158 > URL: http://jira.codehaus.org/browse/MSUREFIRE-158 > Project: Maven 2.x Surefire Plugin > Issue Type: New Feature >Affects Versions: 2.3 >Reporter: Fabian Bauschulte > > Many Tests are using a logger that prints to the console. Sometimes you > cannot see the summary because there a lot of logging messages. It would be > very helpful to have a parameter, that this output only appears in the > surefire log files. If a test fails, you have the output in the place you > need 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
[jira] Closed: (MSUREFIRE-157) ClassNotFoundException or NoClassDefFoundError executing maven2 install
[ http://jira.codehaus.org/browse/MSUREFIRE-157?page=all ]
Brett Porter closed MSUREFIRE-157.
--
Assignee: Brett Porter
Resolution: Won't Fix
this problem is already covered in the jar plugin - thanks
> ClassNotFoundException or NoClassDefFoundError executing maven2 install
> ---
>
> Key: MSUREFIRE-157
> URL: http://jira.codehaus.org/browse/MSUREFIRE-157
> Project: Maven 2.x Surefire Plugin
> Issue Type: Wish
> Environment: eclipse 3.2, windows XP and j2se 1.4.2
>Reporter: Francesc Xavier
> Assigned To: Brett Porter
>
> Hey,
> first all congratultions for your execellent job. We are using Maven2 in
> order to develop a project. This project has several modules with
> dependencies among them, reflected in their pom's. When we try to execute a
> test from the project root in command line (typing mvn test) all works fine,
> but when we try to execute 'mvn install', all the tests of modules that have
> dependencies with other modules (in our case, the core module) begins to fail
> throwing a java.lang.NoClassDefFoundError. Moreover, when we try to execute
> the same tests to the specific module the same error is produced.
> Pom parent has the following definitons
>
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns="http://maven.apache.org/POM/4.0.0";>
> 4.0.0
> com.nextret.frwk
> openfrwk-all
> pom
> NexTReT Open Framework
> 2006
> 0.1-SNAPSHOT
>
> 2.0.4
>
>
> openfrwk-core
> openfrwk-instrument
> openfrwk-mock
> openfrwk-ejbgateway
> openfrwk-security
> openfrwk-persistence
> openfrwk-tasks
> openfrwk-services
> openfrwk-services-jboss
>
> ..
> (we have not included the dependencies that all are correctly retrieved from
> repository) and every pom module chlid has
>
> 4.0.0
>
> com.nextret.frwk
> openfrwk-all
> 0.1-SNAPSHOT
>
> com.nextret.frwk
> openfrwk-core
> jar
> Core
> (also including the dependency of core module in dependencies element)
>
>
> ${project.groupId}
> openfrwk-core
> 0.1-SNAPSHOT
>
> ...
>
> any suggestion ?? we have to skip all the tests (currently executed in
> eclipse), but we realize that are not the best way!!
> Thanks a lot!!
> Francesc Xavier
--
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: (WAGON-60) wagon-webdav fails with commons-logging classloader issues
[ http://jira.codehaus.org/browse/WAGON-60?page=comments#action_72223 ] Dennis Lundberg commented on WAGON-60: -- A good way to diagnose problems regarding commons-logging and classloading issues is to upgrade the dependency on commons-logging to version 1.1. That version has some great new diagnostics that can be turned on. You can read more on how to do this in the Commons Logging troubleshooting guide: http://jakarta.apache.org/commons/logging/troubleshooting.html#How_To_Use_Diagnostic_logging > wagon-webdav fails with commons-logging classloader issues > -- > > Key: WAGON-60 > URL: http://jira.codehaus.org/browse/WAGON-60 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-1 > Environment: maven 2.0.4 >Reporter: Yuri Schimke >Priority: Critical > > I tried it with a build extension and also putting jars in $M2_HOME/lib, but > both ways I get classloader issues with commons-logging. > My project uses commons logging and I've seen at least one other report that > it can be a problem. > with things in lib: > Caused by: org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: Invalid class loader > hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by > org.apache.commons.logging.LogConfigurationException: Invalid class loader > hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by > org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: Invalid class loader > hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by > org.apache.commons.logging.LogConfigurationException: Invalid class loader > hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed.)) > at > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) > at > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) > at > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) > at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) > at > org.apache.commons.httpclient.HttpClient.(HttpClient.java:69) > ... 30 more > Caused by: org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: Invalid class loader > hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by > org.apache.commons.logging.LogConfigurationException: Invalid class loader > hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed.) > at > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) > at > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) > ... 34 more > Caused by: org.apache.commons.logging.LogConfigurationException: Invalid > class loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. > at > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) > using build extension: > java.lang.ExceptionInInitializerError > at > org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:145) > at > org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:127) > at > org.apache.webdav.lib.WebdavResource.setClient(WebdavResource.java:1273) > at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1298) > at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320) > at > org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408) > at > org.apache.webdav.lib.WebdavResource.(WebdavResource.java:290) > at > org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.(CorrectedWebdavResource.java:52) > at > org.apache.maven.wagon.providers.webdav.WebDavWagon.openConnection(WebDavWagon.java:139) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106) > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:132) > at > org.apache.maven.plugin.DefaultPluginManager.executeM
[jira] Created: (WAGON-60) wagon-webdav fails with commons-logging classloader issues
wagon-webdav fails with commons-logging classloader issues -- Key: WAGON-60 URL: http://jira.codehaus.org/browse/WAGON-60 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-1 Environment: maven 2.0.4 Reporter: Yuri Schimke Priority: Critical I tried it with a build extension and also putting jars in $M2_HOME/lib, but both ways I get classloader issues with commons-logging. My project uses commons logging and I've seen at least one other report that it can be a problem. with things in lib: Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.commons.httpclient.HttpClient.(HttpClient.java:69) ... 30 more Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 34 more Caused by: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) using build extension: java.lang.ExceptionInInitializerError at org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:145) at org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:127) at org.apache.webdav.lib.WebdavResource.setClient(WebdavResource.java:1273) at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1298) at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320) at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408) at org.apache.webdav.lib.WebdavResource.(WebdavResource.java:290) at org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.(CorrectedWebdavResource.java:52) at org.apache.maven.wagon.providers.webdav.WebDavWagon.openConnection(WebDavWagon.java:139) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:132) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor
[jira] Commented: (MAVENUPLOAD-1030) Please upload json-lib-0.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1030?page=comments#action_7 ] Andres Almiray commented on MAVENUPLOAD-1030: - I used the exported-pom.xml file, because I thought it was created by the repository plugin. I have updated the json-lib-0.7.1.-bundle.jar with the source pom.xml. > Please upload json-lib-0.6 > -- > > Key: MAVENUPLOAD-1030 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1030 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > JSON-lib is a java library for transforming beans, maps and XML to JSON and > back again to beans and DynaBeans. > Javadocs are at http://json-lib.sourceforge.net/json-lib-0.6-javadoc.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] Commented: (MAVENUPLOAD-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72221 ] Carlos Sanchez commented on MAVENUPLOAD-1032: - you have to prove that the project owns that domain to use that groupId I only see moepii.sourceforge.net And yes, you need a new bundle > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- 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-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72220 ] Andrew Williams commented on MAVENUPLOAD-1032: -- OK, I see - suppose org.schwering is better. No, there are no dependencies. Do you need a new bundle for different groupId? > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- 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: (MPMD-38) Add Posibility to excludes files in Cpd
[ http://jira.codehaus.org/browse/MPMD-38?page=all ] Mike Perham closed MPMD-38. --- Resolution: Fixed Implemented. > Add Posibility to excludes files in Cpd > --- > > Key: MPMD-38 > URL: http://jira.codehaus.org/browse/MPMD-38 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement >Reporter: Fabian Bauschulte > Fix For: 2.2 > > Attachments: MPMD-38-maven-pmd-plugin.patch > > > Sometimes there are Classes, that you do not want to be checked (legacy code, > generated classes). In some cases (for instance generated classes) there a > lot of warnings that cannot be removed. In this case the "false" warnings are > hiding the "important" warnings. -- 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: (MCHANGELOG-43) Changelog not getting created properly.
[ http://jira.codehaus.org/browse/MCHANGELOG-43?page=comments#action_72218 ] Dennis Lundberg commented on MCHANGELOG-43: --- I'm a bit confused now, that's probably because I have never used Perforce. Is your Perforce repository located on your machine or on another machine? Can you issue other scm commands? Like this one: mvn scm:status > Changelog not getting created properly. > --- > > Key: MCHANGELOG-43 > URL: http://jira.codehaus.org/browse/MCHANGELOG-43 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Windows xp SP2 / maven 2.0.4 >Reporter: Abhijit Diwan > > I am trying to generate change log for my maven project. > I have following scm section under my pom.xml > > scm:perforce://EJB/ejb-dev/MavenCodeline/ > > and following plugin decalration under section > > org.codehaus.mojo > changelog-maven-plugin > > > Perofrce report > > range > 10 > > > scm:perforce://EJB/ejb-dev/MavenCodeline/ > > > > org.apache.maven.perforcelib.PerforceChangeLogFactory > > > > changelog > file-activity > dev-activity > > > > > I have already defined P4PORT variable on my machine. > When I ran mvn site command from module directory AeConnector I get following > error. > [INFO] Generating changed sets xml to: > E:\views\EJB\ejb-dev\MavenCodeline\AeConn > ector\target\changelog.xml > [INFO] SCM Working Directory: > E:\views\EJB\ejb-dev\MavenCodeline\AeConnector\src > \main\java > [INFO] SCM Command Line[0]: p4 > [INFO] SCM Command Line[1]: filelog > [INFO] SCM Command Line[2]: -tl > [INFO] SCM Command Line[3]: //EJB/ejb-dev/MavenCodeline/AeConnector > [ERROR] //EJB/ejb-dev/MavenCodeline/AeConnector - no such file(s). > All my java code is under that directory but the plugin is not able to > recurse all the subdirectories under that directory. I looked at perforce doc > and ran command "p4 filelog //EJB/ejb-dev/MavenCodeline/AeConnector/..." and > it worked so I think with plugin those last 3 dots which makes p4 recurse is > not there. The documentation for p4 command you can find from following url - > (http://www.perforce.com/perforce/doc.051/manuals/cmdref/filelog.html) > Please please help. > thanks a lot > abhijit -- 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: (MEV-413) Jaxen has unnecessary and unexpected dependencies (which cause problems with JDK 1.5)
[ http://jira.codehaus.org/browse/MEV-413?page=comments#action_72216 ] Carlos Sanchez commented on MEV-413: the fact that jdk 5 includes xml parser doesn't mean that the dependency is not needed. It must be there at least for JDK 1.4. Adding them to dependencies is not the problem, maybe you need to fork your tests or do some other configuration to avoid the problems. Unless you give a reason why this is a problem this is a wont fix. > Jaxen has unnecessary and unexpected dependencies (which cause problems with > JDK 1.5) > - > > Key: MEV-413 > URL: http://jira.codehaus.org/browse/MEV-413 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies >Reporter: Jimisola Laursen > > The pom > (http://www.ibiblio.org/maven2/jaxen/jaxen/1.1-beta-9/jaxen-1.1-beta-9.pom) > has dependencies on domj, jdom, xom, xerces:xercesImpl and > xerces:xmlParserAPIs (see below). > I can't see why any of these dependencies are necessary - especially not the > dependency on xerces. A slimmed down verson of Xerces is included with JDK > 1.5 and adding an addition Xerces in the classpath caused some major > headache. JDK 1.5 or not, I have the exclude all the dependencies that Jaxen > 1.1-beta-9 has. > > > dom4j > dom4j > 1.6.1 > > > jdom > jdom > 1.0 > > > xerces > xmlParserAPIs > 2.6.2 > > > xerces > xercesImpl > 2.6.2 > > > xom > xom > 1.0b3 > > -- 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: (MEV-431) axis-jaxrpc and axis-saaj both version 1.4 have no POM
[ http://jira.codehaus.org/browse/MEV-431?page=comments#action_72217 ] Carlos Sanchez commented on MEV-431: we dont upload poms just for having them. Only correct poms are uploaded and what you provide are missing a lot of info, specially dependencies > axis-jaxrpc and axis-saaj both version 1.4 have no POM > -- > > Key: MEV-431 > URL: http://jira.codehaus.org/browse/MEV-431 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Aede > > Both axis-saaj and axis-jaxrpc (which specified as dependencies in > axis:axis:pom:1.4) do not have a pom of their own. This will cause maven to > use stubs and not store de deps in its local repo. > axis-saaj would need a pom (axis-saaj-1.4.pom) with the following content: > > 4.0.0 > axis > axis-saaj > 1.4 > > axis-saaj would need a pom (axis-jaxrpc-1.4.pom) with the following content: > > 4.0.0 > axis > axis-jaxrpc > 1.4 > -- 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-1030) Please upload json-lib-0.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1030?page=comments#action_72215 ] Carlos Sanchez commented on MAVENUPLOAD-1030: - why absolute paths in pom? repositories and pluginRepositories must be removed, they are already included by default > Please upload json-lib-0.6 > -- > > Key: MAVENUPLOAD-1030 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1030 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > JSON-lib is a java library for transforming beans, maps and XML to JSON and > back again to beans and DynaBeans. > Javadocs are at http://json-lib.sourceforge.net/json-lib-0.6-javadoc.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] Commented: (MAVENUPLOAD-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72214 ] Carlos Sanchez commented on MAVENUPLOAD-1032: - why org.schwering.irc groupId? see instructions no dependencies? > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- 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: (MAVENUPLOAD-1040) remove unused folder "not-really-jelly/commons-jelly/"
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1040?page=all ] Carlos Sanchez closed MAVENUPLOAD-1040. --- Resolution: Fixed will be in ibiblio in few hours > remove unused folder "not-really-jelly/commons-jelly/" > -- > > Key: MAVENUPLOAD-1040 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1040 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Rainer Wasserfuhr > Assigned To: Carlos Sanchez > > http://www.ibiblio.org/maven2/not-really-jelly/commons-jelly/ is empty, > so both > http://www.ibiblio.org/maven2/not-really-jelly/commons-jelly/ and > http://www.ibiblio.org/maven2/not-really-jelly > could be removed. -- 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: (MPMD-37) Embedded error produced when failing parse on a hibernate annotation (3.1beta9) in java file
[ http://jira.codehaus.org/browse/MPMD-37?page=all ]
Mike Perham closed MPMD-37.
---
Assignee: Mike Perham
Resolution: Cannot Reproduce
This is Not a Bug. The problem is in PMD itself and we are using the latest
available release. Please enter a bug into the PMD issue tracker @ SourceForge
if you want to see this fixed.
> Embedded error produced when failing parse on a hibernate annotation
> (3.1beta9) in java file
>
>
> Key: MPMD-37
> URL: http://jira.codehaus.org/browse/MPMD-37
> Project: Maven 2.x Pmd Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: MACOSX 10.4.7 (PowerPC)
>Reporter: Simon Baker
> Assigned To: Mike Perham
>
> Running mvn pmd:check produces the error:
> Embedded error: Failure executing PMD for:
> /Users/simon/Eclipse/workspace/Gratr/src/main/java/com/aol/cms/domain/CMSContentObject.java
> Encountered "}" at line 16, column 58.
> Was expecting one of:
> "boolean" ...
> "byte" ...
> "char" ...
> "double" ...
> "false" ...
> "float" ...
> "int" ...
> "long" ...
> "new" ...
> "null" ...
> "short" ...
> "super" ...
> "this" ...
> "true" ...
> "void" ...
> ...
> ...
> ...
> ...
> ...
> "(" ...
> "{" ...
> "@" ...
> "!" ...
> "~" ...
> "++" ...
> "--" ...
> "+" ...
> "-" ...
> In the CMSContentObject.java file, line 16, column 58: @Table(name =
> "cms_content_object", uniqueConstraints = {})
>
> Here's what's in the pom.xml:
>
> org.apache.maven.plugins
> maven-pmd-plugin
> 2.1
> test
>
>
> org.hibernate
> hibernate
> 3.2.0.cr1
> compile
>
>
> org.hibernate
> hibernate-annotations
> 3.1beta9
> compile
>
>
>
> ...
>
> org.apache.maven.plugins
> maven-pmd-plugin
>
> true
> UTF-8
> 100
> 1.5
>
>
> ...
>
>
--
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: (MPIR-54) Team list table improvement
[ http://jira.codehaus.org/browse/MPIR-54?page=comments#action_72211 ]
Arik Kfir commented on MPIR-54:
---
I noticed that your patch creates two organization columns - one for the
organization name ("Organization") and one for the organization URL
("Organization URL").
Perhaps it is better to unify them to one column simply called "Organization"
that always displays the organization name, but if an organization URL is
specified in the POM, that label becomes a link to that URL. This would save
some space in the table.
> Team list table improvement
> ---
>
> Key: MPIR-54
> URL: http://jira.codehaus.org/browse/MPIR-54
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.0-beta-3, 2.0, 2.0.1
>Reporter: Dmitry Kobyleha
> Attachments: TeamListReport.java
>
>
> When fo all developers in pom.xml we some property not defined, it is good to
> not include it to html output.
> Fow example:
> ...
>
> developer1
> Developer 1
> [EMAIL PROTECTED]
>
> Project Manager
> Architect
> Java Developer
>
> +2
>
>
> developer2
> Developer 2
> [EMAIL PROTECTED]
>
> Java Developer
>
> +2
>
> ...
> For both developers properties like URL, Organization,Organization
> URL and Properties not specified. In result html we have cells with "-".
> As for me it is good not not include columns where only "-" present at all.
--
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: (MPIR-54) Team list table improvement
[ http://jira.codehaus.org/browse/MPIR-54?page=all ] Dmitry Kobyleha updated MPIR-54: Attachment: TeamListReport.java Try my implementation of this issue. You can look on 2.0.1 generation there: http://embedchat.org/team-list-old.html And on list generated with this change: http://embedchat.org/team-list.html Maybe it is useful to make this configurable? > Team list table improvement > --- > > Key: MPIR-54 > URL: http://jira.codehaus.org/browse/MPIR-54 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-3, 2.0, 2.0.1 >Reporter: Dmitry Kobyleha > Attachments: TeamListReport.java > > > When fo all developers in pom.xml we some property not defined, it is good to > not include it to html output. > Fow example: > ... > > developer1 > Developer 1 > [EMAIL PROTECTED] > > Project Manager > Architect > Java Developer > > +2 > > > developer2 > Developer 2 > [EMAIL PROTECTED] > > Java Developer > > +2 > > ... > For both developers properties like URL, Organization,Organization > URL and Properties not specified. In result html we have cells with "-". > As for me it is good not not include columns where only "-" present at all. -- 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: (MSITE-174) Default bundle used not correct
Default bundle used not correct
---
Key: MSITE-174
URL: http://jira.codehaus.org/browse/MSITE-174
Project: Maven 2.x Site Plugin
Issue Type: Bug
Environment: trunk, french os
Reporter: Vincent Siveton
Using this configuration, MSITE produces only french reports:
{code:xml}
fr,en
{code}
--
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] Reopened: (MAVENUPLOAD-1040) remove unused folder "not-really-jelly/commons-jelly/"
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1040?page=all ] Rainer Wasserfuhr reopened MAVENUPLOAD-1040: hmh, "fixed" or "wontfix"? The folders do still exist. > remove unused folder "not-really-jelly/commons-jelly/" > -- > > Key: MAVENUPLOAD-1040 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1040 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Rainer Wasserfuhr > Assigned To: Carlos Sanchez > > http://www.ibiblio.org/maven2/not-really-jelly/commons-jelly/ is empty, > so both > http://www.ibiblio.org/maven2/not-really-jelly/commons-jelly/ and > http://www.ibiblio.org/maven2/not-really-jelly > could be removed. -- 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: (MSUREFIRE-158) Add Parameter that the output of the test to System.out only appears in the surefire logfiles
Add Parameter that the output of the test to System.out only appears in the surefire logfiles - Key: MSUREFIRE-158 URL: http://jira.codehaus.org/browse/MSUREFIRE-158 Project: Maven 2.x Surefire Plugin Issue Type: New Feature Affects Versions: 2.3 Reporter: Fabian Bauschulte Many Tests are using a logger that prints to the console. Sometimes you cannot see the summary because there a lot of logging messages. It would be very helpful to have a parameter, that this output only appears in the surefire log files. If a test fails, you have the output in the place you need 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
