Maven/Junit: printing test failure/error stack trace to stdout
Is it possible to print out the stack trace for tests that fail or raise an error. I would like more details that a failure/error count. Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unit test failing (using static method from different project)
I'm facing a weird error. I have the following projects with the dependencies shown (a - b means a depends on b) storagemanager-util stindex-util stindex-storagemanager I have made a unit test in the storagemanager project that uses a public static method in a class located in the util project. When I compile and run the test in Eclipse it works fine. Under maven, the source and unit test files compile fine, but if I run the tests the test cases invoking the method fail. If I copy the static method into the unit test itself, then the test passes. Does anyone know what's going on? I don't want to duplicate utility methods in *all* my unit testcases because of this... Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unit test failing (using static method from different project)
Erik Husby wrote: Omair-Inam Abdul-Matin wrote: I'm facing a weird error. I have the following projects with the dependencies shown (a - b means a depends on b) storagemanager-util stindex-util stindex-storagemanager I have made a unit test in the storagemanager project that uses a public static method in a class located in the util project. When I compile and run the test in Eclipse it works fine. Under maven, the source and unit test files compile fine, but if I run the tests the test cases invoking the method fail. If I copy the static method into the unit test itself, then the test passes. Does anyone know what's going on? I don't want to duplicate utility methods in *all* my unit testcases because of this... Sounds like a classpath problem to me. Is the jar containing the class with the static method in your list of dependencies for the project whose tests fail? Yes... I can run reactor and based on the inter-project dependencies it builds the individual subprojects correctly on the dependency tree (i.e. in the order util, storagemanager, stindex) In the pom for the storagemanager I have defined the util project as a dependency. What is the exact error message you get? This is a portion of the test output given by maven test:test: [junit] Running storagemanager.CommonsLRUBufferTest [junit] Tests run: 7, Failures: 0, Errors: 3, Time elapsed: 1.402 sec [junit] [ERROR] TEST storagemanager.CommonsLRUBufferTest FAILED [junit] Running storagemanager.CommonsLRUBufferWithAppendTest [junit] Tests run: 5, Failures: 0, Errors: 4, Time elapsed: 1.041 sec [junit] [ERROR] TEST storagemanager.CommonsLRUBufferWithAppendTest FAILED [junit] Running storagemanager.DiskStorageManagerTest [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 1.392 sec [junit] Running storagemanager.MemoryStorageManagerTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.61 sec [junit] Running storagemanager.TIntVirtualHashtableTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.321 sec [junit] Running storagemanager.TLRUAppendBufferTest [junit] Tests run: 5, Failures: 0, Errors: 4, Time elapsed: 1.171 sec [junit] [ERROR] TEST storagemanager.TLRUAppendBufferTest FAILED [junit] Running storagemanager.TLRUBufferTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 2.062 sec [junit] Running storagemanager.TObjectVirtualHashtableTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 2.734 sec [junit] Running storagemanager.TRandomEvictionsBufferTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.402 sec The errors occur in those tests that invoke the static method... Again I reiterate... Dependencies have been set correctly... because otherwise the project would simply not compile... However I can't tell why the unit tests are giving an error... Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Reactor multi-project: master build not working
I'm using the following project structure
stindex/stindex/ (subproject)
stindex/storagemanager/ (subproject)
stindex/stindex-build/ (subproject)
I have a clean-all goal in the stindex-build defined as follows:
project
xmlns:m=jelly:maven
xmlns:j=jelly:core
goal name=clean-all
m:reactor
basedir=${basedir}/..
includes=*/project.xml
excludes=stindex-build/project.xml
goals=clean
banner=Cleaning
ignoreFailures=false
/
/goal
...
/project
This mimics closely the maven.xml file in the commons-build directory of
the jakarta commons. Now when I try to run maven clean-all from
stindex/stindex-build I get the output shown below...
C:\eclipse\workspace\stindex-new\stindex-buildmaven clean-all
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc4
Starting the reactor...
BUILD FAILED
File.. C:\eclipse\workspace\stindex-new\stindex-build\maven.xml
Element... m:reactor
Line.. 12
Column 11
Error parsing project.xml 'C:\eclipse\workspace\stindex-new\project.xml'
Total time: 2 seconds
Finished at: Sun Jul 11 11:21:37 EDT 2004
I don't understand why maven requires a project.xml file in the parent
directory. Browsing through the jakarta commons repository I did not
find a project.xml file in the parent directory of to the build
directory (http://cvs.apache.org/viewcvs.cgi/jakarta-commons/)... What
am I doing wrong...?
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Reactor multi-project: master build not working
I'm using the following project structure
stindex/stindex/ (subproject)
stindex/storagemanager/ (subproject)
stindex/stindex-build/ (subproject)
I have a clean-all goal in the stindex-build defined as follows:
project
xmlns:m=jelly:maven
xmlns:j=jelly:core
goal name=clean-all
m:reactor
basedir=${basedir}/..
includes=*/project.xml
excludes=stindex-build/project.xml
goals=clean
banner=Cleaning
ignoreFailures=false
/
/goal
...
/project
This mimics closely the maven.xml file in the commons-build directory of
the jakarta commons. Now when I try to run maven clean-all from
stindex/stindex-build I get the output shown below...
C:\eclipse\workspace\stindex-new\stindex-buildmaven clean-all
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc4
Starting the reactor...
BUILD FAILED
File.. C:\eclipse\workspace\stindex-new\stindex-build\maven.xml
Element... m:reactor
Line.. 12
Column 11
Error parsing project.xml 'C:\eclipse\workspace\stindex-new\project.xml'
Total time: 2 seconds
Finished at: Sun Jul 11 11:21:37 EDT 2004
I don't understand why maven requires a project.xml file in the parent
directory. Browsing through the jakarta commons repository I did not
find a project.xml file in the parent directory of to the build
directory (http://cvs.apache.org/viewcvs.cgi/jakarta-commons/)... What
am I doing wrong...?
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactor multi-project: master build not working
Never mind...
My subprojects were trying to extend a non-existent pom in stindex which
was causing the error.
Omair
Omair-Inam Abdul-Matin wrote:
I'm using the following project structure
stindex/stindex/ (subproject)
stindex/storagemanager/ (subproject)
stindex/stindex-build/ (subproject)
I have a clean-all goal in the stindex-build defined as follows:
project
xmlns:m=jelly:maven
xmlns:j=jelly:core
goal name=clean-all
m:reactor
basedir=${basedir}/..
includes=*/project.xml
excludes=stindex-build/project.xml
goals=clean
banner=Cleaning
ignoreFailures=false
/
/goal
...
/project
This mimics closely the maven.xml file in the commons-build directory of
the jakarta commons. Now when I try to run maven clean-all from
stindex/stindex-build I get the output shown below...
C:\eclipse\workspace\stindex-new\stindex-buildmaven clean-all
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc4
Starting the reactor...
BUILD FAILED
File.. C:\eclipse\workspace\stindex-new\stindex-build\maven.xml
Element... m:reactor
Line.. 12
Column 11
Error parsing project.xml 'C:\eclipse\workspace\stindex-new\project.xml'
Total time: 2 seconds
Finished at: Sun Jul 11 11:21:37 EDT 2004
I don't understand why maven requires a project.xml file in the parent
directory. Browsing through the jakarta commons repository I did not
find a project.xml file in the parent directory of to the build
directory (http://cvs.apache.org/viewcvs.cgi/jakarta-commons/)... What
am I doing wrong...?
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Reactor: continuing a goal despite unresolved dependencies
I have a multi-project stindex consisting of two subprojects,
stindex/stindex and stindex/storagemanager
stindex depends on storagemanager
Now I have a clean-all goal as follows:
project
xmlns:m=jelly:maven
xmlns:j=jelly:core
goal name=clean-all
m:reactor
basedir=${basedir}/..
includes=*/project.xml
excludes=stindex-build/project.xml
goals=clean
banner=Cleaning
ignoreFailures=false
/
/goal
...
/project
If I run clean-all with the storagemanager jar not in the repository
then maven fails:
C:\eclipse\workspace\stindex-new\stindex-buildmaven clean-all
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc4
Starting the reactor...
Our processing order:
A storagemanager library
A cool spatio-temporal index library
+
| Cleaning A storagemanager library
| Memory: 2M/3M
+
build:start:
clean-all:
build:start:
clean:clean:
[delete] Deleting directory
C:\eclipse\workspace\stindex-new\storagemanager\target
+
| Cleaning A cool spatio-temporal index library
| Memory: 3M/4M
+
Attempting to download storagemanager-0.1-b4.jar.
WARNING: Failed to download storagemanager-0.1-b4.jar.
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Sun Jul 11 11:51:28 EDT 2004
I'd like in this case to be able to either:
1. clean the project dirs even though the storagemanager jar does not
exist (since in this case stindex doesn't *really* depend on storagemanager)
2. if that's not possible then to have reactor build and install the
storagemanager jar when it finds that the jar does not exist then clean
out the stindex project.
Is that possible?
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Reactor source
I believe this question was asked some time ago. However the source code seems to have moved since then. Does anyone know where the reactor source is in the repository? (I tried Try src/java/org/apache/maven/jelly/tags/maven/ReactorTag.java... the stuff's been moved to the attic) Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactor: tests failing (working dir set to master proj dir not child proj dir)
Dion Gillard wrote:
Set the user.home system property in the child subproject?
On Fri, 09 Jul 2004 23:38:58 -0400, Omair-Inam Abdul-Matin
[EMAIL PROTECTED] wrote:
I'm using JUnit to run some regression tests that need to read in
configuration and data files. For this it is necessary that the working
directory be the same as the project directory. Recently the project
was subdivided into a master project and child subprojects. Now when I
try to run unit tests by invoking the master build target, the tests
fail because apparently the working directory is the directory of the
master project not the current child project. I believe this topic has
been brought up in a previous post but I was not able to find the
solution to the problem.
Can someone please nudge me in the correction direction?
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I don't think that'll work. I believe the solution is something along
the lines of the following:
goal name=printenv-test-all
echo- MASTER PROJECT ENV -/echo
attainGoal name=printenv/
!-- only collect the project names --
m:reactor basedir=${basedir}
includes=*/project.xml
goals=printenv
banner=Building
collectOnly=false
postProcessing=true
ignoreFailures=false
/
j:forEach var=reactorProject items=${reactorProjects}
!-- set the basedir value here for each project and then
attain the desired goal --
/j:forEach
/goal
I was surprised why the reactor doc doesn't mention the fact that any
instance var of the Project class can be accessed (e.g.
${reactorProject.groupId}) I had to actually go thru the source and
then find the instance vars.
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reactor: tests failing (working dir set to master proj dir not child proj dir)
Jason van Zyl wrote:
On Sat, 2004-07-10 at 13:08, Omair-Inam Abdul-Matin wrote:
I've tried the following and my unit tests still fail because the
working directory seems to be the directory of the master project.
There is no way to reliably set the working directory in Java. To make
your tests reactor-able you must reference resources using the basedir
system property that is made available in tests by the junit plugin.
So the general pattern is:
public class MyTest extends TestCase
{
private String basedir;
protected void setUp()
{
basedir = System.getProperty( basedir );
}
public void testThatUsesAResourceFromTheFileSystem()
{
File resource = new File( basedir, src/test/resources/MyTestResource.txt );
// do you stuff with the file system resource.
}
}
Thanks... that's exactly what I was looking for.. I didn't know how to
fetch maven-defined properties in a java file.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Reactor: tests failing (working dir set to master proj dir not child proj dir)
I'm using JUnit to run some regression tests that need to read in configuration and data files. For this it is necessary that the working directory be the same as the project directory. Recently the project was subdivided into a master project and child subprojects. Now when I try to run unit tests by invoking the master build target, the tests fail because apparently the working directory is the directory of the master project not the current child project. I believe this topic has been brought up in a previous post but I was not able to find the solution to the problem. Can someone please nudge me in the correction direction? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimal project.xml for upload requests
Carlos Sanchez wrote: Hi, What are the minimal requirements of an upload request project.xml for a project not using maven? Only pomVersion, id, name, groupId and dependencies? Thanks Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net This question was asked in an earlier thread. Do a search for ibiblio uploads question on the newsgroup. I got the following answer quote If the project builds with maven the POM you provide should be fine. If you don't use maven then it would at least be nice to have the groupId artifactId name currentVersion dependencies /quote Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mevenide: Dialog box q (in UI)
In many of the tabs introduced by Mevenide. E.g. the dependencies tab, it is possible to add, remove dependencies as well as change the order. However when I try to add a new dependency, I get a generic jar file ([artifactId]-[version].jar) which I cannot edit in the same view. I'm assuming that this is expected behavior and that right now it is only possible to edit this in directly in the source. Could someone shed some light on this? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WOW - ultra fast plugin download
Having attempted to download AJDT 1.1.10 yesterday 3 times after failing twice I managed to use the update site to download it. With a T1 connection I was getting a measly speed of below 5 KB/sec (I reckon). I was pleasantly surprised when the Mevenide plugin, which is larger than AJDT I think, downloaded faster than any other plugin I've seen. 2 points for that... :) I was really impressed with the UI design when I checked out the beta version put up by Gilles for M8. I'm sure there's good stuff here. Omair Rafal Krzewski wrote: Maczka Michal wrote: Yeap! You right. I am almost sure that I read somewhere taht m9 = rc1. Almost right. M9 == RC0 Rafal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mevenide: Dialog box q (in UI)
Gilles Dodinet wrote: Omair-Inam Abdul-Matin wrote: In many of the tabs introduced by Mevenide. E.g. the dependencies tab, it is possible to add, remove dependencies as well as change the order. However when I try to add a new dependency, I get a generic jar file ([artifactId]-[version].jar) which I cannot edit in the same view. I'm assuming that this is expected behavior and that right now it is only possible to edit this in directly in the source. Could someone shed some light on this? Omair, actually you can edit the values in the properties sheet view. i guess we should add a button to open the properties view automatically - or to bring it to the front on double-click. regards, -- gd Oh, I didn't even know that existed... So, I was browsing and it seems that when I open maven.xml I can select goals to launch but through project.xml the outline view does not display goals. This I guess is the expected behavior. I'm having a bit of an issue with the plugin. I just installed 3.0RC1 and I was having troubles getting a different plugin to work (Clover) so I deleted it's directory from the plugins directory. Now when I open the preferences window instead of seeing Maven in the options I see the following: %MavenMenu.label Actually this has happened with another plugin as well, and the other plugin (Log4E in case you were wondering) has also decided to do the same thing (so instead of Log4E I see in its place %pluginName) Do you know how I can sort this out? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mevenide wiki : editable? (or not?)
Just wondering why the mevenide wiki is not editable? Not that I've ever wikied. Just a thought. Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Min acceptable POM for ibiblio upload (was Re: ibiblio uploads question)
Jason van Zyl wrote: On Thu, 2004-05-27 at 09:36, Omair-Inam Abdul-Matin wrote: Hi, I've made a bunch of upload requests to ibiblio with detailed enough POMs that allow the libs to compile and I'm just wondering what specific requirements must the POM satisfy. Are you talking about a project that doesn't use maven as its build tool? One that doesn't use maven as its build tool. If the project builds with maven the POM you provide should be fine. If you don't use maven then it would at least be nice to have the groupId artifactId name currentVersion dependencies whoops I didn't put groupId in the last few requests that I made. Actually wait... I think you're referring to the groupId and artifactId that are successor elements of the dependencies element. The groupId element that exists at the top-level actually isn't even present in the Getting Started-Integrate doc. So basically if I understand correctly the min you'd like is a pom in the following form: project nameProject name/name dependencies dependency groupIdmockobjects/groupId artifactIdmockobjects-core/artifactId version0.0.1/version /dependency ... /dependencies /project If you think that's clear, I think it may be helpful to put it on the upload instructions I will add to the upload instructions. Obviously transitive dependencies support requires that I specify all dependencies of a library. But, does the POM actually have to be able to compile the project? Yes, one would hope this is the case. Currently I am assuming the POM is intact and is correct. I do limited checking of the POM. For one of the projects I had to put a sourceModification element in to make it compile... If you are using maven to build then give us the POM you're using. That's what we really want. I'm probably always going to use Maven now... Who needs ant when you can write just one file and get away with it. My problem was really the 3rd party libraries that don't use maven as a build tool. Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mevenide wiki link broken
I was searching for threads on Mevenide and managed to find one that links to the build instructions for Eclipse. That works fine. However from the main mevenide page the link to the wiki is broken. Could one of the committer fix it please? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mevenide working ... ?
Gilles Dodinet wrote: Omair-Inam Abdul-Matin wrote: I was searching for threads on Mevenide and managed to find one that links to the build instructions for Eclipse. That works fine. However from the main mevenide page the link to the wiki is broken. Could one of the committer fix it please? hi- this is already fixed in cvs. however site has not been updated since then. it will with the next release which has been a bit delayed but should drop in the coming days. in any case heres the link : http://docs.codehaus.org/display/MEVENIDE/Home regards, -- gd Is mevenide in working condition right now...? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven error building mevenide
Gilles Dodinet wrote: Omair-Inam Abdul-Matin wrote: I followed the link provided by Gilles and am trying to build the eclipse plugin. All goes well until the final step. I chang into the mevenide-master directory and issue the maven mevenide-eclipse:build command. Maven chugs along for a while, then chokes and dies :( I have attached the final few pages of output given by maven. Can anyone guide me as to what the problem is? Note that my setup environment is correctly set up (I have ECLIPSE_HOME set to point to my Eclipse installation directory) Omair, problem is that youve built against M9. Oh (:-0) i havent yet committed the changes i made for M9. i just committed changes so it will at least compile, however M9 seems to _really_ break runtime.. if you're interested i can upload a M8 compatible update site. -- gd I would definitely be interested in an M8 compatible website. So if I understand correctly this would allow me to go through the Help-Software Updates-Find and Install option in Eclipse 3.0M8 to install the plugin... right? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin built...
Omair-Inam Abdul-Matin wrote: Gilles Dodinet wrote: Omair-Inam Abdul-Matin wrote: I followed the link provided by Gilles and am trying to build the eclipse plugin. All goes well until the final step. I chang into the mevenide-master directory and issue the maven mevenide-eclipse:build command. Maven chugs along for a while, then chokes and dies :( I have attached the final few pages of output given by maven. Can anyone guide me as to what the problem is? Note that my setup environment is correctly set up (I have ECLIPSE_HOME set to point to my Eclipse installation directory) Omair, problem is that youve built against M9. Oh (:-0) i havent yet committed the changes i made for M9. i just committed changes so it will at least compile, however M9 seems to _really_ break runtime.. if you're interested i can upload a M8 compatible update site. -- gd I would definitely be interested in an M8 compatible website. So if I understand correctly this would allow me to go through the Help-Software Updates-Find and Install option in Eclipse 3.0M8 to install the plugin... right? Omair I managed to build the plugin against 3.0M8. Now what is the configuration directory mentioned in the wiki that I have to delete. By that are you referring to the /path/to/my/workspace/.metadata directory? If not then which directory? Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dumb question: config dir = config dir
Omair-Inam Abdul-Matin wrote: Omair-Inam Abdul-Matin wrote: Gilles Dodinet wrote: Omair-Inam Abdul-Matin wrote: I followed the link provided by Gilles and am trying to build the eclipse plugin. All goes well until the final step. I chang into the mevenide-master directory and issue the maven mevenide-eclipse:build command. Maven chugs along for a while, then chokes and dies :( I have attached the final few pages of output given by maven. Can anyone guide me as to what the problem is? Note that my setup environment is correctly set up (I have ECLIPSE_HOME set to point to my Eclipse installation directory) Omair, problem is that youve built against M9. Oh (:-0) i havent yet committed the changes i made for M9. i just committed changes so it will at least compile, however M9 seems to _really_ break runtime.. if you're interested i can upload a M8 compatible update site. -- gd I would definitely be interested in an M8 compatible website. So if I understand correctly this would allow me to go through the Help-Software Updates-Find and Install option in Eclipse 3.0M8 to install the plugin... right? Omair I managed to build the plugin against 3.0M8. Now what is the configuration directory mentioned in the wiki that I have to delete. By that are you referring to the /path/to/my/workspace/.metadata directory? If not then which directory? Omair I see the directory. Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
subversion repo connection string: (again I know)
There was a thread regarding Subversion and a proper connection string for it some time ago. I'm still not sure about the form of the final connection string that pleases Maven. When I try to build my project I get the following error BUILD FAILED File.. C:\Documents and Settings\oiinamul\.maven\plugins\maven-xdoc-plugin-1 .7.1\plugin.jelly Element... velocity:merge Line.. 491 Column 13 Invocation of method 'getScmType' in class org.apache.maven.project.Repository threw exception class java.lang.IllegalArgumentException : repository connection string contains less than six tokens Total time: 1 minutes 45 seconds Finished at: Tue May 25 12:06:25 EDT 2004 Alas... maven still insists on 6 tokens it seems. So if I have the following, how do I turn it into 6 acceptable tokens: scm:svn:http://my-server-name/svn/my-project-name/trunk I've tried scm:svn:http://my-server-name:svn:project-name/trunk didn't work... Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: subversion repo connection string: (again I know)
The relevant snippet from my project.properties file is given below: # --- # # C H A N G E L O G P R O P E R T I E S # # --- maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory Omair Emmanuel Venisse wrote: Do you have setup the maven.changelog.factory property? - Original Message - From: Omair-Inam Abdul-Matin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 6:09 PM Subject: subversion repo connection string: (again I know) There was a thread regarding Subversion and a proper connection string for it some time ago. I'm still not sure about the form of the final connection string that pleases Maven. When I try to build my project I get the following error BUILD FAILED File.. C:\Documents and Settings\oiinamul\.maven\plugins\maven-xdoc-plugin-1 .7.1\plugin.jelly Element... velocity:merge Line.. 491 Column 13 Invocation of method 'getScmType' in class org.apache.maven.project.Repository threw exception class java.lang.IllegalArgumentException : repository connection string contains less than six tokens Total time: 1 minutes 45 seconds Finished at: Tue May 25 12:06:25 EDT 2004 Alas... maven still insists on 6 tokens it seems. So if I have the following, how do I turn it into 6 acceptable tokens: scm:svn:http://my-server-name/svn/my-project-name/trunk I've tried scm:svn:http://my-server-name:svn:project-name/trunk didn't work... Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: subversion repo connection string: (again I know)
Yes, that change worked. I still get a proper changelog (since it doesn't use the repo string) and the url for repository access (Project Info-Source Repository). Until proper SVN support is added to the SCM plugin I guess this workaround will have to do. Omair [EMAIL PROTECTED] wrote: didn't the scm:svn:pserver:[pserver [EMAIL PROTECTED]:/path/to/svn:my-project-name/trunk works ? Nicolas, Omair-Inam Abdul-Matin [EMAIL PROTECTED] Envoyé par : news [EMAIL PROTECTED] 25/05/2004 18:09 Veuillez répondre à Maven Users List Pour : [EMAIL PROTECTED] cc : Objet : subversion repo connection string: (again I know) There was a thread regarding Subversion and a proper connection string for it some time ago. I'm still not sure about the form of the final connection string that pleases Maven. When I try to build my project I get the following error BUILD FAILED File.. C:\Documents and Settings\oiinamul\.maven\plugins\maven-xdoc-plugin-1 .7.1\plugin.jelly Element... velocity:merge Line.. 491 Column 13 Invocation of method 'getScmType' in class org.apache.maven.project.Repository threw exception class java.lang.IllegalArgumentException : repository connection string contains less than six tokens Total time: 1 minutes 45 seconds Finished at: Tue May 25 12:06:25 EDT 2004 Alas... maven still insists on 6 tokens it seems. So if I have the following, how do I turn it into 6 acceptable tokens: scm:svn:http://my-server-name/svn/my-project-name/trunk I've tried scm:svn:http://my-server-name:svn:project-name/trunk didn't work... Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: subversion repo connection string: (again I know)
Let me clarify. What I meant by worked was that my build process didn't fail... As Emmanuel has correctly pointed out SVN does not use the same format for a connection string as CVS. Quoting the SVN red book: - Repository URLs Subversion repositories can be accessed through many different methodson local disk, or through various network protocols. A repository location, however, is always a URL. Table 2-1 describes how different URL schemas map to the available access methods. Table 2.1. Repository Access URLs Schema Access Method file:///direct repository access (on local disk) http:// access via WebDAV protocol to Subversion-aware Apache server https://same as http://, but with SSL encryption. svn:// access via custom protocol to an svnserve server svn+ssh:// same as svn://, but through an SSH tunnel. For the most part, Subversion's URLs use the standard syntax, allowing for server names and port numbers to be specified as part of the URL. Remember that the file: access method is valid only for locations on the same server as the clientin fact, in accordance with convention, the server name portion of the URL is required to be either absent or localhost: $ svn checkout file:///path/to/repos $ svn checkout file://localhost/path/to/repos Also, users of the file: scheme on Windows platforms will need to use an unofficially standard syntax for accessing repositories that are on the same machine, but on a different drive than the client's current working drive. Either of the two following URL path syntaxes will work where X is the drive on which the repository resides: C:\ svn checkout file:///X:/path/to/repos C:\ svn checkout file:///X|/path/to/repos In the second syntax, you need to quote the URL so that the vertical bar character is not interpreted as a pipe. Note that a URL uses ordinary slashes even though the native (non-URL) form of a path on Windows uses backslashes. - For now, I'm happy with a working website :) Omair Emmanuel Venisse wrote: No svn doesn't use cvs connection string style. - Original Message - From: [EMAIL PROTECTED] To: Maven Users List [EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 6:21 PM Subject: RE: subversion repo connection string: (again I know) didn't the scm:svn:pserver:[pserver [EMAIL PROTECTED]:/path/to/svn:my-project-name/trunk works ? Nicolas, Omair-Inam Abdul-Matin [EMAIL PROTECTED] Envoy par : news [EMAIL PROTECTED] 25/05/2004 18:09 Veuillez rpondre Maven Users List Pour : [EMAIL PROTECTED] cc : Objet : subversion repo connection string: (again I know) There was a thread regarding Subversion and a proper connection string for it some time ago. I'm still not sure about the form of the final connection string that pleases Maven. When I try to build my project I get the following error BUILD FAILED File.. C:\Documents and Settings\oiinamul\.maven\plugins\maven-xdoc-plugin-1 .7.1\plugin.jelly Element... velocity:merge Line.. 491 Column 13 Invocation of method 'getScmType' in class org.apache.maven.project.Repository threw exception class java.lang.IllegalArgumentException : repository connection string contains less than six tokens Total time: 1 minutes 45 seconds Finished at: Tue May 25 12:06:25 EDT 2004 Alas... maven still insists on 6 tokens it seems. So if I have the following, how do I turn it into 6 acceptable tokens: scm:svn:http://my-server-name/svn/my-project-name/trunk I've tried scm:svn:http://my-server-name:svn:project-name/trunk didn't work... Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Upgrading to 1.0RC3 - exception thrown when listing goals
I installed Maven 1.0RC3. The first time I forgot to remove the local plugins directory and maven threw a nasty exception and quit on me. I then uninstalled it, removed the local plugin directory and reinstalled it. Now when I call maven -g, maven lists the goal but it throws the following exception first: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3 [MethodExpression] Cannot evaluate expression java.lang.reflect.InvocationTargetException 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:324) at org.apache.commons.betwixt.expression.MethodExpression.evaluate(MethodExpression.java:96) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:658) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:481) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:643) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:630) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:162) at org.apache.commons.betwixt.io.BeanWriter.write(BeanWriter.java:217) at org.apache.maven.MavenUtils.getProjectString(MavenUtils.java:421) at org.apache.maven.MavenUtils.getInterpolatedPOM(MavenUtils.java:372) at org.apache.maven.MavenUtils.getJellyProject(MavenUtils.java:349) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:472) at org.apache.maven.cli.App.main(App.java:1214) 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:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.IllegalArgumentException: repository connection string contains less than six tokens at org.apache.maven.project.Repository.splitSCMConnection(Repository.java:240) at org.apache.maven.project.Repository.getCvsModule(Repository.java:205) at org.apache.maven.project.Repository.getCvsModule(Repository.java:144) ... 33 more [MethodExpression] Cannot evaluate expression java.lang.reflect.InvocationTargetException 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:324) at org.apache.commons.betwixt.expression.MethodExpression.evaluate(MethodExpression.java:96) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:658) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:481) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:643) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:630) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at
Re: Upgrading to 1.0RC3 - exception thrown when listing goals
Never mind, Problem solved. Omair Omair-Inam Abdul-Matin wrote: I installed Maven 1.0RC3. The first time I forgot to remove the local plugins directory and maven threw a nasty exception and quit on me. I then uninstalled it, removed the local plugin directory and reinstalled it. Now when I call maven -g, maven lists the goal but it throws the following exception first: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3 [MethodExpression] Cannot evaluate expression java.lang.reflect.InvocationTargetException 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:324) at org.apache.commons.betwixt.expression.MethodExpression.evaluate(MethodExpression.java:96) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:658) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:481) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:643) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:630) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:162) at org.apache.commons.betwixt.io.BeanWriter.write(BeanWriter.java:217) at org.apache.maven.MavenUtils.getProjectString(MavenUtils.java:421) at org.apache.maven.MavenUtils.getInterpolatedPOM(MavenUtils.java:372) at org.apache.maven.MavenUtils.getJellyProject(MavenUtils.java:349) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:472) at org.apache.maven.cli.App.main(App.java:1214) 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:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: java.lang.IllegalArgumentException: repository connection string contains less than six tokens at org.apache.maven.project.Repository.splitSCMConnection(Repository.java:240) at org.apache.maven.project.Repository.getCvsModule(Repository.java:205) at org.apache.maven.project.Repository.getCvsModule(Repository.java:144) ... 33 more [MethodExpression] Cannot evaluate expression java.lang.reflect.InvocationTargetException 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:324) at org.apache.commons.betwixt.expression.MethodExpression.evaluate(MethodExpression.java:96) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:658) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:481) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:643) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeRestOfElement(AbstractBeanWriter.java:539) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:513) at org.apache.commons.betwixt.io.AbstractBeanWriter.write(AbstractBeanWriter.java:233) at org.apache.commons.betwixt.io.AbstractBeanWriter.writeContent(AbstractBeanWriter.java:630
Typo simian website: property name includetests *not* includeTests
This typo had me confused for a couple of days. The properties section lists a property called maven.simian.includeTests. I was setting this to false with no luck. Turns out it was actually maven.simian.includetests - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Property maven.simian.includes(excludes) applies only to src dir not to test
I've noticed that the maven.simian.includes(excludes) flag apply when simian is looking thru the src directory but when checking the test directory it goes back to the default **/*.java. Is it possible to include a property to modify this behavior (yes I know I should post a req to jira... that's been done too) Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing all new plugin updates ... one way
This works for me in Windows 1. Copy all the commands into Notepad and put each command on one line. 2. Open up a console window. 3. Copy/paste the commands into the console. Enjoy. I've attached the commands to this post. Omair maven plugin:download -DgroupId=maven -DartifactId=maven-test-plugin -Dversion=1.6 maven plugin:download -DgroupId=maven -DartifactId=maven-java-plugin -Dversion=1.4 maven plugin:download -DgroupId=maven -DartifactId=maven-announcement-plugin -Dversion=1.1 maven plugin:download -DgroupId=maven -DartifactId=maven-native-plugin -Dversion=1.1 maven plugin:download -DgroupId=maven -DartifactId=maven-dist-plugin -Dversion=1.5 maven plugin:download -DgroupId=maven -DartifactId=maven-ant-plugin -Dversion=1.7 maven plugin:download -DgroupId=maven -DartifactId=maven-aspectj-plugin -Dversion=3.0 maven plugin:download -DgroupId=maven -DartifactId=maven-jbuilder-plugin -Dversion=1.5 maven plugin:download -DgroupId=maven -DartifactId=maven-jbuilder-plugin -Dversion=1.5 maven plugin:download -DgroupId=maven -DartifactId=maven-checkstyle-plugin -Dversion=2.4 maven plugin:download -DgroupId=maven -DartifactId=maven-clover-plugin -Dversion=1.5 maven plugin:download -DgroupId=maven -DartifactId=maven-console-plugin -Dversion=1.1 maven plugin:download -DgroupId=maven -DartifactId=maven-javadoc-plugin -Dversion=1.5 maven plugin:download -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion=1.5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
changelog plugin - works with subversion now!!!
I installed the updated version of changelog plugin (v1.5). It seems that it works now... I get a proper changelog report I tested it with Subversion: svn, version 1.0.1 (dev build) compiled Mar 25 2004, 16:25:21 Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status of SubVersion integratrion
Emmanuel Venisse wrote: Actually, only changelog report support subversion. A full support of subversion (and others scm tools) arrive in Maven 2 Emmanuel - Original Message - From: Michael MATTOX [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 2:26 PM Subject: Status of SubVersion integratrion I'm deciding between CVS SubVersion and I'm curious what the current status of SubVersion support is in Maven. I've searched the mailing lists and it seems there were a few problems reported in February, including one that didn't have any responses. So I'm not sure if SubVersion is working properly and no one has questions or if no one is using SubVersion. Also, if anyone is using SubVersion, do the maven plugins support SubVersion? Any major plugins not support it? Michael -- This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] You've mentioned that changelog supports subversion. However I tried using the changelog plugin and it seems that the plugin cannot parse the changelog data properly, since my changelog report is empty. Browsing through other posts in the archive I noticed that some people modified the plugin to make changelog work with subversion. What's the status on that? Is it supported now or not? Thanks, Omair - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Changelog plugin - Subversion support status ? (+ some comments)
Hi,
I've browsed through the discussion in the archives regarding subversion
support in the changelog plugin. I tried to use the changelog report.
The good news is that I don't get an error, the bad news is that no
changes are detected.
This is what maven says when building my project
C:\eclipse\workspace\stindexmaven -p test.xml clean site
... (lots of irrelevant output)
[echo] Generating the Change Log...
maven-changelog-plugin:report:
[echo] Generating the changelog report
SCM Working Directory: C:\eclipse\workspace\stindex
SCM Command Line[0]: svn
SCM Command Line[1]: log
SCM Command Line[2]: -v
SCM Command Line[3]: -r{2004-05-16}:{2004-04-15}
ChangeLog found: 0 entries
In the same directory, typing the same command gives
C:\eclipse\workspace\stindexsvn log -v -r{2004-05-16}:{2004-04-15}
r46 | MDB\oiinamul | 2004-05-15 14:47:34 -0400 (Sat, 15 May 2004) | 4 lines
Changed paths:
A \trunk\lib\commons-io-1.0.jar
D \trunk\lib\commons-io-SNAPSHOT.jar
M \trunk\project.xml
M \trunk\src\stindex\Line.java
M \trunk\test\stindex\tbtree\TBTreeTest.java
M \trunk\test.xml
- lib updated commons io v1.0
- more TBTree unit tests added:
*bug* not fixed: nextNode ptr not adjusted on insertion
r45 | MDB\oiinamul | 2004-05-14 23:25:21 -0400 (Fri, 14 May 2004) | 9 lines
Changed paths:
M \trunk\.project
M \trunk\src\stindex\AbstractNode.java
M \trunk\src\stindex\AbstractTracker.java
M \trunk\src\stindex\AbstractTree.java
A \trunk\src\stindex\GenericTracker.java
M \trunk\src\stindex\Line.java
M \trunk\src\stindex\SpatialIndex.java
M \trunk\src\stindex\Statistics.java
A \trunk\src\stindex\Tracker.java (from
\trunk\src\stindex\tsltree\Tracker.java:44)
... etc
Could anyone tell me:
1) if subversion is supported by changelog or still not
2) what I'm doing wrong
This may benefit those who are working on the plugin. I checked out the
code for the plugin and tested the expression in the code to see if it
matched the svn log header. It did... partially. I've attached a
screenshot.
I'd like to know what's the progress on subversion support in the
changelog plugin. Big thanks to all of you who're working on it. I'd
love to contribute, but I'm totally swamped with work.
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changelog plugin - Subversion support status ? (+ some comments)
Omair-Inam Abdul-Matin wrote:
Hi,
I've browsed through the discussion in the archives regarding subversion
support in the changelog plugin. I tried to use the changelog report.
The good news is that I don't get an error, the bad news is that no
changes are detected.
This is what maven says when building my project
C:\eclipse\workspace\stindexmaven -p test.xml clean site
... (lots of irrelevant output)
[echo] Generating the Change Log...
maven-changelog-plugin:report:
[echo] Generating the changelog report
SCM Working Directory: C:\eclipse\workspace\stindex
SCM Command Line[0]: svn
SCM Command Line[1]: log
SCM Command Line[2]: -v
SCM Command Line[3]: -r{2004-05-16}:{2004-04-15}
ChangeLog found: 0 entries
In the same directory, typing the same command gives
C:\eclipse\workspace\stindexsvn log -v -r{2004-05-16}:{2004-04-15}
r46 | MDB\oiinamul | 2004-05-15 14:47:34 -0400 (Sat, 15 May 2004) | 4 lines
Changed paths:
A \trunk\lib\commons-io-1.0.jar
D \trunk\lib\commons-io-SNAPSHOT.jar
M \trunk\project.xml
M \trunk\src\stindex\Line.java
M \trunk\test\stindex\tbtree\TBTreeTest.java
M \trunk\test.xml
- lib updated commons io v1.0
- more TBTree unit tests added:
*bug* not fixed: nextNode ptr not adjusted on insertion
r45 | MDB\oiinamul | 2004-05-14 23:25:21 -0400 (Fri, 14 May 2004) | 9 lines
Changed paths:
M \trunk\.project
M \trunk\src\stindex\AbstractNode.java
M \trunk\src\stindex\AbstractTracker.java
M \trunk\src\stindex\AbstractTree.java
A \trunk\src\stindex\GenericTracker.java
M \trunk\src\stindex\Line.java
M \trunk\src\stindex\SpatialIndex.java
M \trunk\src\stindex\Statistics.java
A \trunk\src\stindex\Tracker.java (from
\trunk\src\stindex\tsltree\Tracker.java:44)
... etc
Could anyone tell me:
1) if subversion is supported by changelog or still not
2) what I'm doing wrong
This may benefit those who are working on the plugin. I checked out the
code for the plugin and tested the expression in the code to see if it
matched the svn log header. It did... partially. I've attached a
screenshot.
I'd like to know what's the progress on subversion support in the
changelog plugin. Big thanks to all of you who're working on it. I'd
love to contribute, but I'm totally swamped with work.
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I guess attachments are banned on this list... if anyone's interested in
the screenshot they can email me and I'll send it to them.
Omair
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
