[jira] Created: (CONTINUUM-1253) Allow to deploy artifact without timestamps

2007-04-24 Thread Damian Golda (JIRA) 
Allow to deploy artifact without timestamps
---

 Key: CONTINUUM-1253
 URL: http://jira.codehaus.org/browse/CONTINUUM-1253
 Project: Continuum
  Issue Type: New Feature
  Components: Core system, Integration - Maven 2, Web - UI
Affects Versions: 1.0.3
Reporter: Damian Golda


In our organisation we don't use unique names of jars in repository. So we have 
set uniqueVersion to false in pom.xml:



  maven2-repo
  Maven2 Repository
  file://${repoPath}
  false

  

And it works while running mvn from command line.

But when we build project from continuum, it deploys built jar into Deployment 
Repository Directory and unfortunately always adds timestamps to filename.

The reason is that in 
org.apache.maven.continuum.core.action.DeployArtifactContinuumAction is 
specified "true" as uniqueVersion parameter of 
ArtifactRepositoryFactory.createDeploymentArtifactRepository method:

 ArtifactRepository deploymentRepository =

artifactRepositoryFactory.createDeploymentArtifactRepository( 
"deployment-repository", location,

  repositoryLayout, true );

PLEASE, change it, and allow to set required behavior by admin in Edit 
Configuration page. 

We have strange problems with hundreds of fat jars in repository, caused by 
unique names of them.

I think it's needed to:
-add to Configuration new field, for example DeployWithUniqueVersion 
-change DeployArtifactContinuumAction, to uset that field instead of hard-coded 
true
-add new field to EditContinuumConfiguration.vm 
-add some code to ConfigurationAction and InitializationChecker

-- 
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: (SUREFIRE-58) Not compatible with TestNG 5.4: InstantiationException: org.testng.internal.annotations.JDK15AnnotationFinder

2006-12-14 Thread Damian Golda (JIRA) 
Not compatible with TestNG 5.4: InstantiationException: 
org.testng.internal.annotations.JDK15AnnotationFinder
-

 Key: SUREFIRE-58
 URL: http://jira.codehaus.org/browse/SUREFIRE-58
 Project: surefire
  Issue Type: Bug
Affects Versions: 2.2
 Environment: JDK  1.5.0_09
mvn 2.0.4
surefire-api:jar:2.0
surefire-testng:jar:2.0


maven-surefire-plugin
2.2
  

 
  org.testng
  testng
  5.4
  jdk15
  test

Reporter: Damian Golda
Priority: Minor


While running test using mvn and TestNG 5.4 there surefire reports exception:

org.apache.maven.surefire.booter.SurefireExecutionException: 
org.testng.internal.annotations.JDK15AnnotationFinder; nes
ed exception is java.lang.InstantiationException: 
org.testng.internal.annotations.JDK15AnnotationFinder; nested excepti
n is org.apache.maven.surefire.testset.TestSetFailedException: 
org.testng.internal.annotations.JDK15AnnotationFinder; n
sted exception is java.lang.InstantiationException: 
org.testng.internal.annotations.JDK15AnnotationFinder
org.apache.maven.surefire.testset.TestSetFailedException: 
org.testng.internal.annotations.JDK15AnnotationFinder; nested
exception is java.lang.InstantiationException: 
org.testng.internal.annotations.JDK15AnnotationFinder
java.lang.InstantiationException: 
org.testng.internal.annotations.JDK15AnnotationFinder
at java.lang.Class.newInstance0(Class.java:335)
at java.lang.Class.newInstance(Class.java:303)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.(TestNGDirectoryTestSuite.java:86)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at 
org.apache.maven.surefire.Surefire.instantiateObject(Surefire.java:216)
at 
org.apache.maven.surefire.Surefire.instantiateSuite(Surefire.java:243)
at 
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:145)
at org.apache.maven.surefire.Surefire.run(Surefire.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)


I suppose that the reason is that in TestNG 5.4 (and 5.3) constructor for 
JDK15AnnotationFinder has an argument:

public JDK15AnnotationFinder(IAnnotationTransformer transformer) 

and there is no default constructor.

I found that there is only one implementation of IAnnotationTransformer - 
DefaultAnnotationTransformer which fortunatly has default constructor.
So I it can be changed from 
new JDK15AnnotationFinder() 
to 
new JDK15AnnotationFinder(new DefaultAnnotationTransformer())

So instead of class.newInstance should be used:
Constructor c = Class.getConstructor(IAnnotationTransformer.class);
DefaultAnnotationTransformer daf = new DefaultAnnotationTransformer()
 c.newInstance(daf);

-- 
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: (SUREFIRE-59) Not compatible with TestNG 5.2: java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V

2006-12-14 Thread Damian Golda (JIRA) 
Not compatible with TestNG 5.2:  java.lang.NoSuchMethodError: 
org.testng.xml.XmlSuite.setParallel(Z)V
-

 Key: SUREFIRE-59
 URL: http://jira.codehaus.org/browse/SUREFIRE-59
 Project: surefire
  Issue Type: Improvement
  Components: TestNG support
 Environment:   
maven-surefire-plugin
2.2



  org.testng
  testng
  5.2
  jdk15
  test


Reporter: Damian Golda


I have project with dependency to testng and surefire plugin as in Environment.
I run tests and get exception:

org.apache.maven.surefire.booter.SurefireExecutionException: 
org.testng.xml.XmlSuite.setParallel(Z)V; nested exception i
s java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V
java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:135)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)

Please, correct surefire to be compatible with new testng.

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