date:20101013

[jira] Created: (MCOMPILER-136) The description of the skip parameter of the testCompile mojo is incorrect

2010-10-13 Thread Anders Hammar (JIRA)

The description of the skip parameter of the testCompile mojo is incorrect
--

 Key: MCOMPILER-136
 URL: http://jira.codehaus.org/browse/MCOMPILER-136
 Project: Maven 2.x Compiler Plugin
  Issue Type: Bug
Affects Versions: 2.3.2
 Environment: n/a
Reporter: Anders Hammar
Priority: Trivial


The description of the skip parameter of TestCompilerMojo should read:

Set this to 'true' to bypass compilation of test sources.

I also think that the text Its use is NOT RECOMMENDED, but quite convenient on 
occasion. should 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] Commented: (MJAVADOC-295) javadoc plugin version: 2.5, 2.6, 2.7 does not follow the reactor build sequence mvn install site site:deploy

2010-10-13 Thread Matthias Frenzel (JIRA)


[ 
http://jira.codehaus.org/browse/MJAVADOC-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239431#action_239431
 ] 

Matthias Frenzel commented on MJAVADOC-295:
---

JDK 6 Update 20 is used.

 javadoc plugin version: 2.5, 2.6, 2.7 does not follow the reactor build 
 sequence mvn install site site:deploy
 ---

 Key: MJAVADOC-295
 URL: http://jira.codehaus.org/browse/MJAVADOC-295
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.5, 2.6, 2.7
 Environment: Windows XP, Maven 2.2.1
Reporter: Matthias Frenzel

 If i use the javadoc plugin version: 2.5, 2.6, 2.7 (these are the version 
 that i´ve checked).
 mvn install site-deploy does not follow the reactor build sequence
 and the complete build failed.
 If i use the javadoc plugin version 2.4 it works correct.
 Similar like: http://jira.codehaus.org/browse/MSITE-302

-- 
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: (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

2010-10-13 Thread Tim Pizey (JIRA)


[ 
http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239433#action_239433
 ] 

Tim Pizey commented on SUREFIRE-569:


This can be done as follows (junit3): 

Ensure test jar contains a class which has a static suite() method

import junit.framework.Test;
import junit.framework.TestSuite;

public class AllTests {

public static Test suite() {
TestSuite suite = new TestSuite(
All Tests);
suite.addTestSuite(TestOne.class);
suite.addTestSuite(TestTwo.class);
return suite;
}

}

Then in the project using the test-jar dependency: 
create a TestCase: 

package org.melati.example.contacts;

import org.melati.poem.AllExportedTests;

import junit.framework.Test;
import junit.framework.TestCase;

public class PoemTest extends TestCase {

public static Test suite() {
return AllExportedTests.suite();
}
}


Now the tests will be found.


 There should be a way to run unit tests from a dependency jar.
 --

 Key: SUREFIRE-569
 URL: http://jira.codehaus.org/browse/SUREFIRE-569
 Project: Maven Surefire
  Issue Type: New Feature
  Components: Maven Surefire Plugin
Reporter: Paul Gier

 In some cases it would be useful to have a set of tests that run with various 
 dependency configurations.  One way to accomplish this would be to have a 
 single project that contains the unit tests and generates a test jar.  
 Several test configuration projects could then consume the unit tests and run 
 them with different dependency sets.  The problem is that there is no easy 
 way to run tests in a dependency jar.  The surefire plugin should have a 
 configuration to allow me to run all or a set of unit tests contained in a 
 dependency 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: (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

2010-10-13 Thread Max Andersen (JIRA)

[
http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239436#action_239436
]

Max Andersen commented on SUREFIRE-569:
---

Tim, that is correct.

But no decent tessuite just contains a few test classes, it contains hundreds
if not thousands of classes for testing. Having AllSuites for them all and
requiring users to subclass them all to ensure it actually gets run is an
unnecessary cumbersome step IMO.

There should be a way to run unit tests from a dependency jar.
--

Key: SUREFIRE-569
URL: http://jira.codehaus.org/browse/SUREFIRE-569
Project: Maven Surefire
Issue Type: New Feature
Components: Maven Surefire Plugin
Reporter: Paul Gier

In some cases it would be useful to have a set of tests that run with various
dependency configurations. One way to accomplish this would be to have a
single project that contains the unit tests and generates a test jar.
Several test configuration projects could then consume the unit tests and run
them with different dependency sets. The problem is that there is no easy
way to run tests in a dependency jar. The surefire plugin should have a
configuration to allow me to run all or a set of unit tests contained in a
dependency 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: (MJAVADOC-276) Initial builds of a multi-module project fail

2010-10-13 Thread Vincenzo Mancini (JIRA)


[ 
http://jira.codehaus.org/browse/MJAVADOC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239438#action_239438
 ] 

Vincenzo Mancini commented on MJAVADOC-276:
---

The problem is still there is not fixed. Why the issue is closed?

 Initial builds of a multi-module project fail
 -

 Key: MJAVADOC-276
 URL: http://jira.codehaus.org/browse/MJAVADOC-276
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.6.1
 Environment: Java jdk1.6.0_16, Maven 2.2.1, Windows Vista 64-bit
 Java jdk1.6.0_05, Maven 2.0.9, Windows XP 32-bit
Reporter: Anthony Whitford
Assignee: John Casey
Priority: Blocker
 Fix For: 2.7

 Attachments: bug.zip, javadoctest.zip


 I ran into a problem using Maven Javadoc Plugin 2.6.1 right after I 
 released...  I went from version 1.15 to 1.16-SNAPSHOT, and my 1.16-SNAPSHOT 
 build failed ({{mvn clean install site}}) because Javadoc fails when run from 
 the top-level parent.  When it is building _module A_, the javadoc complains 
 that _module B_ and _module C_ are missing -- of course they are, they 
 haven't been built yet.  Note that running {{mvn clean install}} from _module 
 A_ works fine -- the behavior is limited to running from the top-level parent 
 -- AND, if you run a {{mvn install}} for _module B_ and _module C_, then you 
 have given it what it needs and so you won't see the error.
 The attached example exhibits the problem.  It was created from the 
 _j2ee-simple_ archetype -- I only added the explicit javadoc plugin 
 declaration to the top level pom to control the version being used.  To 
 recreate the problem, unzip and simply:  {{mvn clean install site}}.  You 
 will get an error message like:
 {noformat}
 [INFO] Unable to find resource 'root.project.projects:logging:jar:1.0' in 
 repository central (http://repo1.maven.org/maven2)
 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Failed to resolve artifact.
 Missing:
 --
 1) root.project.projects:logging:jar:1.0
   Try downloading the file manually from the project website.
   Then, install it using the command:
   mvn install:install-file -DgroupId=root.project.projects 
 -DartifactId=logging -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
   Alternatively, if you host your own repository you can deploy the file 
 there:
   mvn deploy:deploy-file -DgroupId=root.project.projects 
 -DartifactId=logging -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file 
 -Durl=[url] -DrepositoryId=
 [id]
   Path to dependency:
 1) root.project:primary-source:jar:1.0
 2) root.project.projects:logging:jar:1.0
 --
 1 required artifact is missing.
 for artifact:
   root.project:primary-source:jar:1.0
 from the specified remote repositories:
   central (http://repo1.maven.org/maven2)
 {noformat}
 As you can see, it seems to think that a submodule (in this case 
 {{root.project.projects:logging:jar:1.0}}) is necessary to build the javadoc 
 for the project...  Since this is the first time that this is being built, 
 the submodule does not exist (yet).
 I have replicated this problem on two different computing environments, so 
 I'm convinced that the Maven version is not relevant.
 (It is unclear to me if this problem also existed with Javadoc 2.6, but I 
 don't think so.)

-- 
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: (MJAVADOC-275) Creation of Javadoc attachments fails in multi-module project where modules have never been installed/deployed

2010-10-13 Thread Vincenzo Mancini (JIRA)


[ 
http://jira.codehaus.org/browse/MJAVADOC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239439#action_239439
 ] 

Vincenzo Mancini commented on MJAVADOC-275:
---

The problem is still not fixed. Why the issue is closed?

 Creation of Javadoc attachments fails in multi-module project where modules 
 have never been installed/deployed
 --

 Key: MJAVADOC-275
 URL: http://jira.codehaus.org/browse/MJAVADOC-275
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.6.1
Reporter: Benjamin Bentmann
Assignee: John Casey
Priority: Critical
 Fix For: 2.7

 Attachments: MJAVADOC-275.zip


 Running the commands
 {noformat}
 mvn clean
 mvn verify
 {noformat}
 will fail on the attached demo project with
 {noformat}
 [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
   has not be previously called for the project: 
 'org.apache.maven.its.javadoc:mod-b:jar:0.1'.
   Trying to invoke it...
 [ERROR] MavenInvocationException: Error when invoking Maven, consult the 
 invoker log file:
   M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] MavenReportException: Error while creating archive:
   Error when invoking Maven, consult the invoker log file: 
   M:\MJAVADOC\mod-a\target\invoker\maven-javadoc-plugin625147587.txt
 {noformat}
 The command {{mvn clean verify}} as usually used during releases will also 
 fail, but starts working after repeated invocations. 

-- 
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: (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

2010-10-13 Thread Tim Pizey (JIRA)

[
http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239441#action_239441
]

Tim Pizey commented on SUREFIRE-569:

The inheriting test suite can extend TestSuite or TestCase (or implement Test
itself), but the suite() providing class should not extend either, or it too
will be discovered my the Maven Surefire plugin and your tests will be run
twice.

There should be a way to run unit tests from a dependency jar.
--

Key: SUREFIRE-569
URL: http://jira.codehaus.org/browse/SUREFIRE-569
Project: Maven Surefire
Issue Type: New Feature
Components: Maven Surefire Plugin
Reporter: Paul Gier

[jira] Commented: (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

2010-10-13 Thread Tim Pizey (JIRA)

[
http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239442#action_239442
]

Tim Pizey commented on SUREFIRE-569:

@Max Andersen completely agree, I am amazed, in the light of
http://maven.apache.org/guides/mini/guide-attached-tests.html at the existence
of this bug.

I jarred my tests in 2008, assuming that this was the expected use case, then
blocked until now.

I do not want to have to manually maintain the test suite, but that seems to be
the only currently available mechanism.

There should be a way to run unit tests from a dependency jar.
--

Key: SUREFIRE-569
URL: http://jira.codehaus.org/browse/SUREFIRE-569
Project: Maven Surefire
Issue Type: New Feature
Components: Maven Surefire Plugin
Reporter: Paul Gier

[jira] Commented: (MASSEMBLY-510) leading period ('.') added to directory names

2010-10-13 Thread KP (JIRA)


[ 
http://jira.codehaus.org/browse/MASSEMBLY-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=239446#action_239446
 ] 

KP commented on MASSEMBLY-510:
--

@John Casey: Yup, I just tried beta-4 and beta-5 and the result is the same.

 leading period ('.') added to directory names
 -

 Key: MASSEMBLY-510
 URL: http://jira.codehaus.org/browse/MASSEMBLY-510
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.2
 Environment: Windows XP, SP3
 Maven 2.2.1
 Maven Assembly 2.2
Reporter: KP
 Attachments: dist.xml, pom.xml


 $ cat dist.xml
 assembly 
 xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
  http://maven.apache.org/xsd/assembly-1.1.0.xsd;
   iddist/id
   formats
 formatzip/format
   /formats
   
   
   fileSets
  fileSet
 directory${project.basedir}/../paper/directory
  /fileSet
  fileSet
 directory${project.basedir}/../boots/directory
  /fileSet
   /fileSets
 
 /assembly
 $ mvn clean assembly:assembly
 [INFO] Scanning for projects...
 [INFO] 
 
 [INFO] Building oracle-sql-assembly
 [INFO]task-segment: [clean]
 [INFO] 
 
 [INFO] [clean:clean {execution: default-clean}]
 [INFO] Deleting directory F:\test-assembly\target
 [INFO] 
 
 [INFO] Building oracle-sql-assembly
 [INFO]task-segment: [assembly:assembly] (aggregator-style)
 [INFO] 
 
 [INFO] Preparing assembly:assembly
 [INFO] 
 
 [INFO] Building oracle-sql-assembly
 [INFO] 
 
 [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
 [INFO] [assembly:assembly {execution: default-cli}]
 [INFO] Reading assembly descriptor: src/main/assembly/dist.xml
 [INFO] Building zip: 
 F:\test-assembly\target\test-assembly-3.1-SNAPSHOT-dist.zip
 [INFO] 
 
 [INFO] BUILD SUCCESSFUL
 [INFO] 
 
 [INFO] Total time: 2 seconds
 [INFO] Finished at: Mon Oct 11 15:34:37 EDT 2010
 [INFO] Final Memory: 18M/45M
 [INFO] 
 
 $ unzip -l target/test-assembly-dist.zip 
 Archive:  target/test-assembly-dist.zip
   Length  DateTimeName
 -  -- -   
 0  10-11-2010 15:34   test-assembly/
 0  10-11-2010 15:27   test-assembly/.paper/
 0  10-11-2010 15:27   test-assembly/.paper/random.txt
 0  10-11-2010 15:27   test-assembly/.boots/
 0  10-11-2010 15:27   test-assembly/.boots/boots.txt
 - ---
 0 5 files
 Do you notice the '.paper' and '.boots' directories?  It should just be 
 'paper' and 'boots', if I'm understanding it correctly.
 I tried other versions of the plugin (e.g., beta-4), I tried removing 
 ${project.basedir}/.
 No go. :(
 P.S. If someone points me in the right direction, like a class name, I'll 
 write a test case.

-- 
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-4863) Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. Getting ClasCastException.

2010-10-13 Thread Bodhayan Chakraborty (JIRA)

Failed to execute goal org.codehaus.groovy.maven:gmaven-plugin:1.0:execute. 
Getting ClasCastException.
--

 Key: MNG-4863
 URL: http://jira.codehaus.org/browse/MNG-4863
 Project: Maven 2  3
  Issue Type: Bug
  Components: Plugins and Lifecycle
Affects Versions: 3.0
 Environment: Windows XP, Jdk 1.6.0_20
Reporter: Bodhayan Chakraborty


Hi,

I am getting the below error after I upgrade Maven 2.2.1 to Maven 3.0. 

...
[ERROR] Failed to execute goal 
org.codehaus.groovy.maven:gmaven-plugin:1.0:execute (set-bastion-credentials) 
on project esb-parent-pom: java.lang.ClassCastException: script1286984516651 
cannot be cast to groovy.lang.GroovyObject - [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
...

This is the plugin that I am using.

plugin
groupIdorg.codehaus.groovy.maven/groupId
artifactIdgmaven-plugin/artifactId


/plugin

But if I change the plugin like below, it is working. 

plugin
groupIdorg.codehaus.gmaven/groupId
artifactIdgmaven-plugin/artifactId
version1.3/version


/plugin

Is it mandatory to change the Gmaven plugin if I upgrade from maven 2.2.1 to 
3.0?

Please let me know,

Thanks,
Bodhayan.

-- 
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

41 matches

Mail list logo