Re: integrating with continuum
Knut Wannheden a écrit : Hi again, On 2/1/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: I'm not sure I quite understand your question. But let me explain what I'd like to do. We have 100+ projects in our development environment and occasionally we add new projects and change the dependencies between existing projects. We also change the developer list for the projects. Obviously I'd like the definitions in Continuum to stay in sync without having to enter and verify that manually. I have my answer ;-) You'll can do it by xmlrpc client api. Thinking a little bit more about this I still have some questions. I assume that the idea would be to use the XML-RPC API to propagate any changes I make to the project definitions in the development environment to Continuum. The best way I can think of to get that right every time would be to add a commit trigger to the version management system which would remind the user to update the Continuum definitions every time a project definition file is committed. Although even with that solution the definitions will at best just be out of sync for a short period of time, which with bad luck would cause the build to fail for that reason. How does this work with Maven projects? Will Continuum automatically update its project definitions when it detects a change to the POM? If that is the case I'd much prefer to be able to add custom project types to Continuum which would let me achieve the same effect. Does this sound reasonable or is this out of scope for the Continuum project? If pom changes, Continuum update project definition automatically, but not for all changes like scm url. In 1.1, it will be *perhaps* more easy to add a new project type. Emmanuel
[jira] Created: (CONTINUUM-577) Schedule Build Error
Schedule Build Error Key: CONTINUUM-577 URL: http://jira.codehaus.org/browse/CONTINUUM-577 Project: Continuum Type: Bug Reporter: clojinted Hello, I'm using Continuum with a Maven 2 project. It builds fine when you force the build but the following error arises when the build is scheduled: jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled Exception: jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger schedulerError jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception. jvm 1| org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:202) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| * Nested Exception (Underlying Cause) --- jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) I have replaced continuum-core-1.0.2.jar with continuum-core-1.1-SNAPSHOT.jar and the problem was not fixed. Also I only have one project to build in Continuum. Any help will be greatly appreciated, Thanks very much -- 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: (CONTINUUM-462) Relative path not honoured in cvs commands for flat project layout
[ http://jira.codehaus.org/browse/CONTINUUM-462?page=comments#action_57629 ] Olivier Lamy commented on CONTINUUM-462: You can do it with continum by overriding the scm url in all modules (I use this with continuum 1.0.2) Workaround works for continuum but not for http://jira.codehaus.org/browse/MRELEASE-6 Olivier Relative path not honoured in cvs commands for flat project layout -- Key: CONTINUUM-462 URL: http://jira.codehaus.org/browse/CONTINUUM-462 Project: Continuum Type: Bug Versions: 1.0, 1.0.1 Environment: affects all environments Reporter: Christian Schulte Continuum does not implement the flat project layout as described at http://maven.apache.org/guides/mini/guide-ide-eclipse.html at the end of the site correctly. The checkout via ViewCVS does work but during building continuum does not propagate the relative path to the modules and the parent correctly to the cvs commands it executes making the build fail because of cvs errors about unknown modules. Example: REPOROOT |--ROOT |pom.xml |--MODULE1 |pom.xml |--MODULE2 |pom.xml Just directories below REPOROOT. The ViewCVS URL to import such a project into continuum looks something like this... http://somehost/viewcvs/*checkout*/REPOROOT/ROOT/pom.xml and the SCM URL inside ROOT/pom.xml looks like this... connectionscm:cvs:pserver:[EMAIL PROTECTED]:/cvs:/REPOROOT/ROOT/connection Continuum can successfully build the project inside ROOT but fails for all projects defined like this in ROOT/pom.xml. modules module../MODULE1/module module../MDOULE2/module /modules That is because it tries to do the cvs checkouts wihtout the correct relative path as it did during initial checkout via ViewCVS. 21212715 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Command output: cvs server: cannot find module `REPOROOT/ROOT/MODULE1' - ignored cvs [checkout aborted]: cannot expand modules Here it should have used REPOROOT/ROOT/../MODULE1. The workaround to get this structure working in continuum is to specify the SCM URL inside every single pom.xml of the whole project with the correct path. Continuum then does support the flat project layout. Without the SCM URLs inside every pom it only honours the structure during initial checkout via ViewCVS but not during the cvs commands executed. -- 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: (CONTINUUM-577) Schedule Build Error
[ http://jira.codehaus.org/browse/CONTINUUM-577?page=comments#action_57646 ] Emmanuel Venisse commented on CONTINUUM-577: Where do you find continuum-core-1.1-SNAPSHOT? Can you post the stacktrace with it? Schedule Build Error Key: CONTINUUM-577 URL: http://jira.codehaus.org/browse/CONTINUUM-577 Project: Continuum Type: Bug Reporter: clojinted Hello, I'm using Continuum with a Maven 2 project. It builds fine when you force the build but the following error arises when the build is scheduled: jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled Exception: jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger schedulerError jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception. jvm 1| org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:202) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| * Nested Exception (Underlying Cause) --- jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) I have replaced continuum-core-1.0.2.jar with continuum-core-1.1-SNAPSHOT.jar and the problem was not fixed. Also I only have one project to build in Continuum. Any help will be greatly appreciated, Thanks very much -- 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: (CONTINUUM-578) Continuum doesn't add new projects using effective POM
Continuum doesn't add new projects using effective POM -- Key: CONTINUUM-578 URL: http://jira.codehaus.org/browse/CONTINUUM-578 Project: Continuum Type: Bug Components: Core system Versions: 1.0.2 Reporter: Matthew Beermann Fix For: 1.0.3 I have a series of projects that inherit defaultGoaldeploy/defaultGoal, but one of the active profiles in the Continuum build environment overrides this to defaultGoalsite-deploy/defaultGoal (confirmed by help:effective-pom). However, when I add the project to Continuum, it still ends up having deploy as its goal. This strongly suggests that Continuum isn't applying active profiles to the POM before reading it. This could be a problem in other contexts as well - what if it was, for example, a profile that was supplying the SCM connection data? -- 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: (CONTINUUM-577) Schedule Build Error
[ http://jira.codehaus.org/browse/CONTINUUM-577?page=comments#action_57656 ] clojinted commented on CONTINUUM-577: - The jar came from this url http://beaver.codehaus.org/~evenisse/continuum-core-1.1-SNAPSHOT.jar And the contents of wrapper.log is: INFO | jvm 1| 2006/02/02 16:46:14 | 16:46:14.039 EVENT Started HttpContext[/] INFO | jvm 1| 2006/02/02 16:46:27 | 2006-02-02 16:46:27,417 [SocketListener0-1] INFO Action:login - Trying to log in QCONFIG INFO | jvm 1| 2006/02/02 16:46:42 | 2006-02-02 16:46:42,748 [SocketListener0-1] INFO SchedulesActivator - Unactivating schedule itraxspring INFO | jvm 1| 2006/02/02 16:46:43 | 2006-02-02 16:46:42,748 [SocketListener0-1] INFO SchedulesActivator - Stopping active schedule itraxspring. INFO | jvm 1| 2006/02/02 16:46:43 | 2006-02-02 16:46:42,748 [SocketListener0-1] INFO SchedulesActivator - Activating schedule itraxspring INFO | jvm 1| 2006/02/02 16:46:43 | 2006-02-02 16:46:42,748 [SocketListener0-1] INFO SchedulesActivator - Thu Feb 02 16:47:00 GMT 2006 INFO | jvm 1| 2006/02/02 16:47:00 | 2006-02-02 16:47:00,034 [scheduler1_Worker-1] INFO SchedulesActivator - Executing build job (itraxspring)... INFO | jvm 1| 2006/02/02 16:47:00 | 02-Feb-2006 16:47:00 org.quartz.core.JobRunShell run INFO | jvm 1| 2006/02/02 16:47:00 | SEVERE: Job DEFAULT.itraxspring threw an unhandled Exception: INFO | jvm 1| 2006/02/02 16:47:00 | java.lang.NullPointerException INFO | jvm 1| 2006/02/02 16:47:00 | at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) INFO | jvm 1| 2006/02/02 16:47:00 | at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) INFO | jvm 1| 2006/02/02 16:47:00 | at org.quartz.core.JobRunShell.run(JobRunShell.java:191) INFO | jvm 1| 2006/02/02 16:47:00 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) INFO | jvm 1| 2006/02/02 16:47:00 | 02-Feb-2006 16:47:00 org.quartz.core.ErrorLogger schedulerError INFO | jvm 1| 2006/02/02 16:47:00 | SEVERE: Job (DEFAULT.itraxspring threw an exception. INFO | jvm 1| 2006/02/02 16:47:00 | org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] INFO | jvm 1| 2006/02/02 16:47:00 | at org.quartz.core.JobRunShell.run(JobRunShell.java:202) INFO | jvm 1| 2006/02/02 16:47:00 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) INFO | jvm 1| 2006/02/02 16:47:00 | * Nested Exception (Underlying Cause) --- INFO | jvm 1| 2006/02/02 16:47:00 | java.lang.NullPointerException INFO | jvm 1| 2006/02/02 16:47:00 | at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) INFO | jvm 1| 2006/02/02 16:47:00 | at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) INFO | jvm 1| 2006/02/02 16:47:00 | at org.quartz.core.JobRunShell.run(JobRunShell.java:191) INFO | jvm 1| 2006/02/02 16:47:00 | at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) If this isn't what you want let me know. Thanks very much, Ger Schedule Build Error Key: CONTINUUM-577 URL: http://jira.codehaus.org/browse/CONTINUUM-577 Project: Continuum Type: Bug Reporter: clojinted Hello, I'm using Continuum with a Maven 2 project. It builds fine when you force the build but the following error arises when the build is scheduled: jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled Exception: jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger schedulerError jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception. jvm 1| org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:202) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| * Nested Exception (Underlying Cause) --- jvm 1| java.lang.NullPointerException jvm 1|
[jira] Commented: (CONTINUUM-577) Schedule Build Error
[ http://jira.codehaus.org/browse/CONTINUUM-577?page=comments#action_57658 ] Emmanuel Venisse commented on CONTINUUM-577: Thanks. Schedule Build Error Key: CONTINUUM-577 URL: http://jira.codehaus.org/browse/CONTINUUM-577 Project: Continuum Type: Bug Reporter: clojinted Hello, I'm using Continuum with a Maven 2 project. It builds fine when you force the build but the following error arises when the build is scheduled: jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled Exception: jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger schedulerError jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception. jvm 1| org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:202) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) jvm 1| * Nested Exception (Underlying Cause) --- jvm 1| java.lang.NullPointerException jvm 1| at org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:368) jvm 1| at org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:66) jvm 1| at org.quartz.core.JobRunShell.run(JobRunShell.java:191) jvm 1| at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) I have replaced continuum-core-1.0.2.jar with continuum-core-1.1-SNAPSHOT.jar and the problem was not fixed. Also I only have one project to build in Continuum. Any help will be greatly appreciated, Thanks very much -- 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: (CONTINUUM-578) Continuum doesn't add new projects using effective POM
[ http://jira.codehaus.org/browse/CONTINUUM-578?page=comments#action_57700 ] Trygve Laugstol commented on CONTINUUM-578: --- Continuum is using the effective POM as it's using Maven itself to read the pom.xml file. The real issue here is that Continuum isn't using the default goal stated in the pom. Continuum doesn't add new projects using effective POM -- Key: CONTINUUM-578 URL: http://jira.codehaus.org/browse/CONTINUUM-578 Project: Continuum Type: Bug Components: Core system Versions: 1.0.2 Reporter: Matthew Beermann Fix For: 1.0.3 I have a series of projects that inherit defaultGoaldeploy/defaultGoal, but one of the active profiles in the Continuum build environment overrides this to defaultGoalsite-deploy/defaultGoal (confirmed by help:effective-pom). However, when I add the project to Continuum, it still ends up having deploy as its goal. This strongly suggests that Continuum isn't applying active profiles to the POM before reading it. This could be a problem in other contexts as well - what if it was, for example, a profile that was supplying the SCM connection data? -- 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
Re: problem building continuum
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
Re: problem building continuum
$ find . -name wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/solaris/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/win32/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/linux/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/macosx/wrapper.conf
I tried changing the linux one (I'm running on Fedora 4), but I get identical results. Note that continuum is started when being built by maven. So I suspect the wrapper stuff is not used. I will attach result.log to this message (for those inclined to dig into what is not getting enough memory.)
Can anyone tell me how to raise the memory so I don't get these out of memory
errors when building contiuum?
Thanks
-bob
dan tran wrote:
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
result.log.gz
Description: GNU Zip compressed data
Re: problem building continuum
did you take a look at continuum install directory/conf/wrapper.conf ?
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
$ find . -name wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/solaris/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/win32/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/linux/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/macosx/wrapper.conf
I tried changing the linux one (I'm running on Fedora 4), but I get
identical results. Note that continuum is started when being built by
maven. So I suspect the wrapper stuff is not used. I will attach
result.log to this message (for those inclined to dig into what is not
getting enough memory.)
Can anyone tell me how to raise the memory so I don't get these out
of memory errors when building contiuum?
Thanks
-bob
dan tran wrote:
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
[jira] Updated: (SCM-29) test with CVS NT
[ http://jira.codehaus.org/browse/SCM-29?page=all ] Emmanuel Venisse updated SCM-29: Fix Version: 1.0 test with CVS NT Key: SCM-29 URL: http://jira.codehaus.org/browse/SCM-29 Project: Maven SCM Type: Test Components: maven-scm-provider-cvs Reporter: Brett Porter Fix For: 1.0 Vincent reported test failures on CVS NT... test it and fix if required. -- 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: (SCM-121) Intermittent CVS test failures
[ http://jira.codehaus.org/browse/SCM-121?page=all ] Emmanuel Venisse updated SCM-121: - Fix Version: (was: 1.0-beta-3) 1.0 Intermittent CVS test failures -- Key: SCM-121 URL: http://jira.codehaus.org/browse/SCM-121 Project: Maven SCM Type: Bug Components: maven-scm-provider-cvs Versions: 1.0-beta-3 Reporter: Mike Perham Fix For: 1.0 Dan and I continue to have test failures when trying to compile the cvs plugin in our environment. I emailed these problems to the scm-dev list about a week ago. -- 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: (SCM-85) Allow svn username/password to be set in servers section of settings.xml
[ http://jira.codehaus.org/browse/SCM-85?page=all ] Emmanuel Venisse updated SCM-85: Fix Version: 1.0-beta-3 Allow svn username/password to be set in servers section of settings.xml Key: SCM-85 URL: http://jira.codehaus.org/browse/SCM-85 Project: Maven SCM Type: Improvement Components: maven-scm-provider-svn Reporter: Micah Schehl Fix For: 1.0-beta-3 Attachments: MNG-85-maven-scm.patch, SCM-85.patch Allow developers to have their own subversion username/password set in settings.xml.Also, this would prevent having to use the web setup to enter username/password in Continuum since the info would be in settings.xml. -- 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: (SCM-131) mvn scm:validate does not validate the developerConnection in the pom
[ http://jira.codehaus.org/browse/SCM-131?page=all ]
Emmanuel Venisse updated SCM-131:
-
Fix Version: 1.0-beta-3
mvn scm:validate does not validate the developerConnection in the pom
-
Key: SCM-131
URL: http://jira.codehaus.org/browse/SCM-131
Project: Maven SCM
Type: Bug
Components: maven-plugin
Reporter: Dennis Lundberg
Fix For: 1.0-beta-3
Attachments: SCM-131.patch
There are a couple of reasons for this, in ValidateMojo:
# The check to see if the scmDeveloperConnection is not null is done on the
scmConnection
# The @parameter definitions are wrong for both the the scmConnection and
scmDeveloperConnection
The check for scmConnection is never run either because of of the wrong
@parameter definitions. But the actual value from the pom is normally checked
anyway because the default-value for connectionUrl in AbstractScmMojo is
${pom.scm.connection}. But if you run it like this:
mvn scm:validate -DconnectionUrl=invalidScmUrl
the value of pom.scm.connection will not be checked.
The supplied patch fixes these problems and logs an extra error the tells the
user the value of the invalid scm connection url, to help resolve the problem.
--
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: (SCM-133) Merge redundant repository classes
[ http://jira.codehaus.org/browse/SCM-133?page=all ] Emmanuel Venisse updated SCM-133: - Fix Version: (was: 1.0-beta-3) Merge redundant repository classes -- Key: SCM-133 URL: http://jira.codehaus.org/browse/SCM-133 Project: Maven SCM Type: Improvement Components: maven-scm-api Versions: 1.0-beta-2 Reporter: Mike Perham Currently there are: com.apache.maven.scm.repository.ScmRepository com.apache.maven.scm.provider.ScmProviderRepository The comment at the top of the former says: * @todo clarify need - should be able to merge with ScmProviderRepository? -- 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: (SCM-117) Add parameters to scm configuration element
[ http://jira.codehaus.org/browse/SCM-117?page=all ] Emmanuel Venisse updated SCM-117: - Fix Version: (was: 1.0-beta-3) Add parameters to scm configuration element --- Key: SCM-117 URL: http://jira.codehaus.org/browse/SCM-117 Project: Maven SCM Type: Wish Components: maven-scm-provider-starteam Versions: 1.0-beta-2 Reporter: Aviran Mordo Assignee: Dan Tran It would be very nice to have the ability to add parameters to the scm element. For instance to add parameter to always force checkout. for instance in Starteam I would like to add -o so every time stcmd is called the parameters will be concatenated to the command line -- 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: (SCM-21) separate revision and tag handling
[ http://jira.codehaus.org/browse/SCM-21?page=all ]
Emmanuel Venisse updated SCM-21:
Fix Version: (was: 1.0-beta-3)
separate revision and tag handling
--
Key: SCM-21
URL: http://jira.codehaus.org/browse/SCM-21
Project: Maven SCM
Type: Task
Components: maven-scm-api
Reporter: Brett Porter
while in CVS revision# and tag are handled in the same way, the concepts can
be separated and will make other SCMs easier.
for example, in subversion, valid revisions are:
rev#
HEAD
BASE
COMMITTED
PREV
{DATE}
tags are normal checkouts from a different base.
In CVS, revisions are:
rev# (per file only really makes sense here, but can apply to several)
HEAD
SOME_BRANCH_TAG
{DATE}
--
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
Re: Bazaar Provider
1.0-beta-3 will be release before end of Febrary. So if you do them for next week, it's great. Emmanuel Torbjørn Smørgrav a écrit : When is 1.0-beta-3 scheduled to? I'll try to do some of it this weekend, and then I can do the rest at the end of next week. T -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 16:33 To: scm-dev@maven.apache.org Subject: Re: Bazaar Provider Open an issue with this file and you'll add a changelog parser test when it will be ready. You can file issues for other point and assigned them to you. When do you think you'll can do them? I'd like commit fixes before 1.0-beta-3 Emmanuel Torbjørn Smørgrav a écrit : Do you want the output just as below or documented somewhere else? Sample changelog output from Bazaar: revno: 3 committer: [EMAIL PROTECTED] timestamp: Thu 2006-01-26 16:55:47 +0100 message: Inventory stuff revno: 2 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:42:54 +0100 message: Remove comment revno: 1 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:40:14 +0100 message: Initial revision FYI: I have a couple of other issues in the pipeline: 1. Diff cmd is not passing the unit test due to the @@ tag and wrong ScmFileStatus 2. Checkin unit test is failing on linux with bazaar 0.6 3. Add changelog test 4. Test urls with ftps and ftp 5. Proper std.err processing Regards Torbjørn -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 15:11 To: scm-dev@maven.apache.org Subject: Bazaar Provider Hi Torbjorn, Can you provide a sample output of bazaar changelog output and add a changelog consumer test? Thanks Emmanuel
[jira] Created: (SCM-150) Start pure java cvs provider
Start pure java cvs provider Key: SCM-150 URL: http://jira.codehaus.org/browse/SCM-150 Project: Maven SCM Type: New Feature Components: maven-scm-provider-cvs Reporter: Emmanuel Venisse Fix For: 1.0-beta-3 required by changelo plugin for backward compatibility -- 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: (SCM-150) Start pure java cvs provider
[ http://jira.codehaus.org/browse/SCM-150?page=all ] Emmanuel Venisse updated SCM-150: - Assign To: Emmanuel Venisse Fix Version: 1.0-beta-3 Start pure java cvs provider Key: SCM-150 URL: http://jira.codehaus.org/browse/SCM-150 Project: Maven SCM Type: New Feature Components: maven-scm-provider-cvs Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 required by changelo plugin for backward compatibility -- 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: (SCM-130) scm:validate should not require a project
[ http://jira.codehaus.org/browse/SCM-130?page=all ] Emmanuel Venisse closed SCM-130: Assign To: Emmanuel Venisse Resolution: Fixed Done. scm:validate should not require a project - Key: SCM-130 URL: http://jira.codehaus.org/browse/SCM-130 Project: Maven SCM Type: Improvement Versions: 1.0-beta-2 Environment: xp, cvs, starteam Reporter: Dan Tran Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 We should be able to run scm:validate any where as long as we can passin -DconnectionUrl -- 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: (SCM-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=all ] Emmanuel Venisse closed SCM-124: Assign To: Emmanuel Venisse Resolution: Fixed Fixed. I've tested with : MAVEN_OPTS=-Duser.language=de -Duser.country=DE StarteamChangeLogConsumerTest does not work if locale is not en or fr - Key: SCM-124 URL: http://jira.codehaus.org/browse/SCM-124 Project: Maven SCM Type: Bug Components: maven-scm-provider-starteam Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale Reporter: Dennis Lundberg Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 The testcase StarteamChangeLogConsumerTest makes assumptions about the user's locale that are not always true. Lines 45-52 uses the default locale and if a suitable changelog for that locale is not found, it defaults to using the English changelog file. This works well for English and French which have changelog files. But it does not work for other locales that use a different dateformat than English, i.e most of Europe. The problem is that the class StarteamChangeLogConsumer has a private instance variable of SimpleDateFormat called localFormat. This variable can not be set from outside the class. On line 390 localFormat is used to parse dates. This will fail if the user has a different locale than the one being used in the logfile being parsed. I imagine that it is common (at least not uncommon) to have different locales on the server and the client. So the locale used in the StarteamChangeLogConsumer needs to be set to the locale used by the *server* and not the *client*. A simple getter/setter would do the trick. The locale would need to be configurable in some way so that the user can set the locale that is used by his/her server. The reason I stumbled upon this was when I tried to do mvn test for maven-scm. It produced this stacktrace: ... [INFO] [INFO] Building Maven SCM Starteam Provider [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 25 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes [INFO] [surefire:test] [INFO] Setting reports dir: G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports --- T E S T S --- [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec Added: ./maven.xml Added: ./target/checkout/maven.xml Added: ./target/checkout/project.properties Added: ./target/checkout/project.xml Added: ./target/checkout/bootstrap/maven.xml Added: ./target/checkout/bootstrap/project.properties Added: ./target/checkout/bootstrap/project.xml [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec [ERROR] ParseException Caught java.text.ParseException: Unparseable date: 4/21/04 1:05:00 PM PDT at java.text.DateFormat.parse(DateFormat.java:335) at org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) at
[jira] Commented: (SCM-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=comments#action_57688 ] Dennis Lundberg commented on SCM-124: - I can confirm that the tests run successfully using revision 374523. But I do think that the root of the problem is still there. Running the tests succeeds, but they produce 6 ERROR lines in the output, which seems to be ignored. They look like this: [ERROR] ParseException Caught java.text.ParseException: Unparseable date: 4/21/04 1:05:00 PM PDT at java.text.DateFormat.parse(DateFormat.java:335) at org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:79) The reason for these exceptions is this. If no pattern is specified in a call to parseDate( String date, String userPattern, String defaultPattern ) a SimpleDateInstance is created using the users default locale. This assumes that the ChangeLog that is being parsed uses the same date format as the users default locale. As I stated in a previous comment, I don't know much about Starteam, so please correct me if I'm wrong here: Wouldn't it be better to assume a locale of en_US if no pattern is specified? By using a DateFormat factory method I managed to do this in AbstractConsumer, which made the test run successfully *without* any ERROR lines. I'll attach a patch shortly. I do not know, however, how this would affect normal usage. Perhaps someone knowledgeable in Starteam can step up and shed some light on this. StarteamChangeLogConsumerTest does not work if locale is not en or fr - Key: SCM-124 URL: http://jira.codehaus.org/browse/SCM-124 Project: Maven SCM Type: Bug Components: maven-scm-provider-starteam Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale Reporter: Dennis Lundberg Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 The testcase StarteamChangeLogConsumerTest makes assumptions about the user's locale that are not always true. Lines 45-52 uses the default locale and if a suitable changelog for that locale is not found, it defaults to using the English changelog file. This works well for English and French which have changelog files. But it does not work for other locales that use a different dateformat than English, i.e most of Europe. The problem is that the class StarteamChangeLogConsumer has a private instance variable of SimpleDateFormat called localFormat. This variable can not be set from outside the class. On line 390 localFormat is used to parse dates. This will fail if the user has a different locale than the one being used in the logfile being parsed. I imagine that it is common (at least not uncommon) to have different locales on the server and the client. So the locale used in the StarteamChangeLogConsumer needs to be set to the locale used by the *server* and not the *client*. A simple getter/setter would do the trick. The locale would need to be configurable in some way so that the user can set the locale that is used by his/her server. The reason I stumbled upon this was when I tried to do mvn test for maven-scm. It produced this stacktrace: ... [INFO] [INFO] Building Maven SCM Starteam Provider [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 25 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes [INFO] [surefire:test] [INFO] Setting reports dir: G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports --- T E S T S --- [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec Added: ./maven.xml Added: ./target/checkout/maven.xml Added: ./target/checkout/project.properties Added: ./target/checkout/project.xml
[jira] Updated: (SCM-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=all ] Dennis Lundberg updated SCM-124: Attachment: SCM-124.patch StarteamChangeLogConsumerTest does not work if locale is not en or fr - Key: SCM-124 URL: http://jira.codehaus.org/browse/SCM-124 Project: Maven SCM Type: Bug Components: maven-scm-provider-starteam Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale Reporter: Dennis Lundberg Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 Attachments: SCM-124.patch The testcase StarteamChangeLogConsumerTest makes assumptions about the user's locale that are not always true. Lines 45-52 uses the default locale and if a suitable changelog for that locale is not found, it defaults to using the English changelog file. This works well for English and French which have changelog files. But it does not work for other locales that use a different dateformat than English, i.e most of Europe. The problem is that the class StarteamChangeLogConsumer has a private instance variable of SimpleDateFormat called localFormat. This variable can not be set from outside the class. On line 390 localFormat is used to parse dates. This will fail if the user has a different locale than the one being used in the logfile being parsed. I imagine that it is common (at least not uncommon) to have different locales on the server and the client. So the locale used in the StarteamChangeLogConsumer needs to be set to the locale used by the *server* and not the *client*. A simple getter/setter would do the trick. The locale would need to be configurable in some way so that the user can set the locale that is used by his/her server. The reason I stumbled upon this was when I tried to do mvn test for maven-scm. It produced this stacktrace: ... [INFO] [INFO] Building Maven SCM Starteam Provider [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 25 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes [INFO] [surefire:test] [INFO] Setting reports dir: G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports --- T E S T S --- [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec Added: ./maven.xml Added: ./target/checkout/maven.xml Added: ./target/checkout/project.properties Added: ./target/checkout/project.xml Added: ./target/checkout/bootstrap/maven.xml Added: ./target/checkout/bootstrap/project.properties Added: ./target/checkout/bootstrap/project.xml [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec [ERROR] ParseException Caught java.text.ParseException: Unparseable date: 4/21/04 1:05:00 PM PDT at java.text.DateFormat.parse(DateFormat.java:335) at org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) at org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.processGetAuthor(StarteamChangeLogConsumer.java:281 at
[jira] Commented: (SCM-150) Start pure java cvs provider
[ http://jira.codehaus.org/browse/SCM-150?page=comments#action_57690 ] Dennis Lundberg commented on SCM-150: - How is this different from SCM-10? Start pure java cvs provider Key: SCM-150 URL: http://jira.codehaus.org/browse/SCM-150 Project: Maven SCM Type: New Feature Components: maven-scm-provider-cvs Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 required by changelo plugin for backward compatibility -- 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: (SCM-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=all ] Emmanuel Venisse closed SCM-124: Resolution: Fixed Applied. Thanks. StarteamChangeLogConsumerTest does not work if locale is not en or fr - Key: SCM-124 URL: http://jira.codehaus.org/browse/SCM-124 Project: Maven SCM Type: Bug Components: maven-scm-provider-starteam Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale Reporter: Dennis Lundberg Assignee: Emmanuel Venisse Fix For: 1.0-beta-3 Attachments: SCM-124.patch The testcase StarteamChangeLogConsumerTest makes assumptions about the user's locale that are not always true. Lines 45-52 uses the default locale and if a suitable changelog for that locale is not found, it defaults to using the English changelog file. This works well for English and French which have changelog files. But it does not work for other locales that use a different dateformat than English, i.e most of Europe. The problem is that the class StarteamChangeLogConsumer has a private instance variable of SimpleDateFormat called localFormat. This variable can not be set from outside the class. On line 390 localFormat is used to parse dates. This will fail if the user has a different locale than the one being used in the logfile being parsed. I imagine that it is common (at least not uncommon) to have different locales on the server and the client. So the locale used in the StarteamChangeLogConsumer needs to be set to the locale used by the *server* and not the *client*. A simple getter/setter would do the trick. The locale would need to be configurable in some way so that the user can set the locale that is used by his/her server. The reason I stumbled upon this was when I tried to do mvn test for maven-scm. It produced this stacktrace: ... [INFO] [INFO] Building Maven SCM Starteam Provider [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 25 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes [INFO] [surefire:test] [INFO] Setting reports dir: G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports --- T E S T S --- [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec Added: ./maven.xml Added: ./target/checkout/maven.xml Added: ./target/checkout/project.properties Added: ./target/checkout/project.xml Added: ./target/checkout/bootstrap/maven.xml Added: ./target/checkout/bootstrap/project.properties Added: ./target/checkout/bootstrap/project.xml [surefire] Running org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [surefire] Running org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec [ERROR] ParseException Caught java.text.ParseException: Unparseable date: 4/21/04 1:05:00 PM PDT at java.text.DateFormat.parse(DateFormat.java:335) at org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) at org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.processGetAuthor(StarteamChangeLogConsumer.java:281 at
[jira] Created: (MRM-66) Repoitory configuration
Repoitory configuration --- Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-66) Repoitory configuration
[ http://jira.codehaus.org/browse/MRM-66?page=all ] Maria Odea Ching updated MRM-66: Remaining Estimate: 1 day Original Estimate: 1 day Repoitory configuration --- Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-67) Index maintenance
Index maintenance - Key: MRM-67 URL: http://jira.codehaus.org/browse/MRM-67 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Update of index is triggered by discovery, which is a scheduled task. A configuration file that contains the execution schedule of the discoverer will be retrieved and read. These values will be passed/set on the scheduler. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-67) Index maintenance
[ http://jira.codehaus.org/browse/MRM-67?page=all ] Maria Odea Ching updated MRM-67: Remaining Estimate: 1 day Original Estimate: 1 day Index maintenance - Key: MRM-67 URL: http://jira.codehaus.org/browse/MRM-67 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day Update of index is triggered by discovery, which is a scheduled task. A configuration file that contains the execution schedule of the discoverer will be retrieved and read. These values will be passed/set on the scheduler. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSUREFIRE-57) Forking documentation improvement to help with class loader constrainst issues
Forking documentation improvement to help with class loader constrainst issues -- Key: MSUREFIRE-57 URL: http://jira.codehaus.org/browse/MSUREFIRE-57 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.3 Environment: maven 2.0.2 Reporter: Ben Gidley Priority: Minor Attachments: maven-surefire-plugin-374325.patch With (for example) JAXB2 forking surefire causes a java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class This is because by default when forking an Isolated class loader is used. this can be resovled by turning child delegation on. The documentation does not mention this and should be improved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSUREFIRE-57) Forking documentation improvement to help with class loader constrainst issues
[ http://jira.codehaus.org/browse/MSUREFIRE-57?page=all ] Ben Gidley updated MSUREFIRE-57: Attachment: maven-surefire-plugin-374325.patch Forking documentation improvement to help with class loader constrainst issues -- Key: MSUREFIRE-57 URL: http://jira.codehaus.org/browse/MSUREFIRE-57 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.3 Environment: maven 2.0.2 Reporter: Ben Gidley Priority: Minor Attachments: maven-surefire-plugin-374325.patch With (for example) JAXB2 forking surefire causes a java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class This is because by default when forking an Isolated class loader is used. this can be resovled by turning child delegation on. The documentation does not mention this and should be improved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-68) Accomodate query everything in the index
Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-68) Accomodate query everything in the index
[ http://jira.codehaus.org/browse/MRM-68?page=all ] Maria Odea Ching updated MRM-68: Remaining Estimate: 20 hours Original Estimate: 20 hours Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 20 hours Remaining: 20 hours Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-69) Simple query everything search
Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Remaining Estimate: 15 hours Original Estimate: 15 hours Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 15 hours Remaining: 15 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-70) Browse by Group/Artifact/Version
Browse by Group/Artifact/Version Key: MRM-70 URL: http://jira.codehaus.org/browse/MRM-70 Project: Maven Repository Manager Type: Task Components: browser Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-70) Browse by Group/Artifact/Version
[ http://jira.codehaus.org/browse/MRM-70?page=all ] John Tolentino updated MRM-70: -- Version: 1.0-alpha-1 Remaining Estimate: 8 hours Original Estimate: 8 hours Browse by Group/Artifact/Version Key: MRM-70 URL: http://jira.codehaus.org/browse/MRM-70 Project: Maven Repository Manager Type: Task Components: browser Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-71) Traverse Dependencies
Traverse Dependencies - Key: MRM-71 URL: http://jira.codehaus.org/browse/MRM-71 Project: Maven Repository Manager Type: Task Components: browser Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-71) Traverse Dependencies
[ http://jira.codehaus.org/browse/MRM-71?page=all ] John Tolentino updated MRM-71: -- Remaining Estimate: 8 hours Original Estimate: 8 hours Traverse Dependencies - Key: MRM-71 URL: http://jira.codehaus.org/browse/MRM-71 Project: Maven Repository Manager Type: Task Components: browser Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-72) Administration web user interface
Administration web user interface - Key: MRM-72 URL: http://jira.codehaus.org/browse/MRM-72 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-72) Administration web user interface
[ http://jira.codehaus.org/browse/MRM-72?page=all ] John Tolentino updated MRM-72: -- Remaining Estimate: 8 hours Original Estimate: 8 hours Administration web user interface - Key: MRM-72 URL: http://jira.codehaus.org/browse/MRM-72 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MECLIPSE-66) Java Build Path of dependency with scope system is prefixed with the M2_REPO system classpath variable
Java Build Path of dependency with scope system is prefixed with the M2_REPO
system classpath variable
Key: MECLIPSE-66
URL: http://jira.codehaus.org/browse/MECLIPSE-66
Project: Maven 2.x Eclipse Plugin
Type: Bug
Environment: M2 2.0.2
Reporter: Kristian Nordal
I have a dependency defined like this:
dependency
groupIdoink/groupId
artifactIdoink/artifactId
version1.0.0/version
scopesystem/scope
systemPath${basedir}/oink/oink/1.0.0/oink-1.0.0.jar/systemPath
/dependency
mvn eclipse:eclipse puts an entry in .classpath like this:
classpathentry kind=var
path=M2_REPO//Users/kristian/hisp/scm/trunk/dhis-2-web/dhis-rt/oink/oink/1.0.0/oink-1.0.0.jar/
I guess it should be something like this:
classpathentry kind=lib
path=/Users/kristian/hisp/scm/trunk/dhis-2-web/dhis-rt/oink/oink/1.0.0/oink-1.0.0.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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] plugin releases
+5 Arnaud On 2/1/06, Lukas Theussl [EMAIL PROTECTED] wrote: Hi again, I'd like to release the following m1 plugins for inclusion in m11b3: [] maven-checkstyle-plugin-3.0 [] maven-clover-plugin-1.11 [] maven-dashboard-plugin-1.9 [] maven-jdepend-plugin-1.6 [] maven-jira-plugin-1.3 Please check the changes and jira reports on the plugin web pages below for information on what has changed (and what hasn't). +1 and 72h from me. Cheers, Lukas http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-checkstyle-plugin/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-clover-plugin/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-dashboard-plugin/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-jdepend-plugin/ http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-jira-plugin/ maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-checkstyle-plugin -Dversion=3.0-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-clover-plugin -Dversion=1.11-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.9-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-jdepend-plugin -Dversion=1.6-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-jira-plugin -Dversion=1.3-SNAPSHOT - 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]
[jira] Created: (MNG-2031) Easily disable / exclude transitive dependencies
Easily disable / exclude transitive dependencies Key: MNG-2031 URL: http://jira.codehaus.org/browse/MNG-2031 Project: Maven 2 Type: New Feature Components: Dependencies Versions: 2.0.2 Reporter: Guillaume Nodet Priority: Critical Transitive dependencies are cool, however, the limitations are very difficult to work around. * specification dependencies * jarjar dependencies (spring.jar includes all spring-xxx.jar, so no need to include them) * remove warning on relocations for transitive dependencies (it's always difficult to tell users: that's not an error, and we can not do anything) * poms on ibiblio are all in m2 and never change * exclusions for transitive deps can be overriden if manually included One cool feature would be to allow disabling transitive dependencies in the following ways: * disable all transitive deps * enable transitive dependencies only for modules of the same project * enable transitive deps for specific groupIds * disable transitive deps for specific groupIds * have a tag/attribute to exclude all transitive deps for one dependency (instead of having list all exclusions) -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-718) poi-2.0-final-20040126.jar gives HTTP 404 error
poi-2.0-final-20040126.jar gives HTTP 404 error --- Key: MAVENUPLOAD-718 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-718 Project: maven-upload-requests Type: Bug Reporter: Eirik Bjørsnøs Hi, The following URL leads to a 404 page: http://www.ibiblio.org/maven/poi/jars/poi-2.0-final-20040126.jar But the file is listed in the directory index, here: http://www.ibiblio.org/maven/poi/jars/ What could be wrong? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-714) Upload jericho-html-1.5-dev1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-714?page=all ] Tomislav Stojcevich reopened MAVENUPLOAD-714: - The sources did not make it into the repository. Upload jericho-html-1.5-dev1.jar Key: MAVENUPLOAD-714 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-714 Project: maven-upload-requests Type: Bug Reporter: Tomislav Stojcevich Assignee: Carlos Sanchez Attachments: jericho-html-1.5-dev1-bundle.jar Upload 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-659) Upload AjaxTags library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=comments#action_57624 ] Tomislav Stojcevich commented on MAVENUPLOAD-659: - The sources did not make it into the repository. Upload AjaxTags library --- Key: MAVENUPLOAD-659 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659 Project: maven-upload-requests Type: Task Reporter: Olivier Lamy Assignee: Carlos Sanchez Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5.jar, project.xml Hi, Please upload the AjaxTags library version 1.1.5. The project url is located http://ajaxtags.sourceforge.net. Download link : http://sourceforge.net/project/showfiles.php?group_id=140499package_id=154180release_id=370728 This project is build with maven1. Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MASSEMBLY-66) Ability to index into a nominated dependency JAR to identify files to include in the assembly (Im thinking .so/.dll etc)
Ability to index into a nominated dependency JAR to identify files to include in the assembly (Im thinking .so/.dll etc) Key: MASSEMBLY-66 URL: http://jira.codehaus.org/browse/MASSEMBLY-66 Project: Maven 2.x Assembly Plugin Type: Improvement Environment: Linux, x86_64, x86, win32 Reporter: Andy Brook Priority: Critical Im trying to bundle a SWT application, I'm almost there, the only thing missing is the ability to include .so files in the assembly that are currently stored inside a dependancy. As far as I can tell there is no neat way to pull a few files out of a given dependency... My example is the SWT libraries, the GTK linux specific JAR in the eclipse bundle also contain the native libraries. Ive renamed this to fit into a maven2 repository, but really dont want to have to copy the files manually. Ideally, I would like to be able to specify the dependency in mind and extend the fileSet element to allow the context of the include to work only within that dependency. If there is something Im missing and this can be done with existing plugins Id like to hear about it! eg: ::POM:: !--ECLIPSE SWT GTK-- dependency groupIdorg.eclipse.swt/groupId artifactIdgtk-linux-x86/artifactId version3.1.1/version scoperuntime/scope /dependency ::assembly-descriptor.xml:: !-- /native -- fileSet dependencyorg.eclipse.swt:gtk-linux-x86:3.1.1/dependency outputDirectory/lib/outputDirectory includes include*.so/include /includes /fileSet -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MASSEMBLY-66) Ability to index into a nominated dependency JAR to identify files to include in the assembly (Im thinking .so/.dll etc)
[ http://jira.codehaus.org/browse/MASSEMBLY-66?page=comments#action_57626 ] Andy Brook commented on MASSEMBLY-66: - another possible workaround is to bodge the use of scope in the dependency, mark the dependency in question as say 'test', and refer to this scope in the dependencySets, identifying it specifically. Unfortunatly there is no include filter so this would unpack the classes also. messy. Ability to index into a nominated dependency JAR to identify files to include in the assembly (Im thinking .so/.dll etc) Key: MASSEMBLY-66 URL: http://jira.codehaus.org/browse/MASSEMBLY-66 Project: Maven 2.x Assembly Plugin Type: Improvement Environment: Linux, x86_64, x86, win32 Reporter: Andy Brook Priority: Critical Im trying to bundle a SWT application, I'm almost there, the only thing missing is the ability to include .so files in the assembly that are currently stored inside a dependancy. As far as I can tell there is no neat way to pull a few files out of a given dependency... My example is the SWT libraries, the GTK linux specific JAR in the eclipse bundle also contain the native libraries. Ive renamed this to fit into a maven2 repository, but really dont want to have to copy the files manually. Ideally, I would like to be able to specify the dependency in mind and extend the fileSet element to allow the context of the include to work only within that dependency. If there is something Im missing and this can be done with existing plugins Id like to hear about it! eg: ::POM:: !--ECLIPSE SWT GTK-- dependency groupIdorg.eclipse.swt/groupId artifactIdgtk-linux-x86/artifactId version3.1.1/version scoperuntime/scope /dependency ::assembly-descriptor.xml:: !-- /native -- fileSet dependencyorg.eclipse.swt:gtk-linux-x86:3.1.1/dependency outputDirectory/lib/outputDirectory includes include*.so/include /includes /fileSet -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bazaar Provider
Hi Torbjorn, Can you provide a sample output of bazaar changelog output and add a changelog consumer test? Thanks Emmanuel
[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57633 ] Kenney Westerhof commented on MRELEASE-6: - 1) that is best practise. But having a module directory 'a' containing a pom with artifactId 'b' should work though. 2) Correct, that is the default. When scanning for parent poms, first ../pom.xml is checked to see if it matches the parent tag. If that fails, the local/remote repositories are consulted for that pom. The problem here with the SCM module is that if your CVS/Subversion/Whatever repository layout does not match the default parent/module inheritance model (module = artifactId subdir, parent = ..), you have to specify the SCMUrl in every pom. Only when the default layout is used, Maven can make a well educated guess on the SCM url. The same goes for site urls, btw. In theory, maven should use the module definitions to define SCM urls for child modules. But it poses some problems. Say you want to release a submodule. You do the release there. Maven will try to guess the SCM url by traversing the parent-tree until an SCM url is found (actually it'll go all the way up to the built-in root pom..). It first tries ../pom.xml, which does not exist. It then retrieves the pom from the repository. Since there's no relation between the module directory name and the artifactId, it cannot see which of the module tags corresponds to the project you're currently trying to release. It can only append the current artifactId to that SCM url and hope it's correct. I hope this clarifies a lot. There is no easy solution.. Multiproject Release: No check in - Key: MRELEASE-6 URL: http://jira.codehaus.org/browse/MRELEASE-6 Project: Maven 2.x Release Plugin Type: Bug Environment: Windows XP, Eclipse Workspace Reporter: Bernd Mau Priority: Critical I tried to release a multiproject with 5 modules (on a Branch). Well, the POMs of all modules are changed and there are some dependencies which have been updated correctly. But only the master has been checked in correctly. I'm changed the recommended layout, to fit in an eclipse workspace. I have one master at the same level as the other modules. The module section of the master pom.xml: modules module../hhla.library.pom/module module../hhla.library.site/module module../hhla.lang/module module../hhla.common.log4jx/module /modules -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57634 ] Kenney Westerhof commented on MRELEASE-6: - One more thing: only typepom/type projects can have modules. So I don't see any reason not to add a root pom that specifies your four modules. That way you can have a normal tree with the modules as direct children (in the sub-directory-sense) as was intended: master/ /hhla /hhla... Since the master would have packaging pom, it won't get included in eclipse, since it does not produce any artifacts. I do this all the time and have absolutely no problems with it. Multiproject Release: No check in - Key: MRELEASE-6 URL: http://jira.codehaus.org/browse/MRELEASE-6 Project: Maven 2.x Release Plugin Type: Bug Environment: Windows XP, Eclipse Workspace Reporter: Bernd Mau Priority: Critical I tried to release a multiproject with 5 modules (on a Branch). Well, the POMs of all modules are changed and there are some dependencies which have been updated correctly. But only the master has been checked in correctly. I'm changed the recommended layout, to fit in an eclipse workspace. I have one master at the same level as the other modules. The module section of the master pom.xml: modules module../hhla.library.pom/module module../hhla.library.site/module module../hhla.lang/module module../hhla.common.log4jx/module /modules -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2032) Bug in dependency exclusions processing (ArtifactFilter's)
Bug in dependency exclusions processing (ArtifactFilter's) -- Key: MNG-2032 URL: http://jira.codehaus.org/browse/MNG-2032 Project: Maven 2 Type: Bug Components: Dependencies Versions: 2.0.1 Reporter: Grzegorz Slowikowski I thing, I found an error in dependency exclusions calculations. For pom dependencies: dependencies dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.8/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency dependency groupIdjfree/groupId artifactIdjfreechart/artifactId version1.0.0/version exclusions exclusion groupIdgnujaxp/groupId artifactIdgnujaxp/artifactId /exclusion /exclusions /dependency /dependencies in method MavenMetadataSource.createArtifacts the two above dependencies are processed and ArtifactFilters are applied. The first dependency (struts) gets ExcludesArtifactFilter( javax.servlet:servlet-api ) - this is OK, but the second dependency (jfreechart) gets wrong filter - AndArtifactFilter which concatenates ExcludesArtifactFilter( gnujaxp:gnujaxp ) with ExcludesArtifactFilter( javax.servlet:servlet-api ). This second ExcludesArtifactFilter comes from the first dependency (struts). Method parameter dependencyFilter is overridden when processing the first dependency and read when processing the second one. The fix should be simple. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-2032) Bug in dependency exclusions processing (ArtifactFilter's)
[ http://jira.codehaus.org/browse/MNG-2032?page=comments#action_57635 ] Grzegorz Slowikowski commented on MNG-2032: --- Sholud be Maven 2.0.2, not 2.0.1 Bug in dependency exclusions processing (ArtifactFilter's) -- Key: MNG-2032 URL: http://jira.codehaus.org/browse/MNG-2032 Project: Maven 2 Type: Bug Components: Dependencies Versions: 2.0.1 Reporter: Grzegorz Slowikowski I thing, I found an error in dependency exclusions calculations. For pom dependencies: dependencies dependency groupIdstruts/groupId artifactIdstruts/artifactId version1.2.8/version exclusions exclusion groupIdjavax.servlet/groupId artifactIdservlet-api/artifactId /exclusion /exclusions /dependency dependency groupIdjfree/groupId artifactIdjfreechart/artifactId version1.0.0/version exclusions exclusion groupIdgnujaxp/groupId artifactIdgnujaxp/artifactId /exclusion /exclusions /dependency /dependencies in method MavenMetadataSource.createArtifacts the two above dependencies are processed and ArtifactFilters are applied. The first dependency (struts) gets ExcludesArtifactFilter( javax.servlet:servlet-api ) - this is OK, but the second dependency (jfreechart) gets wrong filter - AndArtifactFilter which concatenates ExcludesArtifactFilter( gnujaxp:gnujaxp ) with ExcludesArtifactFilter( javax.servlet:servlet-api ). This second ExcludesArtifactFilter comes from the first dependency (struts). Method parameter dependencyFilter is overridden when processing the first dependency and read when processing the second one. The fix should be simple. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bazaar Provider
Open an issue with this file and you'll add a changelog parser test when it will be ready. You can file issues for other point and assigned them to you. When do you think you'll can do them? I'd like commit fixes before 1.0-beta-3 Emmanuel Torbjørn Smørgrav a écrit : Do you want the output just as below or documented somewhere else? Sample changelog output from Bazaar: revno: 3 committer: [EMAIL PROTECTED] timestamp: Thu 2006-01-26 16:55:47 +0100 message: Inventory stuff revno: 2 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:42:54 +0100 message: Remove comment revno: 1 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:40:14 +0100 message: Initial revision FYI: I have a couple of other issues in the pipeline: 1. Diff cmd is not passing the unit test due to the @@ tag and wrong ScmFileStatus 2. Checkin unit test is failing on linux with bazaar 0.6 3. Add changelog test 4. Test urls with ftps and ftp 5. Proper std.err processing Regards Torbjørn -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 15:11 To: scm-dev@maven.apache.org Subject: Bazaar Provider Hi Torbjorn, Can you provide a sample output of bazaar changelog output and add a changelog consumer test? Thanks Emmanuel
[jira] Created: (MRM-73) Artifact Management web user interface
Artifact Management web user interface -- Key: MRM-73 URL: http://jira.codehaus.org/browse/MRM-73 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57636 ] Olivier Lamy commented on MRELEASE-6: - Personnaly, I named directory (module and scm) striclty equals (;-) ). In fact, I used something like this - root-module/pom.xml src/site/global documentation - api-module/pom.xml - root-module as this to edit it with eclipse. But it's easy to change to ./pom.xml (root) site-module with global documentation not a real trouble Thanks, Olivier Multiproject Release: No check in - Key: MRELEASE-6 URL: http://jira.codehaus.org/browse/MRELEASE-6 Project: Maven 2.x Release Plugin Type: Bug Environment: Windows XP, Eclipse Workspace Reporter: Bernd Mau Priority: Critical I tried to release a multiproject with 5 modules (on a Branch). Well, the POMs of all modules are changed and there are some dependencies which have been updated correctly. But only the master has been checked in correctly. I'm changed the recommended layout, to fit in an eclipse workspace. I have one master at the same level as the other modules. The module section of the master pom.xml: modules module../hhla.library.pom/module module../hhla.library.site/module module../hhla.lang/module module../hhla.common.log4jx/module /modules -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-74) Browse web user interface
Browse web user interface - Key: MRM-74 URL: http://jira.codehaus.org/browse/MRM-74 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-75) Caching web user interface
Caching web user interface -- Key: MRM-75 URL: http://jira.codehaus.org/browse/MRM-75 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-76) Front End web user interface
Front End web user interface Key: MRM-76 URL: http://jira.codehaus.org/browse/MRM-76 Project: Maven Repository Manager Type: Task Reporter: John Tolentino For configuring multiple repository proxy. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-77) Reporting web user interface
Reporting web user interface Key: MRM-77 URL: http://jira.codehaus.org/browse/MRM-77 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-78) Repository Indexing web user interface
Repository Indexing web user interface -- Key: MRM-78 URL: http://jira.codehaus.org/browse/MRM-78 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-79) Repository Interface web user interface
Repository Interface web user interface --- Key: MRM-79 URL: http://jira.codehaus.org/browse/MRM-79 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Manual removal of lockfile can be done here. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
hey, i am new to maven dev list
I would like to develop maven plugin for JML as well as push a JML artifact to maven repository, how can i start this? thanks -- killing is my business and business is good :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-80) Scheduling web user interface
Scheduling web user interface - Key: MRM-80 URL: http://jira.codehaus.org/browse/MRM-80 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Should allow user to set schedule for checking of repository changes. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-80) Scheduling web user interface
[ http://jira.codehaus.org/browse/MRM-80?page=all ] John Tolentino updated MRM-80: -- Remaining Estimate: 8 hours Original Estimate: 8 hours Scheduling web user interface - Key: MRM-80 URL: http://jira.codehaus.org/browse/MRM-80 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 8 hours Remaining: 8 hours Should allow user to set schedule for checking of repository changes. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-81) Search web user interface
Search web user interface - Key: MRM-81 URL: http://jira.codehaus.org/browse/MRM-81 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (SCM-148) specify flags to svn
specify flags to svn Key: SCM-148 URL: http://jira.codehaus.org/browse/SCM-148 Project: Maven SCM Type: Improvement Components: maven-scm-provider-svn Reporter: David Saff I'd like an easy way to specify flags that should be passed to the svn command when updating my project. For example, I'd like to pass the --config-dir flag to svn, to redirect it to a different configuration directory. -- 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: (MRM-81) Search web user interface
[ http://jira.codehaus.org/browse/MRM-81?page=all ] John Tolentino updated MRM-81: -- Remaining Estimate: 16 hours Original Estimate: 16 hours Search web user interface - Key: MRM-81 URL: http://jira.codehaus.org/browse/MRM-81 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 16 hours Remaining: 16 hours General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-73) Artifact Management web user interface
[ http://jira.codehaus.org/browse/MRM-73?page=all ] John Tolentino updated MRM-73: -- Remaining Estimate: 18 hours Original Estimate: 18 hours Artifact Management web user interface -- Key: MRM-73 URL: http://jira.codehaus.org/browse/MRM-73 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 18 hours Remaining: 18 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-74) Browse web user interface
[ http://jira.codehaus.org/browse/MRM-74?page=all ] John Tolentino updated MRM-74: -- Remaining Estimate: 1 day, 16 hours Original Estimate: 1 day, 16 hours Browse web user interface - Key: MRM-74 URL: http://jira.codehaus.org/browse/MRM-74 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 1 day, 16 hours Remaining: 1 day, 16 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-78) Repository Indexing web user interface
[ http://jira.codehaus.org/browse/MRM-78?page=all ] John Tolentino updated MRM-78: -- Remaining Estimate: 8 hours Original Estimate: 8 hours Repository Indexing web user interface -- Key: MRM-78 URL: http://jira.codehaus.org/browse/MRM-78 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-75) Caching web user interface
[ http://jira.codehaus.org/browse/MRM-75?page=all ] John Tolentino updated MRM-75: -- Remaining Estimate: 16 hours Original Estimate: 16 hours Caching web user interface -- Key: MRM-75 URL: http://jira.codehaus.org/browse/MRM-75 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 16 hours Remaining: 16 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-77) Reporting web user interface
[ http://jira.codehaus.org/browse/MRM-77?page=all ] John Tolentino updated MRM-77: -- Remaining Estimate: 1 day, 16 hours Original Estimate: 1 day, 16 hours Reporting web user interface Key: MRM-77 URL: http://jira.codehaus.org/browse/MRM-77 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 1 day, 16 hours Remaining: 1 day, 16 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-79) Repository Interface web user interface
[ http://jira.codehaus.org/browse/MRM-79?page=all ] John Tolentino updated MRM-79: -- Remaining Estimate: 4 hours Original Estimate: 4 hours Repository Interface web user interface --- Key: MRM-79 URL: http://jira.codehaus.org/browse/MRM-79 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 4 hours Remaining: 4 hours Manual removal of lockfile can be done here. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MSUREFIRE-54) XML test reports are not well-formed when failure message contains quotes.
[ http://jira.codehaus.org/browse/MSUREFIRE-54?page=all ] Mike Whittemore updated MSUREFIRE-54: - Attachment: XMLReporter.java XML test reports are not well-formed when failure message contains quotes. -- Key: MSUREFIRE-54 URL: http://jira.codehaus.org/browse/MSUREFIRE-54 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: n/a Reporter: Mike Whittemore Attachments: TEST-bad.xml, TEST-good.xml, XMLReporter.java, unittests.xsl When a test fails, and the error message contains quotes, the surefire XML report is not well-formed. The error message gets placed in the failure element's 'message' attribute, which causes nested quotes if the message contains any quotes. Error message quotes should be escaped I believe. This may apply to other elements in the XML report. I am using surefire plugin version 2.1.2 but it may affect other versions as well. Test Case: It's not junit, but it may be helpful. I've attached two faked XML reports that resemble real Maven2 XML surefire reports. The 'bad' one has a message with quotes, the 'good' one does not. I used Xalan and an XSLT found in my CruiseControl install to transform each one. The 'bad' one cannot be parsed. The 'good' well-formed one can be parsed and successfully transformed. I've also attached the XSLT. The commands to run the transforms follow: java -cp path to xalan jar org.apache.xalan.xslt.Process -IN TEST-good.xml -XSL unittests.xsl java -cp path to xalan jar org.apache.xalan.xslt.Process -IN TEST-bad.xml -XSL unitests.xsl -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MSUREFIRE-54) XML test reports are not well-formed when failure message contains quotes.
[ http://jira.codehaus.org/browse/MSUREFIRE-54?page=comments#action_57648 ] Mike Whittemore commented on MSUREFIRE-54: -- Ha ha. The JIRA rendering rendered the symbols above as HTML rather than verbatim. The symbols should be amp;quot;, amp;lt; and amp;gt; XML test reports are not well-formed when failure message contains quotes. -- Key: MSUREFIRE-54 URL: http://jira.codehaus.org/browse/MSUREFIRE-54 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: n/a Reporter: Mike Whittemore Attachments: TEST-bad.xml, TEST-good.xml, XMLReporter.java, unittests.xsl When a test fails, and the error message contains quotes, the surefire XML report is not well-formed. The error message gets placed in the failure element's 'message' attribute, which causes nested quotes if the message contains any quotes. Error message quotes should be escaped I believe. This may apply to other elements in the XML report. I am using surefire plugin version 2.1.2 but it may affect other versions as well. Test Case: It's not junit, but it may be helpful. I've attached two faked XML reports that resemble real Maven2 XML surefire reports. The 'bad' one has a message with quotes, the 'good' one does not. I used Xalan and an XSLT found in my CruiseControl install to transform each one. The 'bad' one cannot be parsed. The 'good' well-formed one can be parsed and successfully transformed. I've also attached the XSLT. The commands to run the transforms follow: java -cp path to xalan jar org.apache.xalan.xslt.Process -IN TEST-good.xml -XSL unittests.xsl java -cp path to xalan jar org.apache.xalan.xslt.Process -IN TEST-bad.xml -XSL unitests.xsl -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-82) Reports should be components of their own so that new ones can be dropped in
Reports should be components of their own so that new ones can be dropped in Key: MRM-82 URL: http://jira.codehaus.org/browse/MRM-82 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-84) Basic statistics
Basic statistics Key: MRM-84 URL: http://jira.codehaus.org/browse/MRM-84 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-83) Reports should be passed a listener to be able to log their discoveries
Reports should be passed a listener to be able to log their discoveries --- Key: MRM-83 URL: http://jira.codehaus.org/browse/MRM-83 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino - There will be different types of listeners passed in - web page, mail, etc. - There may be more than one listener, which can be achieved through an aggregate listener rather than crowding the interface with collections -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-82) Reports should be components of their own so that new ones can be dropped in
[ http://jira.codehaus.org/browse/MRM-82?page=all ] John Tolentino updated MRM-82: -- Remaining Estimate: 16 hours Original Estimate: 16 hours Reports should be components of their own so that new ones can be dropped in Key: MRM-82 URL: http://jira.codehaus.org/browse/MRM-82 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 16 hours Remaining: 16 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-83) Reports should be passed a listener to be able to log their discoveries
[ http://jira.codehaus.org/browse/MRM-83?page=all ] John Tolentino updated MRM-83: -- Remaining Estimate: 16 hours Original Estimate: 16 hours Reports should be passed a listener to be able to log their discoveries --- Key: MRM-83 URL: http://jira.codehaus.org/browse/MRM-83 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 16 hours Remaining: 16 hours - There will be different types of listeners passed in - web page, mail, etc. - There may be more than one listener, which can be achieved through an aggregate listener rather than crowding the interface with collections -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-84) Basic statistics
[ http://jira.codehaus.org/browse/MRM-84?page=all ] John Tolentino updated MRM-84: -- Remaining Estimate: 16 hours Original Estimate: 16 hours Basic statistics Key: MRM-84 URL: http://jira.codehaus.org/browse/MRM-84 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 16 hours Remaining: 16 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2033) published m2 POM descriptor incorrectly uses o instead of os in at least two places
published m2 POM descriptor incorrectly uses o instead of os in at least two places --- Key: MNG-2033 URL: http://jira.codehaus.org/browse/MNG-2033 Project: Maven 2 Type: Bug Components: Documentation: Guides Reporter: Jerome Lacoste Priority: Minor Probably fixed as the page was published in October 2005. Someone may want to try to duplicate that. Errors indicated with - Extracts: activation activeByDefault/ jdk/ - o name/ family/ arch/ version/ /o activation The conditions within the build runtime environment which will trigger the automatic inclusion of the parent build profile. Element Description activeByDefault Flag specifying whether this profile is active as a default. jdk Specifies that this profile will be activated when a matching JDK is detected. OKosSpecifies that this profile will be activated when matching OS attributes are detected. property Specifies that this profile will be activated when this System property is specified. file Specifies that this profile will be activated based on existence of a file. - o This is an activator which will detect an operating system's attributes in order to activate its profile. ElementDescription -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-85) Repository access should be done through Wagon
Repository access should be done through Wagon -- Key: MRM-85 URL: http://jira.codehaus.org/browse/MRM-85 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino Most likely using the file wagon. When wagon doesn't handle something, we need to make a call on whether to add it to its interface, or write custom handling based on local filesystem. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-86) The operations on the repository must be transactional
The operations on the repository must be transactional -- Key: MRM-86 URL: http://jira.codehaus.org/browse/MRM-86 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-87) Place a lockfile to prevent repository operations when there is a long ongoing process
Place a lockfile to prevent repository operations when there is a long ongoing process -- Key: MRM-87 URL: http://jira.codehaus.org/browse/MRM-87 Project: Maven Repository Manager Type: Task Reporter: John Tolentino Place a lockfile in the root of the repository that prevents deployment or other repository operations when there is a long, ongoing 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-321) Cobertura plugin requires a new psuedo-artifact
Cobertura plugin requires a new psuedo-artifact - Key: MEV-321 URL: http://jira.codehaus.org/browse/MEV-321 Project: Maven Evangelism Type: Bug Reporter: Mike Perham The fix for MOJO-226 requires a copy of the cobertura artifact copied to cobertura-runtime and the following POM added as cobertura-runtime-1.7.pom: project modelVersion4.0.0/modelVersion groupIdcobertura/groupId artifactIdcobertura-runtime/artifactId version1.7/version descriptionA copy of cobertura without the listed dependencies. This artifact is added to the project's test classpath for coverage generation./description /project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-85) Repository access should be done through Wagon
[ http://jira.codehaus.org/browse/MRM-85?page=all ] John Tolentino updated MRM-85: -- Remaining Estimate: 8 hours Original Estimate: 8 hours Repository access should be done through Wagon -- Key: MRM-85 URL: http://jira.codehaus.org/browse/MRM-85 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 8 hours Remaining: 8 hours Most likely using the file wagon. When wagon doesn't handle something, we need to make a call on whether to add it to its interface, or write custom handling based on local filesystem. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-86) The operations on the repository must be transactional
[ http://jira.codehaus.org/browse/MRM-86?page=all ] John Tolentino updated MRM-86: -- Remaining Estimate: 20 hours Original Estimate: 20 hours The operations on the repository must be transactional -- Key: MRM-86 URL: http://jira.codehaus.org/browse/MRM-86 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 20 hours Remaining: 20 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-87) Place a lockfile to prevent repository operations when there is a long ongoing process
[ http://jira.codehaus.org/browse/MRM-87?page=all ] John Tolentino updated MRM-87: -- Version: 1.0-alpha-1 Component: repository interface Remaining Estimate: 1 day Original Estimate: 1 day Place a lockfile to prevent repository operations when there is a long ongoing process -- Key: MRM-87 URL: http://jira.codehaus.org/browse/MRM-87 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino Original Estimate: 1 day Remaining: 1 day Place a lockfile in the root of the repository that prevents deployment or other repository operations when there is a long, ongoing 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (SCM-6) Development/Testing guide
[ http://jira.codehaus.org/browse/SCM-6?page=all ] Emmanuel Venisse updated SCM-6: --- Fix Version: (was: 1.0-beta-3) 1.0 Development/Testing guide - Key: SCM-6 URL: http://jira.codehaus.org/browse/SCM-6 Project: Maven SCM Type: Task Versions: 1.0-alpha-1 Reporter: Jason van Zyl Fix For: 1.0 Guide on how to create new scm providers utilizing the abstract scm test case for easy testing. -- 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: (SCM-42) Create a ChangeSorter for sort and group ChangeSet list
[ http://jira.codehaus.org/browse/SCM-42?page=all ] Emmanuel Venisse updated SCM-42: Fix Version: (was: 1.0-beta-3) Create a ChangeSorter for sort and group ChangeSet list --- Key: SCM-42 URL: http://jira.codehaus.org/browse/SCM-42 Project: Maven SCM Type: Improvement Components: maven-scm-api Versions: 1.0-alpha-2 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse -- 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: (SCM-19) resolve file status ambiguities
[ http://jira.codehaus.org/browse/SCM-19?page=all ] Emmanuel Venisse updated SCM-19: Fix Version: (was: 1.0-beta-3) 1.0 resolve file status ambiguities --- Key: SCM-19 URL: http://jira.codehaus.org/browse/SCM-19 Project: Maven SCM Type: Task Components: maven-scm-api Reporter: Brett Porter Fix For: 1.0 currently ScmFileStatus just reports whatever the provider gave back, but means different things in different SCM's. eg. updated in CVS is UPDATED or PATCHED, in SVN it is UPDATED or MERGED. added in CVS is UPDATED, in SVN it is ADDED. The API should hide this from the user, though perhaps be able to give the extended info if necessary. I suggest isXXX flags instead: isUpdated() isAdded() - just came from an update isMerged() isInConflict() isNew() - new locally etc. -- 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: (SCM-18) complete commands and expose through ScmManager
[ http://jira.codehaus.org/browse/SCM-18?page=all ] Emmanuel Venisse updated SCM-18: Fix Version: (was: 1.0-beta-3) 1.0 complete commands and expose through ScmManager --- Key: SCM-18 URL: http://jira.codehaus.org/browse/SCM-18 Project: Maven SCM Type: Task Components: maven-scm-provider-clearcase, maven-scm-provider-starteam, maven-scm-provider-local, maven-scm-provider-cvs, maven-scm-provider-svn, maven-scm-provider-perforce, maven-scm-api Reporter: Brett Porter Fix For: 1.0 many commands are not completely implemented, or not implemented at all, and some that are have not been exposed through the ScmManager interface. These all need to be rounded out and tested via the TCK for a final 1.0 release. -- 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: (SCM-10) Use cvslib instead of cvs command line in cvs provider
[ http://jira.codehaus.org/browse/SCM-10?page=all ] Emmanuel Venisse updated SCM-10: Fix Version: (was: 1.0-beta-3) 1.0 Use cvslib instead of cvs command line in cvs provider -- Key: SCM-10 URL: http://jira.codehaus.org/browse/SCM-10 Project: Maven SCM Type: Task Versions: 1.0-alpha-1 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0 if cvslib support ext protocol. -- 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: (SCM-5) Create user guide/Guide for the impatient programmer (gipper)
[ http://jira.codehaus.org/browse/SCM-5?page=all ] Emmanuel Venisse updated SCM-5: --- Fix Version: (was: 1.0-beta-3) 1.0 Create user guide/Guide for the impatient programmer (gipper) - Key: SCM-5 URL: http://jira.codehaus.org/browse/SCM-5 Project: Maven SCM Type: Task Versions: 1.0-alpha-1 Reporter: Jason van Zyl Fix For: 1.0 -- 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: (SCM-2) Create POJO facade
[ http://jira.codehaus.org/browse/SCM-2?page=all ] Emmanuel Venisse updated SCM-2: --- Fix Version: (was: 1.0-beta-3) 1.0 Create POJO facade -- Key: SCM-2 URL: http://jira.codehaus.org/browse/SCM-2 Project: Maven SCM Type: Task Versions: 1.0-alpha-1 Reporter: Jason van Zyl Fix For: 1.0 Make an easy to use POJO facade for maven-scm. -- 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
