[jira] Created: (MDEP-67) NPE when resolving the version of a dependency
NPE when resolving the version of a dependency
--
Key: MDEP-67
URL: http://jira.codehaus.org/browse/MDEP-67
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 2.0-alpha-1
Reporter: Stephane Nicoll
Assigned To: Brian Fox
In my project I have the following dependency
{noformat}
com.foo.shared.bar
foo-bar
5.8.3
obfuscated
{noformat}
I try to get the sources without specifying the version so I have the following
config:
{noformat}
org.apache.maven.plugins
maven-dependency-plugin
copy
compile
copy
com.foo.shared.bar
foo-bar
java-source
${project.build.directory}/foo-sources
{noformat}
And I got this
{noformat}
java.lang.NullPointerException
at
org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.fillMissingArtifactVersion(AbstractFromConfigurationMojo.java:230)
at
org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:136)
at
org.apache.maven.plugin.dependency.fromConfiguration.CopyMojo.execute(CopyMojo.java:65)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
--
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: (CONTINUUM-1155) Continuum should be able to use cached username/password credentials when the scm provider supports it
[ http://jira.codehaus.org/browse/CONTINUUM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lester Ecarma updated CONTINUUM-1155: - Attachment: CONTINUUM-1155.patch Please see attached patch for a possible solution. > Continuum should be able to use cached username/password credentials when the > scm provider supports it > -- > > Key: CONTINUUM-1155 > URL: http://jira.codehaus.org/browse/CONTINUUM-1155 > Project: Continuum > Issue Type: New Feature > Components: Environmental >Affects Versions: 1.0.3 >Reporter: Edwin Punzalan > Assigned To: Lester Ecarma > Fix For: 1.1 > > Attachments: CONTINUUM-1155.patch > > -- 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-1155) Continuum should be able to use cached username/password credentials when the scm provider supports it
[ http://jira.codehaus.org/browse/CONTINUUM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89517 ] Emmanuel Venisse commented on CONTINUUM-1155: - Your patch seems to be good, but I'll accept to apply it only when all project types will have this option. > Continuum should be able to use cached username/password credentials when the > scm provider supports it > -- > > Key: CONTINUUM-1155 > URL: http://jira.codehaus.org/browse/CONTINUUM-1155 > Project: Continuum > Issue Type: New Feature > Components: Environmental >Affects Versions: 1.0.3 >Reporter: Edwin Punzalan > Assigned To: Lester Ecarma > Fix For: 1.1 > > Attachments: CONTINUUM-1155.patch > > -- 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: (CONTINUUM-1208) Continuum email notification doesn't have the correct url for log file
[
http://jira.codehaus.org/browse/CONTINUUM-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed CONTINUUM-1208.
---
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: 1.1
> Continuum email notification doesn't have the correct url for log file
> --
>
> Key: CONTINUUM-1208
> URL: http://jira.codehaus.org/browse/CONTINUUM-1208
> Project: Continuum
> Issue Type: Bug
> Components: Notifier - Mail
>Affects Versions: 1.0.3
> Environment: XP Pro SP2
>Reporter: nakees Vivek
> Assigned To: Emmanuel Venisse
> Fix For: 1.1
>
>
> Build failure notification send by continuum doesn't have the correct url
> to download logs. I believe there is a bug filed for this.
> ie "Download as test" doesn't resolve to correct url
> for example
> if you open link send out my email
>
> http://myserver.com:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/193
> download text link point to
>
> http://myserver.com:8080/continuum/servlet/browse?file=$requestUtil.getParameter('id')/${requestUtil.getParameter('buildId')}.log.txt
> instead it should point to
> http://myserver.com:8080/continuum/servlet/browse?file=1/193.log.txt
--
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: (MDEP-67) NPE when resolving the version of a dependency
[
http://jira.codehaus.org/browse/MDEP-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89524
]
Brian Fox commented on MDEP-67:
---
Hrm. That's not good. Going by memory, I think you want type "sources"
> NPE when resolving the version of a dependency
> --
>
> Key: MDEP-67
> URL: http://jira.codehaus.org/browse/MDEP-67
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
>Affects Versions: 2.0-alpha-1
>Reporter: Stephane Nicoll
> Assigned To: Brian Fox
>
> In my project I have the following dependency
> {noformat}
>
> com.foo.shared.bar
> foo-bar
> 5.8.3
> obfuscated
>
> {noformat}
> I try to get the sources without specifying the version so I have the
> following config:
> {noformat}
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> copy
> compile
>
> copy
>
>
>
>
> com.foo.shared.bar
> foo-bar
> java-source
>
> ${project.build.directory}/foo-sources
>
>
>
>
>
>
>
> {noformat}
> And I got this
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.fillMissingArtifactVersion(AbstractFromConfigurationMojo.java:230)
> at
> org.apache.maven.plugin.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems(AbstractFromConfigurationMojo.java:136)
> at
> org.apache.maven.plugin.dependency.fromConfiguration.CopyMojo.execute(CopyMojo.java:65)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
--
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: (MRM-299) IndexArtifactConsumer is never run during wlking through repository
[ http://jira.codehaus.org/browse/MRM-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt closed MRM-299. -- Assignee: Joakim Erdfelt Resolution: Fixed Thanks for the fix! Applied in r516417. > IndexArtifactConsumer is never run during wlking through repository > --- > > Key: MRM-299 > URL: http://jira.codehaus.org/browse/MRM-299 > Project: Archiva > Issue Type: Bug > Components: indexing > Environment: Windows XP, JVM 1.5.0_09-b03, plexus, archiva trunk At > revision 515030. >Reporter: Milosz Witkowski > Assigned To: Joakim Erdfelt >Priority: Minor > > Running archiva on plexus log shows that during walking through repository > index-artifact is never executed. > Instead of it "Artifact Health Consumer" is initiated 3 times. > 2007-03-06 11:08:39,000 [pool-1-thread-1] INFO ConsumerFactory > - Attempting to create consumer [index-artifact] > 2007-03-06 11:08:39,000 [pool-1-thread-1] INFO ConsumerFactory > - Created consumer [index-artifact|Artifact Health Consumer] > 2007-03-06 11:08:39,000 [pool-1-thread-1] INFO ConsumerFactory > - Attempting to create consumer [artifact-health] > 2007-03-06 11:08:39,015 [pool-1-thread-1] INFO ConsumerFactory > - Created consumer [artifact-health|Artifact Health Consumer] > 2007-03-06 11:08:39,015 [pool-1-thread-1] INFO ConsumerFactory > - Attempting to create consumer [metadata-health] > 2007-03-06 11:08:39,015 [pool-1-thread-1] INFO ConsumerFactory > - Created consumer [metadata-health|Artifact Health Consumer] > 2007-03-06 11:08:39,093 [pool-1-thread-1] INFO Discoverer > - Walk Started: [test] /C:/tmp/maven-2.x-repository/ > 2007-03-06 11:08:39,125 [pool-1-thread-1] WARN SQL > - Object with id "javax.xml:jsr173:1.0:pom:" not found ! > 2007-03-06 11:08:39,312 [pool-1-thread-1] WARN SQL > - Object with id "javax.xml:jsr173:1.0:pom:" not found ! > 2007-03-06 11:08:39,328 [pool-1-thread-1] WARN SQL > - Object with id "javax.xml:jsr173:1.0:pom:" not found ! > 2007-03-06 11:08:39,343 [pool-1-thread-1] WARN SQL > - Object with id "jboss:jbpm:3.1.1:jar:" not found ! > 2007-03-06 11:08:39,359 [pool-1-thread-1] WARN SQL > - Object with id "jboss:jbpm:3.1.1:jar:" not found ! > 2007-03-06 11:08:39,375 [pool-1-thread-1] WARN SQL > - Object with id "jboss:jbpm:3.1.1:jar:" not found ! > 2007-03-06 11:08:39,390 [pool-1-thread-1] INFO Discoverer > - Walk Finished: [test] /C:/tmp/maven-2.x-repository/ -- 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-740) Replace JDO/JPOX
[ http://jira.codehaus.org/browse/CONTINUUM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89530 ] Joakim Erdfelt commented on CONTINUUM-740: -- I recommend iBATIS. > Replace JDO/JPOX > > > Key: CONTINUUM-740 > URL: http://jira.codehaus.org/browse/CONTINUUM-740 > Project: Continuum > Issue Type: Task > Components: Database >Reporter: Emmanuel Venisse > Fix For: 1.1 > > > We'll look at JPA as a substitute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2865) New * feature is not documented anywhere
New * feature is not documented anywhere - Key: MNG-2865 URL: http://jira.codehaus.org/browse/MNG-2865 Project: Maven 2 Issue Type: Bug Components: Documentation: General Affects Versions: 2.0.5 Reporter: Wayne Fay After a recent email to Maven Users list, I discovered the new * feature has not been documented *anywhere* official. It is not in the 2.0.5 changelog, nor in JIRA (that I've found), nor in settings.xml reference [1], etc. The only place this has been "documented" is on the Maven Users and Maven Developer email lists, and in various blogs [2]. I find it very strange that a new feature made it into Maven without a corresponding JIRA -- so perhaps it might even make sense to retroactively add it? This needs to be documented somewhere (probably multiple places) asap. [1] http://maven.apache.org/ref/2.0.4/maven-settings/settings.html#class_mirror [2] http://jroller.com/page/carlossg?entry=proxying_and_hosting_a_maven -- 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: (MNG-2865) New * feature is not documented anywhere
[ http://jira.codehaus.org/browse/MNG-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89546 ] Brett Porter commented on MNG-2865: --- http://maven.apache.org/guides/mini/guide-mirror-settings.html I'm going to edit this JIRA to be the one you mentioned retroactively. > New * feature is not documented anywhere > - > > Key: MNG-2865 > URL: http://jira.codehaus.org/browse/MNG-2865 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Reporter: Wayne Fay > Fix For: 2.0.5 > > > After a recent email to Maven Users list, I discovered the new > * feature has not been documented *anywhere* official. > It is not in the 2.0.5 changelog, nor in JIRA (that I've found), nor in > settings.xml reference [1], etc. The only place this has been "documented" is > on the Maven Users and Maven Developer email lists, and in various blogs [2]. > I find it very strange that a new feature made it into Maven without a > corresponding JIRA -- so perhaps it might even make sense to retroactively > add it? > This needs to be documented somewhere (probably multiple places) asap. > [1] > http://maven.apache.org/ref/2.0.4/maven-settings/settings.html#class_mirror > [2] http://jroller.com/page/carlossg?entry=proxying_and_hosting_a_maven -- 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: (MNG-2865) Add * feature
[ http://jira.codehaus.org/browse/MNG-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2865. - Resolution: Fixed > Add * feature > -- > > Key: MNG-2865 > URL: http://jira.codehaus.org/browse/MNG-2865 > Project: Maven 2 > Issue Type: New Feature > Components: Documentation: General >Reporter: Wayne Fay > Assigned To: Brett Porter > Fix For: 2.0.5 > > > After a recent email to Maven Users list, I discovered the new > * feature has not been documented *anywhere* official. > It is not in the 2.0.5 changelog, nor in JIRA (that I've found), nor in > settings.xml reference [1], etc. The only place this has been "documented" is > on the Maven Users and Maven Developer email lists, and in various blogs [2]. > I find it very strange that a new feature made it into Maven without a > corresponding JIRA -- so perhaps it might even make sense to retroactively > add it? > This needs to be documented somewhere (probably multiple places) asap. > [1] > http://maven.apache.org/ref/2.0.4/maven-settings/settings.html#class_mirror > [2] http://jroller.com/page/carlossg?entry=proxying_and_hosting_a_maven -- 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: (MNG-2865) Add * feature
[ http://jira.codehaus.org/browse/MNG-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2865: -- Assignee: Brett Porter Affects Version/s: (was: 2.0.5) Fix Version/s: 2.0.5 Issue Type: New Feature (was: Bug) Summary: Add * feature (was: New * feature is not documented anywhere) > Add * feature > -- > > Key: MNG-2865 > URL: http://jira.codehaus.org/browse/MNG-2865 > Project: Maven 2 > Issue Type: New Feature > Components: Documentation: General >Reporter: Wayne Fay > Assigned To: Brett Porter > Fix For: 2.0.5 > > > After a recent email to Maven Users list, I discovered the new > * feature has not been documented *anywhere* official. > It is not in the 2.0.5 changelog, nor in JIRA (that I've found), nor in > settings.xml reference [1], etc. The only place this has been "documented" is > on the Maven Users and Maven Developer email lists, and in various blogs [2]. > I find it very strange that a new feature made it into Maven without a > corresponding JIRA -- so perhaps it might even make sense to retroactively > add it? > This needs to be documented somewhere (probably multiple places) asap. > [1] > http://maven.apache.org/ref/2.0.4/maven-settings/settings.html#class_mirror > [2] http://jroller.com/page/carlossg?entry=proxying_and_hosting_a_maven -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1410) please could somebody correct castor-1.0, or give a hint how to use it?
please could somebody correct castor-1.0, or give a hint how to use it? --- Key: MAVENUPLOAD-1410 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1410 Project: maven-upload-requests Issue Type: Task Reporter: THURNER rupert http://repo1.maven.org/maven2/castor/castor/1.0/ does not have a pom file. is there a special maven version which can read such artefacts or the upload somehow was 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
[jira] Closed: (MRRESOURCES-13) If remote resources is run twice (like in a forked lifecycle) the resources are all 0 length
[ http://jira.codehaus.org/browse/MRRESOURCES-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp closed MRRESOURCES-13. -- Resolution: Fixed > If remote resources is run twice (like in a forked lifecycle) the resources > are all 0 length > > > Key: MRRESOURCES-13 > URL: http://jira.codehaus.org/browse/MRRESOURCES-13 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-2 >Reporter: Daniel Kulp > Assigned To: Daniel Kulp >Priority: Blocker > Fix For: 1.0-alpha-3 > > Attachments: pom.xml > > > If you run "mvn compile" with the attached pom, the resources are all 0 > length. This is CRITICAL as the javadoc plugin forks a lifecycle that may > re-invoke the remote-resources plugin. Thus, "mvn javadoc:jar install" > sometimes results in jars without the proper resources. -- 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: (MRRESOURCES-12) It should be possible to use something other than "project.name" for the header
[
http://jira.codehaus.org/browse/MRRESOURCES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp closed MRRESOURCES-12.
--
Resolution: Fixed
> It should be possible to use something other than "project.name" for the
> header
>
>
> Key: MRRESOURCES-12
> URL: http://jira.codehaus.org/browse/MRRESOURCES-12
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Improvement
>Affects Versions: 1.0-alpha-1, 1.0-alpha-2
>Reporter: Daniel Kulp
> Assigned To: Daniel Kulp
> Fix For: 1.0-alpha-3
>
>
> "Adam Lally" <[EMAIL PROTECTED]>:
> However, is there a way to override the name of
> the project that is written to the NOTICES and DISCLAIMER files?
> Currently each jar file uses its own artifact name (e.g. "Apache UIMA
> Java Framework Core") when really we want just the name of our project
> ("Apache UIMA").
--
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: (MNG-2619) building from the middle pom of a (parent,child,grandchild) heirarchy fails
[
http://jira.codehaus.org/browse/MNG-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89549
]
Barrett Nuzum commented on MNG-2619:
Seems to be related to repository metadata --
if the parent has been deployed rather than installed, it is more easily found.
> building from the middle pom of a (parent,child,grandchild) heirarchy fails
> ---
>
> Key: MNG-2619
> URL: http://jira.codehaus.org/browse/MNG-2619
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.4, 2.0.5, 2.1
>Reporter: Richard van der Hoff
> Attachments: maven-project-middlepom.patch
>
>
> Given a heirerchy of projects - parent, child, grandchild - with and
> links between them in the normal way:
> Attempting to start a build from the middle of the heirarchy - ie, the
> "child" - causes maven to attempt to download the parent from the repository
> - even if the version in the filesystem is correct in terms of
> {artifact,group,version}.
> The problem appears to be that the ProjectBuilder first reads the child pom,
> and caches the result (but not the parent pom). The reactor then makes the
> ProjectBuilder read the grandchild pom, and hence the child pom (which now
> comes from the cache), and the parent pom (which it can't find).
> This is much easier demonstrated than explained :/
> The attached patch fixes the problem by making sure that all the projects in
> the heirarchy (including the parent) are added to the cache. It also includes
> a test case to demonstrate 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] Commented: (MIDEA-79) Sources for SNAPSHOT-dependencies are not downloaded correctly.
[ http://jira.codehaus.org/browse/MIDEA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89550 ] Andy DePue commented on MIDEA-79: - I believe this is what I'm seeing as well. I've noticed that if a .pom declares a dependency to an inhouse project, then the sources and javadocs are not linked in the IDEA project. However, sources and javadocs are linked to projects from the maven central repository. It could be the reason for this is because the inhouse modules are all SNAPSHOT. I have a large project with many modules - so many modules, in fact, that it doesn't make sense to put them all in one IDEA project. What I've done is declare the core modules in my main parent .pom, so all those modules get included in the main IDEA project. I should note that all the modules in this main IDEA project do indeed link to each other properly. So, the sources are available, but only because the modules link to each other within the same project. The remaining modules (not included in the main IDEA project) declare the parent .pom as their parent, but the parent .pom does not declare them in its section. Each of these modules is built independently from the main .pom. What I'd like to do is run mvn idea:idea on these independent modules so that each one has its own project all to itself - which works, for the most part, except that any dependencies to other modules in our organization do not have their sources or javadocs added - though dependencies to outside modules do have the sources and javadocs linked. And yes, I've verified that the sources and javadocs for the other modules have been generated and uploaded properly to our inhouse snapshot server. > Sources for SNAPSHOT-dependencies are not downloaded correctly. > --- > > Key: MIDEA-79 > URL: http://jira.codehaus.org/browse/MIDEA-79 > Project: Maven 2.x Idea Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Jan Thomae > Assigned To: Stephane Nicoll > > When downloading sources for SNAPSHOT dependencies, the plugin uses the > wrong path. Instead of downloading > http://repository.insomnia-hq.de/de/insomniahq/icc/1.0-SNAPSHOT/icc-1.0-20061202.231038-59-sources.jar > it tries to download > http://repository.insomnia-hq.de/de/insomniahq/icc/icc-1.0-20061202.231038-59/icc-1.0-20061202.231038-59-sources.jar > Also sometimes it tries to download > http://repository.insomnia-hq.de/de/insomniahq/icc/1.0-SNAPSHOT/icc-1.0-SNAPSHOT-sources.jar > instead of replacing the SNAPSHOT with the actual snapshot version. -- 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: (CONTINUUM-440) Failed to start continuum on 64bit Linux
[ http://jira.codehaus.org/browse/CONTINUUM-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-440: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Failed to start continuum on 64bit Linux > > > Key: CONTINUUM-440 > URL: http://jira.codehaus.org/browse/CONTINUUM-440 > Project: Continuum > Issue Type: Bug > Components: Environmental >Affects Versions: 1.0 > Environment: OS:Debian Linux x86-64, Proc: amd64-xeon >Reporter: Nic >Priority: Critical > Fix For: 1.1-alpha-2 > > > When starting continuum I get the following error: > # ./run.sh start > Starting continuum... > ./run.sh: line 192: /usr/local/continuum-1.0/bin/linux/wrapper: No such file > or directory > ./run.sh: line 192: /usr/local/continuum-1.0/bin/linux/wrapper: Success > But, there's no such error on a 32bit Linux system. -- 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: (CONTINUUM-745) Uploading pom file does not support projects with modules
[ http://jira.codehaus.org/browse/CONTINUUM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-745: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Uploading pom file does not support projects with modules > - > > Key: CONTINUUM-745 > URL: http://jira.codehaus.org/browse/CONTINUUM-745 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: debian linux / ubuntu linux >Reporter: Andrew Williams >Priority: Critical > Fix For: 1.1-alpha-2 > > > Uploaded pom files cannot contain sub modules. > I see in issue CONTINUUM-425 that this is known, but it really should be > possible to fix. > Can we not just read the scm and download _before_ trying to read the child > poms? -- 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: (CONTINUUM-723) strange trouble on solaris
[ http://jira.codehaus.org/browse/CONTINUUM-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-723: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > strange trouble on solaris > --- > > Key: CONTINUUM-723 > URL: http://jira.codehaus.org/browse/CONTINUUM-723 > Project: Continuum > Issue Type: Bug > Components: Environmental >Affects Versions: 1.0.3 > Environment: solaris >Reporter: Olivier Lamy >Priority: Critical > Fix For: 1.1-alpha-2 > > Attachments: CONTINUUM-723.tar.gz > > > Hi, > I have a junit test with contains the following code : > SimpleDateFormat simpleDateFormat = new SimpleDateFormat( "-MM-dd", > Locale.FRANCE ); > // harcoded date due to xmlunit comparaison > Date timeStamp = simpleDateFormat.parse( "2001-05-28" ); > return DateTools.setNoonHour( timeStamp ); > FastDateFormat.getInstance( "-MM-dd'T'HH:mm:ss.SSSZZ" > ).format(date); > On windows+cygwin : 2001-05-28T12:00:00.000+02:00 > On solaris with same user who start continuum exec junit with cli : > 2001-05-28T12:00:00.000+02:00 > The same junit with continuum says : 2001-05-28T12:00:00.000+00:00 > Error says : > Expected attribute value '2001-05-28T12:00:00.000+02:00' but was > '2001-05-28T12:00:00.000+00:00' - comparing at > /OTA_HotelAvailRS[1]/@TimeStamp to at /OTA_HotelAvailRS[1]/@TimeStamp > I start continuum with $CONTINUUM_HOME/bin/plexus.sh > /dev/null & > The .profile contains : > ... > LANG=en_US.ISO8859-15 > export LANG > ##opts maven > MAVEN_OPTS="-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1" > export MAVEN_OPTS > ... > I don't change anything on plexus.sh script. > Any ideas ?? > Thanks, > -- > Olivier -- 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: (CONTINUUM-127) Try using a series of incorrect data in the integration tests
[ http://jira.codehaus.org/browse/CONTINUUM-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-127: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Try using a series of incorrect data in the integration tests > - > > Key: CONTINUUM-127 > URL: http://jira.codehaus.org/browse/CONTINUUM-127 > Project: Continuum > Issue Type: Task > Components: Testing >Affects Versions: 1.0-alpha-3 >Reporter: Jason van Zyl > Assigned To: Trygve Laugstol >Priority: Critical > Fix For: 1.1-alpha-# > > > We need to trap any incorrect data being thrown at continuum coming from any > interface. The best place to try this is the integration tests that we run > from python. I accidentally used some bad POMs using the xmlrpc interface and > in the web interface the projects seems to stay perpetually in the "Checking > Out" state. -- 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: (CONTINUUM-684) Access to Continuum using XML-RPC is not authenticated.
[ http://jira.codehaus.org/browse/CONTINUUM-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-684: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Access to Continuum using XML-RPC is not authenticated. > --- > > Key: CONTINUUM-684 > URL: http://jira.codehaus.org/browse/CONTINUUM-684 > Project: Continuum > Issue Type: Bug > Components: XMLRPC Interface >Reporter: Rahul Thakur > Assigned To: Rahul Thakur >Priority: Critical > Fix For: 1.1-alpha-2 > > > Noticed that I could connect to a Continuum instance on my local box and > obtain list of project details without being authenticated. > Can this also be considered as a request to implement a "doLogin( )" service > or similar for Continuum - 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
[jira] Updated: (CONTINUUM-838) Cross Site Request Forgery protection
[ http://jira.codehaus.org/browse/CONTINUUM-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-838: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Cross Site Request Forgery protection > - > > Key: CONTINUUM-838 > URL: http://jira.codehaus.org/browse/CONTINUUM-838 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0, 1.0.1, 1.0.2, 1.0.3, 1.1-alpha-1 >Reporter: Christian Gruber >Priority: Critical > Fix For: 1.1-alpha-# > > > XSRF vulnerabilities are very hard to fix. More details on them at > http://en.wikipedia.org/wiki/Cross-site_request_forgery with a key document > found at http://isecpartners.com/documents/XSRF_Paper.pdf which outlines a > solution. > In short, an XSRFProtectionToken is passed in each form in a hidden variable, > with the XSRFProtectionToken consisting of (pseudocode): > hash(sessionid + actionName + sitewide_secret); > The hash can be MD5 or SHA-1 or whatever. The important thing is that even > if a user is logged on with a valid sessionId, the attacker cannot know in > advance what the token will be without getting it out of an insecure browser > (in which case, you have other problems). Even if the attacker gets access > to a token for one action that's less security-risky (like invoking a build), > they cannot then replay that token against something more risky (such as > creating a new admin user). -- 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: (CONTINUUM-699) Error in displaying of build state icons in main page of gui.
[ http://jira.codehaus.org/browse/CONTINUUM-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-699. - Resolution: Cannot Reproduce not applicable in current version > Error in displaying of build state icons in main page of gui. > - > > Key: CONTINUUM-699 > URL: http://jira.codehaus.org/browse/CONTINUUM-699 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: Linux Debian > maven 2.0.4 >Reporter: Wolfgang Klein > Assigned To: Jesse McConnell >Priority: Critical > Fix For: 1.1-alpha-1 > > Attachments: icon_problem.png > > > Hello! > First, let me say that i like the 1.0.3 version. > I´ve got a small problem with the state icons > in the web client and have attached a screen > shot showing the problem. > After some time, the "update sources" icons > disappears and it looks like shown in the > screenshot. > I´ve found another icon bug, i hope, this is > a different bug and so no duplicate! > Greetings, > W.K. -- 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: (CONTINUUM-427) create an XML report of all the failures in all the builds
[ http://jira.codehaus.org/browse/CONTINUUM-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-427: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > create an XML report of all the failures in all the builds > -- > > Key: CONTINUUM-427 > URL: http://jira.codehaus.org/browse/CONTINUUM-427 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Reporter: james strachan >Priority: Critical > Fix For: 1.1-alpha-# > > > It'd make it really easy to slice and dice the data & make custom > views/portlets/pages across multiple continuum installations on different > hardware, OS and JVM if we could get a single XML report of all the failures > in all the builds as a blob of XML. > e.g. > > > org.activemq.FooTest>http://acme.com/foo.txt > > > > > > Then with a trivial bit of XSLT (or some script) we can easily slice and dice > the results from multiple continuum installations (OS, hardware, JVM) into > reports to make it easy to see the big picture. Hopefully these reports can > also become part of CI - but at least folks can then hack up their own to get > going. > e.g. folks could emded on wiki/portal pages summaries of whats working & not > 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: (CONTINUUM-347) document push build technique by project id
[ http://jira.codehaus.org/browse/CONTINUUM-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-347: -- Description: this could use some further explanation Fix Version/s: (was: 1.1-alpha-1) Future > document push build technique by project id > --- > > Key: CONTINUUM-347 > URL: http://jira.codehaus.org/browse/CONTINUUM-347 > Project: Continuum > Issue Type: Task > Components: Documentation >Reporter: Brett Porter > Fix For: Future > > > this could use some further explanation -- 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: (CONTINUUM-383) Build Status Notification Information Promotion
[ http://jira.codehaus.org/browse/CONTINUUM-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-383: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Build Status Notification Information Promotion > > > Key: CONTINUUM-383 > URL: http://jira.codehaus.org/browse/CONTINUUM-383 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Affects Versions: 1.0.1 >Reporter: Natalie Burdick > Fix For: 1.1-alpha-2 > > > Change to build status notification e-mail from Continuum, so that specific > Build Failure information is displayed at the Top (and Bottom) of the report > -- see below for sample: > Build statistics: > State: Failed > Failure(s): File.. > /home/foconer/maven/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly > Element... maven:reactor > Line.. 217 > Column 9 > Unable to obtain goal [test:test] -- > > /home/foconer/maven/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly:181:54: > > Previous State: Failed > Started at: Thu, 27 Oct 2005 15:02:38 -0700 > Finished at: Thu, 27 Oct 2005 15:06:36 -0700 > Total time: 3m 57s > Build Trigger: Schedule > Exit code: 70 > Building machine hostname: iago > Operating system : Linux(unknown) > Java version : 1.5.0_05(Sun Microsystems Inc.) > Changes > assembly/project.xml > assembly/src/release/examples/basic/servicemix.xml > assembly/src/release/examples/jms-binding/servicemix.xml > assembly/src/release/examples/bpel/servicemix.xml > assembly/src/release/examples/file-binding/servicemix.xml > assembly/src/release/examples/http-binding/servicemix.xml > assembly/src/release/examples/quartz-binding/servicemix.xml > project.properties > servicemix-all/maven.xml > servicemix-all/project.xml > core/project.properties > core/maven.xml > core/project.xml > etc/project.properties > etc/maven.xml > > > Output: > > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.2 > build:start: > clean:clean: > [delete] Deleting directory > /opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2/target > init: > [echo] init > basedir=/opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2 > jar:install: > multiproject:projects-init: > [echo] Gathering project list > Starting the reactor... > Our processing order: > ServiceMix :: JBI > ServiceMix :: Core > ServiceMix :: Components > ServiceMix :: XFire > ServiceMix :: JAXWS > ServiceMix Full Package > + > | Gathering project list ServiceMix :: JBI > | Memory: 5M/7M > + > + > | Gathering project list ServiceMix :: Core > | Memory: 5M/7M > + > + > | Gathering project list ServiceMix :: Components > | Memory: 5M/7M > + > + > | Gathering project list ServiceMix :: XFire > | Memory: 5M/7M > + > + > | Gathering project list ServiceMix :: JAXWS > | Memory: 5M/7M > + > + > | Gathering project list ServiceMix Full Package > | Memory: 5M/7M > + > Starting the reactor... > Our processing order: > ServiceMix :: JBI > ServiceMix :: Core > ServiceMix :: Components > ServiceMix :: XFire > ServiceMix :: JAXWS > ServiceMix Full Package > + > | Executing jar:install ServiceMix :: JBI > | Memory: 5M/7M > + > multiproject:goal: > build:start: > java:prepare-filesystem: > java:compile: > [echo] Compiling to > /opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2/jbi/target/classes > java:jar-resources: > test:prepare-filesystem: > test:test-resources: > test:compile: > [echo] No test source files to compile. > test:test: > [echo] No tests to run. > Copying: from > '/opt/continuum/continuum-1.0-beta-1/apps/continuum/working-directory/2/jbi/target/servicemix-jbi-2.0-SNAPS
[jira] Closed: (CONTINUUM-596) security applies to entry pages, but not form submission
[ http://jira.codehaus.org/browse/CONTINUUM-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-596. - Resolution: Fixed this was actually addressed recently with some of ochings commits > security applies to entry pages, but not form submission > > > Key: CONTINUUM-596 > URL: http://jira.codehaus.org/browse/CONTINUUM-596 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Brett Porter > Fix For: 1.1-alpha-1 > > > maybe already fixed by the security overhaul, but I noticed in 1.0.3 that I > could add a build definition without being logged in by submitting the form, > when the guest didn't have that permission. -- 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: (CONTINUUM-688) The application.xml file should only specify one component to start up
[ http://jira.codehaus.org/browse/CONTINUUM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-688: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > The application.xml file should only specify one component to start up > -- > > Key: CONTINUUM-688 > URL: http://jira.codehaus.org/browse/CONTINUUM-688 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Jason van Zyl > Assigned To: Jason van Zyl > Fix For: 1.1-alpha-2 > > > A Plexus application should encapsulate all other components it uses. Right > now the load-on-start specifies the continuum application and the task > queues. It should only be the continuum application. -- 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: (CONTINUUM-563) integrate core gbuild distributed builds
[ http://jira.codehaus.org/browse/CONTINUUM-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-563: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > integrate core gbuild distributed builds > > > Key: CONTINUUM-563 > URL: http://jira.codehaus.org/browse/CONTINUUM-563 > Project: Continuum > Issue Type: Task > Components: Core system >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > see: http://opensource2.atlassian.com/confluence/oss/display/GBuild/Home -- 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: (CONTINUUM-458) Trigger scripts ?
[ http://jira.codehaus.org/browse/CONTINUUM-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-458: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Trigger scripts ? > -- > > Key: CONTINUUM-458 > URL: http://jira.codehaus.org/browse/CONTINUUM-458 > Project: Continuum > Issue Type: New Feature > Components: Documentation, XMLRPC Interface >Affects Versions: 1.0.1 >Reporter: Grégory Joseph > Fix For: 1.1-alpha-2 > > > http://maven.apache.org/continuum/guides/getting-started/index.html mentions > 2 python scripts. > However, these are not present in the 1.0.1 tgz distribution. > I hope these are useable as on-commit scripts, to trigger builds when > commiting. > Could be extra nice to have (or others) downloadable as separate artifact, in > order to use them as on-commit trigger scripts, for instance when your > continuum instance runs remotely from the scm server, you wouldn't > necessarily want your scm admin to have to get the 12mb archive ;) -- 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: (CONTINUUM-363) Some URLs incorrect when behind httpd with mod_proxy
[ http://jira.codehaus.org/browse/CONTINUUM-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-363: -- Assignee: Emmanuel Venisse emm, did you take care of this when you were playing around with https support? > Some URLs incorrect when behind httpd with mod_proxy > > > Key: CONTINUUM-363 > URL: http://jira.codehaus.org/browse/CONTINUUM-363 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0-beta-1 >Reporter: David Blevins > Assigned To: Emmanuel Venisse > Fix For: 1.1-alpha-1 > > > Given a mod_proxy setup like: > > [...] > RewriteEngine on > RewriteRule ^/(.*)$ http://localhost:8080/$1 [p] > ProxyPassReverse / http://localhost:8080/ > > All the URLs but the various icon_foo_sml.gif icons will be hardcoded to the > localhost:8080 -- 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: (CONTINUUM-752) Create a tag
[ http://jira.codehaus.org/browse/CONTINUUM-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-752: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Create a tag > -- > > Key: CONTINUUM-752 > URL: http://jira.codehaus.org/browse/CONTINUUM-752 > Project: Continuum > Issue Type: Task > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-# > > > Thsi tag will replace in jsp -- 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: (CONTINUUM-522) IRC support needed for IRC servers not supporting /privmsg
[ http://jira.codehaus.org/browse/CONTINUUM-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-522: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > IRC support needed for IRC servers not supporting /privmsg > -- > > Key: CONTINUUM-522 > URL: http://jira.codehaus.org/browse/CONTINUUM-522 > Project: Continuum > Issue Type: Improvement > Components: Notifier - IRC >Affects Versions: 1.0.2 > Environment: Linux >Reporter: Daniel Kulp > Fix For: 1.1-alpha-# > > > The IRC server we use in house does not support /privmsg for any non-operator > user. The IS folks are refusing to add any other operators for use by the > continuum builds. > It would be nice if we could configure the IRC notifier to do a normal: > /join #channel > and then a normal text message is sent. -- 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: (CONTINUUM-515) Add a wait page when adding a project
[ http://jira.codehaus.org/browse/CONTINUUM-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-515: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 I thought webwork had some built in support for this, might be pretty easy > Add a wait page when adding a project > - > > Key: CONTINUUM-515 > URL: http://jira.codehaus.org/browse/CONTINUUM-515 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-2 > > -- 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: (CONTINUUM-398) changes window shows internal id for project
[ http://jira.codehaus.org/browse/CONTINUUM-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-398. - Resolution: Won't Fix this is the way things are designed at the moment, I would like to see this changed in the future when we better support things like build profiles > changes window shows internal id for project > > > Key: CONTINUUM-398 > URL: http://jira.codehaus.org/browse/CONTINUUM-398 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0 > Environment: Mac Os X >Reporter: yo > Fix For: 1.1-alpha-1 > > > The build result window shows the internal id for a project in the url > for example > 6/somedir/somefile > this should be > somedir/somefile -- 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: (CONTINUUM-668) Build history not showing after 1.0.2 to 1.0.3 migration
[ http://jira.codehaus.org/browse/CONTINUUM-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-668. - Resolution: Won't Fix later in the alpha series we'll try and support better migration with some tooling, but this was from 1.0.2 to 1.0.3 which is dated by the end of the alpha series we should have 1.0.3 -> 1.1 conversions down pat though > Build history not showing after 1.0.2 to 1.0.3 migration > > > Key: CONTINUUM-668 > URL: http://jira.codehaus.org/browse/CONTINUUM-668 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: hpux, winxp >Reporter: Shinobu Kawai > Fix For: 1.1-alpha-1 > > > After following the instructions at > http://maven.apache.org/continuum/upgrade.html and upgrading to 1.0.3, the > build history screen shows nothing. Builds after the upgrade are showing. > However, if I directly put the URL for a specific build, I can view the > results. > Like this: > http://localhost:8080/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=534&id=14 -- 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: (CONTINUUM-703) Display of last build date on Project Summary page
[ http://jira.codehaus.org/browse/CONTINUUM-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-703: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 I think this information was added a while back by kenney when he worked with the build queues, hopefully just need to percolate it up > Display of last build date on Project Summary page > -- > > Key: CONTINUUM-703 > URL: http://jira.codehaus.org/browse/CONTINUUM-703 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Paul Spencer > Fix For: 1.1-alpha-2 > > > Adding the date of the last build to the Project Summary pages would be very > useful. At the very least the user can tell how log it has been since a > build was attempted for a project without having to view the builds history. -- 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: (CONTINUUM-464) cannot use a build.xml file in a folder
[
http://jira.codehaus.org/browse/CONTINUUM-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-464:
--
Fix Version/s: (was: 1.1-alpha-1)
1.1-alpha-2
> cannot use a build.xml file in a folder
> ---
>
> Key: CONTINUUM-464
> URL: http://jira.codehaus.org/browse/CONTINUUM-464
> Project: Continuum
> Issue Type: Bug
> Components: Core system
>Affects Versions: 1.0.1
> Environment: running on Linux Debian
>Reporter: Adam Kiezun
> Fix For: 1.1-alpha-2
>
>
> In an ANT project, I have a build.xml file in a subfolder ("experiments") of
> the main project folder.
> The webinterface form says I can specify a relative path to that file but
> "experiments/build.xml" does not work.
--
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: (CONTINUUM-704) Make columns on the project summary page sortable.
[ http://jira.codehaus.org/browse/CONTINUUM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-704: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 I think we are using the extreme components table there so it should be a matter of enabling that > Make columns on the project summary page sortable. > -- > > Key: CONTINUUM-704 > URL: http://jira.codehaus.org/browse/CONTINUUM-704 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Paul Spencer > Fix For: 1.1-alpha-2 > > > Making the columns on the Project Summary page sortable would be very > useful. As an example you could sort by build status, which is the first > column of icons, to see all of the failed builds group together. I added an > issue requesting the addition of build date column. Sorting by this column > will allow the user to see the order projects where build. -- 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: (CONTINUUM-559) Keep connection on servers between each messages
[ http://jira.codehaus.org/browse/CONTINUUM-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-559: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Keep connection on servers between each messages > > > Key: CONTINUUM-559 > URL: http://jira.codehaus.org/browse/CONTINUUM-559 > Project: Continuum > Issue Type: Improvement > Components: Notifier - IRC, Notifier - Jabber, Notifier - MSN >Affects Versions: 1.0.2 >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-# > > > Actually, notifiers do a connection/disconnection with the server for each > messages sent. We must start a connection when we send the first message and > disconnect when continuum stops. -- 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: (CONTINUUM-99) The Continuum Python CLI has to be configurable
[ http://jira.codehaus.org/browse/CONTINUUM-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-99: - Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > The Continuum Python CLI has to be configurable > --- > > Key: CONTINUUM-99 > URL: http://jira.codehaus.org/browse/CONTINUUM-99 > Project: Continuum > Issue Type: Improvement >Reporter: Trygve Laugstol > Fix For: 1.1-alpha-# > > > In particular the host and port to talk to has to be configured. -- 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: (CONTINUUM-475) threshold for number of build results to display
[ http://jira.codehaus.org/browse/CONTINUUM-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-475: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > threshold for number of build results to display > > > Key: CONTINUUM-475 > URL: http://jira.codehaus.org/browse/CONTINUUM-475 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > -- 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: (CONTINUUM-570) Documentation to add for war deployment in several container
[ http://jira.codehaus.org/browse/CONTINUUM-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-570: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Documentation to add for war deployment in several container > > > Key: CONTINUUM-570 > URL: http://jira.codehaus.org/browse/CONTINUUM-570 > Project: Continuum > Issue Type: Task > Components: Documentation >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-2 > > > - Need doc for Jetty 6 > - Need doc for Jetty 5 > - Need doc for Tomcat 4 > - Need doc for Tomcat 5 > - Need doc for Weblogic (if we can access to a server) > - Need doc for Websphere (if we can access to a server) > - [Add other 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
[jira] Updated: (CONTINUUM-272) add installation configuration to white site
[ http://jira.codehaus.org/browse/CONTINUUM-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-272: -- Fix Version/s: (was: 1.1-alpha-1) Future > add installation configuration to white site > > > Key: CONTINUUM-272 > URL: http://jira.codehaus.org/browse/CONTINUUM-272 > Project: Continuum > Issue Type: Sub-task >Reporter: Brett Porter > Fix For: Future > > -- 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: (CONTINUUM-445) document how to obtain and build a yahoo messenger notifier
[ http://jira.codehaus.org/browse/CONTINUUM-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-445: -- Fix Version/s: (was: 1.1-alpha-1) Future > document how to obtain and build a yahoo messenger notifier > --- > > Key: CONTINUUM-445 > URL: http://jira.codehaus.org/browse/CONTINUUM-445 > Project: Continuum > Issue Type: Improvement > Components: Documentation, Notification Subsystem >Reporter: Brett Porter > Fix For: Future > > > we can't distribute due to license, but we should document how to obtain and > build this, and put it somewhere that it can be licensed properly. > Maybe we should consider rewriting the base library from scratch using a > BSD/ASL license? > (I'm primarily a Yahoo! user, so... :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-310) customisable email templates
[ http://jira.codehaus.org/browse/CONTINUUM-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-310: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > customisable email templates > > > Key: CONTINUUM-310 > URL: http://jira.codehaus.org/browse/CONTINUUM-310 > Project: Continuum > Issue Type: New Feature > Components: Notifier - Mail >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > some things that the ActiveMQ folks would like to be able to do: > - customise the appearance of the host name > - customise the from/to addresses (this should already be possible) > - customise the subject of the email > Being able to configure the last two, and provide your own email templates is > possible the best way to go about this. -- 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: (CONTINUUM-546) Translate Continuum interface
[ http://jira.codehaus.org/browse/CONTINUUM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-546: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Translate Continuum interface > - > > Key: CONTINUUM-546 > URL: http://jira.codehaus.org/browse/CONTINUUM-546 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-# > > -- 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: (CONTINUUM-273) implement screens for installation configuration
[ http://jira.codehaus.org/browse/CONTINUUM-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-273: -- Fix Version/s: (was: 1.1-alpha-1) Future > implement screens for installation configuration > > > Key: CONTINUUM-273 > URL: http://jira.codehaus.org/browse/CONTINUUM-273 > Project: Continuum > Issue Type: Sub-task > Components: Web interface >Reporter: Brett Porter > Fix For: Future > > -- 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: (CONTINUUM-59) design and implement configurable installations
[ http://jira.codehaus.org/browse/CONTINUUM-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-59: - Fix Version/s: (was: 1.1-alpha-1) Future > design and implement configurable installations > > > Key: CONTINUUM-59 > URL: http://jira.codehaus.org/browse/CONTINUUM-59 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.0-alpha-4 >Reporter: Jason van Zyl > Fix For: Future > > > Need to be able to build for any desired JDK, maven and ant installation -- 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: (CONTINUUM-305) Update all continuum web tests for the new web interface
[ http://jira.codehaus.org/browse/CONTINUUM-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-305. - Resolution: Fixed there are web tests in place now, sure they can be expanded on but that doesn't need a issue any longer > Update all continuum web tests for the new web interface > > > Key: CONTINUUM-305 > URL: http://jira.codehaus.org/browse/CONTINUUM-305 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-359) define all html properties in css instead of in html code like size for
[ http://jira.codehaus.org/browse/CONTINUUM-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-359: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > define all html properties in css instead of in html code like size for > > > > Key: CONTINUUM-359 > URL: http://jira.codehaus.org/browse/CONTINUUM-359 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: 1.1-alpha-# > > -- 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: (CONTINUUM-646) Add a way to associate definitions with schedules
[ http://jira.codehaus.org/browse/CONTINUUM-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-646. - Resolution: Fixed build definition are triggered by a schedule now so this should be supported > Add a way to associate definitions with schedules > - > > Key: CONTINUUM-646 > URL: http://jira.codehaus.org/browse/CONTINUUM-646 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Matthew Beermann > Fix For: 1.1-alpha-1 > > > It would be very handy if there was a way to associate build definitions with > build schedules. In conjunction with Maven's profiles, this would allow (for > example) the ability to run certain reports only during the nightly build, > instead of every single time the project builds. > This might depend on CONTINUUM-294. -- 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: (CONTINUUM-417) Don't list the entire revision history for a changed file, just the most recent changes
[ http://jira.codehaus.org/browse/CONTINUUM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-417: -- Fix Version/s: (was: 1.1-alpha-1) Future > Don't list the entire revision history for a changed file, just the most > recent changes > --- > > Key: CONTINUUM-417 > URL: http://jira.codehaus.org/browse/CONTINUUM-417 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0 >Reporter: David Blevins > Fix For: Future > > > Instead, think of allowing ViewCVS or FishEye to be configured and create > links. > It is *extremely* annoying the way it is now. On OpenEJB, when a project.xml > file is changed, we get this: > modules/core/project.xml > djencks GERONIMO-1123 add dependencies on plugin where it is used > djencks GERONIMO-1123 Use dependency plugin to generate > geronimo-service.xml files > djencks GERONIMO-880 Remove bouncy-castle in favor of some copied > classes > ammulder branches: 1.58.2; Sync with Geronimo changes - ServerInfo now > an interface - Moved management API interfaces to a new module > djencks GERONIMO-784 and refactor xmlbeans2 plugin for move to xmlbeans > djencks GERONIMO-782 step 1 remove xfire. Also clean up dependencies a > bit > dain Removed openorb/tmporb Removed tools jar hack Removed all stub/tie > compiler code since is used openorb > djencks GERONIMO-738 move to xmlbeans v2 > dain Added KernelFactory for pluggable kernel Kernel is now an interface > Moved Kernel implementation to basic kernel Converted JMX registry and config > manager to plain old gbeans (they do not require special access to the > kernel) Magic attributes such as state and enabled are now accessed via > kernel methods Use of getAttribute and invoke for magic attributes and state > transition is now deprecated Cleaned up cruft in GBean infos such as > declaration of non existent attributes Upgraded to newest CGLIB, asm, and > commons-collections > djencks update dependency versions > maguroRemoved reliance on tmporb-ssl > djencks Add NamedUsernamePasswordCredential and supporting > infrastructure to allow configuring security info for ws client calls > maguroChange dependency to geronimo-spec-corba. > maguroUpdated to use the default Sun ORB. > dain Convert remaining tmporb references to openorb > dain Switch to tmporb > chirino Implemented WSDL port address replacment. > dblevins First run of axis integration. more to sew up yet. > maguroIntermediate CORBA checkin. > djencks simple MEJB implementation, some changes to help MEJB > deployment > dblevins Revising the WSContainer to better support rpc/encoded strictly > against a lightweight WSDL->Java mapping. Added validation for lightweigth > mappings. Added ability to download the WSDL via > http://foobar.com/someservice?wsdl > maguroNeeded for CSIv2 > djencks Partial implementation of GERONIMO-450. GBean names are > (mostly) constructed like jsr-77 names and xml config usually only needs to > specify namePart and optionally type > chirino The geronimo security package now depends on activeio and no > longer on geronimo remoting. > dblevins Basic soap rpc/encoded deployment and container support along > with a general revamping of the networkservice stacks. > dblevins The asm and bouncycastle dependencies had hardcoded versions > dblevins Reformatted > dain Replaced xml parsed entities for dependency version numbers with > project.properties > djencks GERONIMO-402, 464. Split openejb and security deployment code > into separate modules > djencks GERONIMO-403/405/418 Split builders out of j2ee, naming, and > jetty > maguroIntermediate CORBA checkin > dblevins Updated castor version to 0.9.5.3 > maguroCORBA jars > djencks don't make duplicate xmlbeans-generated classes. Work around > problem with xmlbeans imported group refs > dblevins Added AppClient support for JNDI > dain Consolidated all version numbers into etc/version-info.ent > djencks Add timer support to session and mdbs. (entities still todo). > Adapt to TransactionContextManager. Adapt to deploying with external plan. > > djencks Upgrade conncurrent to 1.3.4 > djencks Implement message driven bean deployment and some of > message-destination refs. Update to howl 0.1.3 > dain Updated the spec jar version number
[jira] Closed: (CONTINUUM-465) Lot's of unexpected input errors
[ http://jira.codehaus.org/browse/CONTINUUM-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-465. - Resolution: Fixed just a mess of debugging from maven scm, I think this was toned out in subsequent releases of maven-scm > Lot's of unexpected input errors > > > Key: CONTINUUM-465 > URL: http://jira.codehaus.org/browse/CONTINUUM-465 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.1 > Environment: Linux Fedora Core 4 > SVN with SSPI authentication > SVN repository has external links >Reporter: Tom Skinner > Fix For: 1.1-alpha-1 > > > Getting a bunch of these errors in my wrapper.log during builds. > INFO | jvm 2| 2005/11/21 14:29:58 | 2005-11-21 14:29:58,841 [Thread-1] > INFO ScmManager - Working directory: > /local/ci/continuum-1.0.1/apps/continuum/working-directory/6 > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,108 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,109 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,109 > [Thread-212] DEBUG ScmManager - Fetching external item > into 'hpsps-inside/src/main/java' > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,110 > [Thread-212] INFO ScmManager - Unknown file status: 'F'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,110 > [Thread-212] DEBUG ScmManager - External at revision 2150. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,279 > [Thread-212] INFO ScmManager - Unknown file status: 'E'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,279 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - Fetching external item > into 'hpsps-inside/src/main/webapp' > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] INFO ScmManager - Unknown file status: 'F'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - External at revision 2150. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] INFO ScmManager - Unknown file status: 'E'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - Fetching external item > into 'hpsps-outside/src/main/java' > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] INFO ScmManager - Unknown file status: 'F'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - External at revision 2150. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] INFO ScmManager - Unknown file status: 'E'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-2
[jira] Updated: (CONTINUUM-701) Continuum obscures the output of CVS exceptions
[
http://jira.codehaus.org/browse/CONTINUUM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-701:
--
Fix Version/s: (was: 1.1-alpha-1)
1.1-alpha-#
> Continuum obscures the output of CVS exceptions
> ---
>
> Key: CONTINUUM-701
> URL: http://jira.codehaus.org/browse/CONTINUUM-701
> Project: Continuum
> Issue Type: Bug
> Components: SCM
>Affects Versions: 1.0.3
>Reporter: Alex Mayorga Adame
> Fix For: 1.1-alpha-#
>
>
> The error in Continuum on initial checkout of a Maven 2 project under
> Continuum 1.0.3 when using following syntax of SCM:
> {code:none}
> scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module
> {code}
> Error in Continuum is as follows and doesn't represent real issue on mvn
> scm:checkout goal:
> {code:none}
> Provider message: The cvs command failed.
> Command output:
> --
> port/repository: no such repository
> cvs checkout: authorization failed: server host rejected access to
> port/repository for user user
> cvs checkout: used empty password; try "cvs login" with a real password
> ---
> {code}
> The Continuum logs for this error:
> {code:none}
> INFO | jvm 1 | 2006/05/11 01:00:08 | 2006-05-11 01:00:08,921 [Thread-2] WARN
> SQL - Object with id "0" not found !
> INFO | jvm 1 | 2006/05/11 01:00:08 | 2006-05-11 01:00:08,950 [Thread-2] INFO
> ContinuumScm - Checking out project: 'Maven Webapp Archetype', id: '12' to
> '/usr/bin/continuum/continuum-1.0.3/bin/solaris/../../apps/continuum/working-directory/12'.
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,026 [Thread-2] DEBUG
> ScmManager - cvsRoot: :pserver:[EMAIL PROTECTED]:port/repository
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,027 [Thread-2] DEBUG
> ScmManager - passFile: /opt/continuum-user/.cvspass
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,029 [Thread-2] DEBUG
> ScmManager - cvsroot :pserver:[EMAIL PROTECTED]:port/repository already exist
> in /opt/continuum-user/.cvspass. SKIPPED.
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,033 [Thread-2] INFO
> ScmManager - Executing: cvs -z3 -f -d :pserver:[EMAIL
> PROTECTED]:port/repository -q checkout -d 12 path/to/module
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,033 [Thread-2] INFO
> ScmManager - Working directory:
> /usr/bin/continuum/continuum-1.0.3/apps/continuum/working-directory
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,653 [Thread-2] WARN
> ContinuumScm - Error while checking out the code for project: 'Maven Webapp
> Archetype', id: '12' to
> '/usr/bin/continuum/continuum-1.0.3/bin/solaris/../../apps/continuum/working-directory/12'.
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,655 [Thread-2] WARN
> ContinuumScm - Command output: port/repository: no such repository
> INFO | jvm 1 | 2006/05/11 01:00:09 | cvs checkout: authorization failed:
> server host rejected access to port/repository for user user
> INFO | jvm 1 | 2006/05/11 01:00:09 | cvs checkout: used empty password; try
> "cvs login" with a real password
> INFO | jvm 1 | 2006/05/11 01:00:09 |
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,655 [Thread-2] WARN
> ContinuumScm - Provider message: The cvs command failed.
> {code}
> The _real_ error behind this:
> {code:none}
> bash-2.03$ mvn scm:checkout -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'scm'.
> [INFO]
>
> [INFO] Building Maven Webapp Archetype
> [INFO]task-segment: [scm:checkout] (aggregator-style)
> [INFO]
>
> [INFO] [scm:checkout]
> [INFO] Removing /export1/eae/am74839/pvr/target/checkout
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Cannot run checkout command :
>
> Embedded error: Exception while executing SCM command.
> cvs: not found
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Cannot run checkout
> command :
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.ex
[jira] Updated: (CONTINUUM-169) relocate database and temp data
[ http://jira.codehaus.org/browse/CONTINUUM-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-169: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > relocate database and temp data > --- > > Key: CONTINUUM-169 > URL: http://jira.codehaus.org/browse/CONTINUUM-169 > Project: Continuum > Issue Type: Bug > Components: Database >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > the temp checkouts should be named something sensible and configurable - > defaulted to something outside of the continuum install if possible > the database should likewise be stored outside of the continuum install -- 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: (CONTINUUM-712) Download as text link in Build result page does not work from URL send in notification mails
[
http://jira.codehaus.org/browse/CONTINUUM-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-712:
--
Fix Version/s: (was: 1.1-alpha-1)
1.1-alpha-2
> Download as text link in Build result page does not work from URL send in
> notification mails
> -
>
> Key: CONTINUUM-712
> URL: http://jira.codehaus.org/browse/CONTINUUM-712
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0.3
>Reporter: Shinobu Kawai
> Fix For: 1.1-alpha-2
>
>
> When you go to the Build result page from the link sent by the notification
> mail, the URL is something like this:
> http://localhost:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/21/buildId/704
> Since the id and buildId are not in request parameter form, the "Download as
> text" link becomes something like this:
> http://localhost:8080/continuum/servlet/browse?file=$requestUtil.getParameter('id')/${requestUtil.getParameter('buildId')}.log.txt
> Therefore, failing to download.
--
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: (CONTINUUM-261) When building Ant and Shell project, still look for pom.xml
[ http://jira.codehaus.org/browse/CONTINUUM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-261: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > When building Ant and Shell project, still look for pom.xml > --- > > Key: CONTINUUM-261 > URL: http://jira.codehaus.org/browse/CONTINUUM-261 > Project: Continuum > Issue Type: New Feature > Components: Core system >Reporter: Trygve Laugstol > Fix For: 1.1-alpha-# > > > This is useful for those who want to make it easy to configure their > Continuum instance. > At least read notifiers, dependencies and developers. -- 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: (CONTINUUM-68) Make Continuum control database initialization and destruction.
[ http://jira.codehaus.org/browse/CONTINUUM-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-68: - Fix Version/s: (was: 1.1-alpha-1) Future > Make Continuum control database initialization and destruction. > --- > > Key: CONTINUUM-68 > URL: http://jira.codehaus.org/browse/CONTINUUM-68 > Project: Continuum > Issue Type: Improvement > Components: Core system, Database >Affects Versions: 1.0-alpha-1 >Reporter: Trygve Laugstol > Assigned To: Trygve Laugstol > Fix For: Future > > > Continuum should be able to autodetect if the application has been properly > configured and if not autmatically set up a database given a configuration > either from the user or from a configuration file. This should possibly be > integrated into the web view so the application won't start up all the way > without a proper storage. -- 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: (CONTINUUM-256) trace memory leak with yourkit
[ http://jira.codehaus.org/browse/CONTINUUM-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-256: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > trace memory leak with yourkit > -- > > Key: CONTINUUM-256 > URL: http://jira.codehaus.org/browse/CONTINUUM-256 > Project: Continuum > Issue Type: Bug > Components: Core system >Reporter: Brett Porter > Fix For: 1.1-alpha-2 > > Attachments: nohup.out.tar.gz > > > continuum has been spitting OOME in our test environment -- 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: (CONTINUUM-436) prefill the build definition
[ http://jira.codehaus.org/browse/CONTINUUM-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-436: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > prefill the build definition > > > Key: CONTINUUM-436 > URL: http://jira.codehaus.org/browse/CONTINUUM-436 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0 >Reporter: Wim Deblauwe > Fix For: 1.1-alpha-# > > > when adding a build definition it would be nice if it is pre-filled with the > values of the previous one. Most of the time the values will probably be the > same (wel at least the location of the pom.xml). It might save some typing > (and the possibility for typo's!). Or you can have a clone button or > something. -- 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: (CONTINUUM-724) Make the group name update itself when the build runs.
[ http://jira.codehaus.org/browse/CONTINUUM-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-724: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Make the group name update itself when the build runs. > -- > > Key: CONTINUUM-724 > URL: http://jira.codehaus.org/browse/CONTINUUM-724 > Project: Continuum > Issue Type: Sub-task > Components: Integration - Maven 2 >Affects Versions: 1.0.3 >Reporter: Adrian > Fix For: 1.1-alpha-# > > > The group name never updates itself throughout the projects life, even if I > change the name in the pom.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: (CONTINUUM-830) Use redirect after post instead of forward when page refresh is common but could cause re-triggering
[ http://jira.codehaus.org/browse/CONTINUUM-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-830: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Use redirect after post instead of forward when page refresh is common but > could cause re-triggering > > > Key: CONTINUUM-830 > URL: http://jira.codehaus.org/browse/CONTINUUM-830 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: John Casey > Fix For: 1.1-alpha-# > > > When I force a build, Continuum simply forwards me to the summary page, > instead of redirecting. This means that if I use the browser's refresh > function, I'll force another build, since the URL is the one used to trigger > the build. If you're doing many things at once, it means you have to look at > the URL before you punch reload, or you may wind up rebuilding again. > It'd be nice to simply redirect the user to the summary page, so reloads of > the page wouldn't trigger fresh builds. -- 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: (CONTINUUM-817) The generated output in the Working Copy page displays the wrong content
[ http://jira.codehaus.org/browse/CONTINUUM-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-817: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > The generated output in the Working Copy page displays the wrong content > > > Key: CONTINUUM-817 > URL: http://jira.codehaus.org/browse/CONTINUUM-817 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-alpha-1 > Environment: Linux FC4, Maven 2.0.4, JDK 1.5 >Reporter: Napoleon Esmundo C. Ramirez > Fix For: 1.1-alpha-2 > > > The Working Copy page displays html codes (which it shouldn't). > In the page source, is generated as > and so on... -- 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: (CONTINUUM-708) Continuum can not correctly locate modules for multiple module maven 2 projects.
[ http://jira.codehaus.org/browse/CONTINUUM-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-708. - Resolution: Won't Fix by design, emm offered a solution though > Continuum can not correctly locate modules for multiple module maven 2 > projects. > > > Key: CONTINUUM-708 > URL: http://jira.codehaus.org/browse/CONTINUUM-708 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.3 > Environment: Windows 2000, CVS running on windows >Reporter: Paul Grove > Fix For: 1.1-alpha-1 > > > We have a Maven 2 project with mutiple modules we call this the reactor > project with the reactor POM. We have the below directory structure for > development > brokerApp > | > |POM.xml (reactor pom) > | > |-webapp1 > ||-POM.xml > | > |-coreAPI > ||-POM.xml > | > |-appEAR > ||-POM.xml > groupId = com..conceptlabs.brokerApp > In the reactor POM we have the following modules > > webapp1 > coreAPI > appEAR > > When we build and deploy from the Maven 2 reactor POM, we get the following > directory structure in our Maven 2 repository. > http://conceptlabs1.intranet..co.uk:8080/m2-repo/snapshots/com//conceptlabs/brokerApp/ > > Under this root we have the following > |-brokerApp > ||-1.0-SNAPSHOT > | |-brokerApp-1.0-20060523.162030-1.pom > | > |-webapp1 > ||-1.0-SNAPSHOT > | |-webapp1-1.0-20060523.162030-1.pom > | > |-coreAPI > ||-1.0-SNAPSHOT > ||-coreAPI-1.0-20060523.162030-1.pom > | > |-appEAR > ||-1.0-SNAPSHOT > ||-appEAR-1.0-20060523.162030-1.pom > Continuum can not correctly locate modules for multiple module maven 2 > projects. > This is the proper location as produced by doing a Maven 2 mvn deploy > http://conceptlabs1.intranet..co.uk:8080/m2-repo/snapshots/com//conceptlabs/brokerApp/webapp1/1.0-SNAPSHOT/webapp1-1.0-20060523.162030-1.pom > but Continuum for some reason looks here? > http://conceptlabs1.intranet..co.uk:8080/m2-repo/snapshots/com//conceptlabs/brokerApp/brokerApp/1.0-SNAPSHOT/brokerApp-1.0-20060523.1620/webapp1/pom.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: (CONTINUUM-1028) Continuum needs to be restarted to pick changes in settings.xml for some operations
[ http://jira.codehaus.org/browse/CONTINUUM-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1028: --- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Continuum needs to be restarted to pick changes in settings.xml for some > operations > --- > > Key: CONTINUUM-1028 > URL: http://jira.codehaus.org/browse/CONTINUUM-1028 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 1.1-alpha-2 > > > start continuum > add a m2 project with a parent pom that it's only in the internal repo > -> error parent pom not found > change settings.xml to point to internal repo > add a m2 project with a parent pom that it's only in the internal repo > -> error parent pom not found > restart continuum > add a m2 project with a parent pom that it's only in the internal repo > -> it works, downloads all the parent poms 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: (CONTINUUM-860) multiple email addresses delimited with commas causes AddressException
[ http://jira.codehaus.org/browse/CONTINUUM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-860: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > multiple email addresses delimited with commas causes AddressException > -- > > Key: CONTINUUM-860 > URL: http://jira.codehaus.org/browse/CONTINUUM-860 > Project: Continuum > Issue Type: Bug > Components: Notifier - Mail >Reporter: Adam Hardy > Fix For: 1.1-alpha-2 > > > Email notification fails with a "javax.mail.internet.AddressException: > Illegal route-addr in string" exception when a comma-delimited list of email > addresses is used. > See the linked message for the pom.xml node for an example. > There is a work-around, see this thread in user list > http://mail-archives.apache.org/mod_mbox/maven-continuum-users/200609.mbox/browser -- 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: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-509: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Shinobu Kawai > Fix For: 1.1-alpha-2 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- 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: (CONTINUUM-1142) Refactor notifiers APIs
[ http://jira.codehaus.org/browse/CONTINUUM-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1142: --- Fix Version/s: (was: 1.1-alpha-1) Future > Refactor notifiers APIs > --- > > Key: CONTINUUM-1142 > URL: http://jira.codehaus.org/browse/CONTINUUM-1142 > Project: Continuum > Issue Type: Improvement > Components: Notification Subsystem >Reporter: Emmanuel Venisse > Fix For: Future > > > Actually, when a user want to add a notifier, he need to implement a notifier > project, then he need to modify a jsp (notifierSelectType.jsp) and few java > action classes for the recipients rendering. > I'd like to see a complete refactoring of the notifiers APIs with a notifier > manager that return the role-hint of each notifiers and the name of them for > the jsp, and an utility class by notifier that return a formatted string for > recipients. > With that, all actions/JSPs (except specific notifier actions/JSPs like > IrcProjectNotifierEditAction.java/notifierIrc.jsp) will be independant of a > specific notifier and user that want to add a new notifier won't need to > modify continuum files -- 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: (CONTINUUM-841) Notifier get duplicated during builds
[ http://jira.codehaus.org/browse/CONTINUUM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-841: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Notifier get duplicated during builds > - > > Key: CONTINUUM-841 > URL: http://jira.codehaus.org/browse/CONTINUUM-841 > Project: Continuum > Issue Type: Bug > Components: Notification Subsystem >Affects Versions: 1.0.3 > Environment: maven 1.1-beta3 on Windows 2000 / JDK 5 >Reporter: nicolas de loof > Fix For: 1.1-alpha-# > > Attachments: wrapper.log > > > I receive my failure mail 12 times. Looking at the project configuration in > continuum, my notifier eMail is registered 12 times. I delete all and > register a fresh new email account. After some (failed) builds, it gets > duplicated as notifier. -- 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: (CONTINUUM-1184) using plexus-contextualizer to setup port in jetty
[ http://jira.codehaus.org/browse/CONTINUUM-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1184: --- Fix Version/s: 1.1-alpha-1 > using plexus-contextualizer to setup port in jetty > -- > > Key: CONTINUUM-1184 > URL: http://jira.codehaus.org/browse/CONTINUUM-1184 > Project: Continuum > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy > Fix For: 1.1-alpha-1 > > Attachments: CONTINUUM-1184 > > > Actually when using continuum-plexus-runtime, in order to change the http > port : the application must be started (in order to be extracted), stopped. > Then configuration file can be changed. > With this patch the jetty port can be set before the first start. > I have deployed all needed artifacts in codehaus snapshot repo. > -- > Olivier -- 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: (CONTINUUM-620) Changes section in Continuum build result and build e-mail only show blank columns and file names
[ http://jira.codehaus.org/browse/CONTINUUM-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-620: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Changes section in Continuum build result and build e-mail only show blank > columns and file names > - > > Key: CONTINUUM-620 > URL: http://jira.codehaus.org/browse/CONTINUUM-620 > Project: Continuum > Issue Type: Bug > Components: Core system, SCM, Web interface >Affects Versions: 1.0.3 > Environment: Using the version from continuum-20060306.143000.tar.gz > Windows XP SP2 >Reporter: Mang Lau > Assigned To: Emmanuel Venisse > Fix For: 1.1-alpha-# > > > The Changes section in the build results screen show 3 blank columns and the > name of the changed file in the 4th column. This is also true in the build > e-mail Continuum sends out after the build. I believe that the columns are > supposed to show the author and any check-in comments from the 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
[jira] Updated: (CONTINUUM-1054) IllegalStateException stack adding pom
[ http://jira.codehaus.org/browse/CONTINUUM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1054: --- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > IllegalStateException stack adding pom > -- > > Key: CONTINUUM-1054 > URL: http://jira.codehaus.org/browse/CONTINUUM-1054 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 1.1-alpha-2 > > > Adding a m2 pom from a web location causes this stack trace, although seems > to work fine > 2006-12-13 10:46:07,109 [SocketListener0-1] INFO DispatcherUtils >- Unable to find 'webwork.multipart.saveDir' property setting. Defaulting > to javax.servlet.context.tempdir > 2006-12-13 10:46:07,156 [SocketListener0-1] WARN MultiPartRequest >- Item is a file upload of 0 size, ignoring > 2006-12-13 10:46:07,156 [SocketListener0-1] ERROR DispatcherUtils >- Error setting character encoding to 'UTF-8' - ignoring. > java.lang.IllegalStateException: getReader() or getInputStream() called > at > org.mortbay.jetty.servlet.ServletHttpRequest.setCharacterEncoding(ServletHttpRequest.java:602) > at > javax.servlet.ServletRequestWrapper.setCharacterEncoding(ServletRequestWrapper.java:112) > at > com.opensymphony.webwork.dispatcher.DispatcherUtils.prepare(DispatcherUtils.java:392) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:160) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) > at org.mortbay.http.HttpServer.service(HttpServer.java:909) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) -- 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: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-994. - Resolution: Fixed this was fixed with the jpox release of 1.1.6 which in turn created some other issues with postgres (but not this one :), however there is a new jpox version coming very soon which fixes those issues which we will upgrade to promptly > New indexes created during continuum startup when using postgresql > -- > > Key: CONTINUUM-994 > URL: http://jira.codehaus.org/browse/CONTINUUM-994 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Richard C. L. Li > Fix For: 1.1-alpha-1 > > > I used postgresql 8.1.4 with continuum and everytime when continuum startup, > it creates a set of indexes. I configured to restart continuum once a day > and after 2 months it generated tens of indexes in every table. > I guessed this maybe the problem of the the UPPER CASE of the table and > column names, this may make the detection of indexes fails and the JDO > recreate everytime it startup. > Workaround: after starting continuum for the first time and set the property > org.jpox.autoCreateSchema to false so that indexes will not recreated. -- 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: (CONTINUUM-709) Runtime error during recording in datanase
[ http://jira.codehaus.org/browse/CONTINUUM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-709: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Runtime error during recording in datanase > -- > > Key: CONTINUUM-709 > URL: http://jira.codehaus.org/browse/CONTINUUM-709 > Project: Continuum > Issue Type: Bug > Components: Core system, Database >Affects Versions: 1.0.3 > Environment: solaris 9 >Reporter: Olivier Lamy > Fix For: 1.1-alpha-2 > > > I have the following strack trace : > ERROR 22001: A truncation error was encountered trying to shrink VARCHAR > '/OTAReceiver/trunk/ota-rec > eiver-parsing/src/main/java/com/ac&' to length 255. > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown > Source) > at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown > Source) > at > org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown > Source) > at > org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown > Source) > at > org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown > Source) > at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown > Source) > at org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > at org.jpox.store.StoreManager.insert(StoreManager.java:739) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) > at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) > at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.jav > a:1146) > at > org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1201) > at > org.codehaus.plexus.jdo.PlexusJdoUtils.makePersistent(PlexusJdoUtils.java:97) > at > org.apache.maven.continuum.store.JdoContinuumStore.makePersistent(JdoContinuumStore.java: > 524) > at > org.apache.maven.continuum.store.JdoContinuumStore.addBuildResult(JdoContinuumStore.java: > 265) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.makeAndStoreBuildResult > (DefaultBuildController.java:443) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildContr > oller.java:298) > The result is strange : > - in the build history the build is marked as succesfull > - in the project summary I have the red icon which says failed but no mail > received > -- > Olivier -- 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: (CONTINUUM-530) HTML encode the build output
[ http://jira.codehaus.org/browse/CONTINUUM-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-530: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > HTML encode the build output > > > Key: CONTINUUM-530 > URL: http://jira.codehaus.org/browse/CONTINUUM-530 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Trygve Laugstol > Fix For: 1.1-alpha-2 > > Attachments: continuum-snapshot.png, htmlEscape.patch > > > Currently the output is included verbatim, which means that the browser will > try to parse any XML that's in the build output. See the attached snapshot > versus the actual output: > -- SNIP -- > > identifier="swrefVrecordVdatasetZaddressVcollectionZne_adresseVkeysZ158428" > typeName="View of GAB Adresse"> > Norge > 158428 > 219 > Bærum > KYRRES VEI > 19 > C > > 1369 > STABEKK > > ID="swrefVgeometryVdatasetZaddressVcollectionZne_adresseVfieldZposisjonVlocalZTrueVkeysZ536885020X662636086X690767" > swldy:world="swrefVworldVdatasetZaddressVuniverseZ2VworldZ0"> > -409769860,-357023026 > > > > ID="swrefVgeometryVdatasetZaddressVcollectionZne_adresseVfieldZannotationVlocalZTrueVkeysZ536885020X662636069X690770" > swldy:world="swrefVworldVdatasetZaddressVuniverseZ2VworldZ0"> > -409769860,-357022026 > 19C > 0.00 > 22 > > 1.00 > > > > > > > > -- SNIP -- -- 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: (CONTINUUM-605) Add a RecipientSource that derives addresses from the change list
[ http://jira.codehaus.org/browse/CONTINUUM-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-605: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Add a RecipientSource that derives addresses from the change list > - > > Key: CONTINUUM-605 > URL: http://jira.codehaus.org/browse/CONTINUUM-605 > Project: Continuum > Issue Type: New Feature > Components: Notification Subsystem >Reporter: John Didion > Fix For: 1.1-alpha-2 > > Attachments: change-list-recipient-source.diff, > ChangeListRecipientSource.diff > > > CruiseControl has the nice feature of only sending notification email to > those users who submitted the changes in the build. I missed that feature > when switching to Continuum, so I implemented it. It compiles a list of scm > ids from the change list, then matches them against the developers in the POM > to get email addresses. It delegates to the default RecipientSource if there > is no change list. -- 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: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-44: - Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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: (CONTINUUM-713) re-enabling xfire?
[ http://jira.codehaus.org/browse/CONTINUUM-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-713: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > re-enabling xfire? > -- > > Key: CONTINUUM-713 > URL: http://jira.codehaus.org/browse/CONTINUUM-713 > Project: Continuum > Issue Type: Wish >Affects Versions: 1.0.2, 1.0.3 >Reporter: Laszlo Hornyak Kocka > Fix For: 1.1-alpha-# > > > As far as I remember XFire-based ws interface was disabled by default from > continuum in release 1.0.2, and I did not manange to re-enable it. > XFire 1.1 has motm support, so the build data can be streamed to clients e.g. > for IDE-plugins... -- 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: (CONTINUUM-821) The Project.getBuildResults() method returns an empty list
[
http://jira.codehaus.org/browse/CONTINUUM-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-821:
--
Fix Version/s: (was: 1.1-alpha-1)
1.1-alpha-2
> The Project.getBuildResults() method returns an empty list
> --
>
> Key: CONTINUUM-821
> URL: http://jira.codehaus.org/browse/CONTINUUM-821
> Project: Continuum
> Issue Type: Bug
> Components: XMLRPC Interface
>Affects Versions: 1.0.3
> Environment: JDK 1.5.0_07, Linux (Fedora Core 5)
>Reporter: John Smart
> Fix For: 1.1-alpha-2
>
>
> The Project.getBuildResults() method returns an empty list. The unit test is
> shown here:
> @Test
> public void testGetProjectBuildResults() throws XmlRpcException,
> IOException {
> String url = "http://localhost:8000/continuum";;
> ProjectsReader pr = new ProjectsReader( new URL( url ) );
>
> Project[] projects = projects = pr.readProjects();
> //
> // Note: All the projects on the localhost server have builds
> //
> for ( Project project : projects){
>
> List buildResults = project.getBuildResults();
> //
> // Builds have been defined
> //
> assertTrue(project.getBuildDefinitions().size() > 0);
> //
> // Builds have been done
> //
> assertTrue(project.getBuildNumber() > 0);
> //
> // We can access the build results
> //
> assertNotNull(buildResults);
> //
> // Test fails here:
> //
> assertTrue(buildResults.size() > 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: (CONTINUUM-1155) Continuum should be able to use cached username/password credentials when the scm provider supports it
[ http://jira.codehaus.org/browse/CONTINUUM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1155: --- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Continuum should be able to use cached username/password credentials when the > scm provider supports it > -- > > Key: CONTINUUM-1155 > URL: http://jira.codehaus.org/browse/CONTINUUM-1155 > Project: Continuum > Issue Type: New Feature > Components: Environmental >Affects Versions: 1.0.3 >Reporter: Edwin Punzalan > Assigned To: Lester Ecarma > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-1155.patch > > -- 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: (CONTINUUM-729) Conitnnum buids project twice when clicking on 'build now'
[ http://jira.codehaus.org/browse/CONTINUUM-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-729: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > Conitnnum buids project twice when clicking on 'build now' > -- > > Key: CONTINUUM-729 > URL: http://jira.codehaus.org/browse/CONTINUUM-729 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: Continuum-1.0.3 / Maven-2.0.4 / JSE 1.5.0 update 06 / > Windows Server 2003 >Reporter: Thomas Cornet > Fix For: 1.1-alpha-2 > > Attachments: continuum-log.txt > > > Whenever I click on the 'build now' link in the project list or on the 'build > now' button in the project info page, the selected project is build twice. If > I let the scheduler do its work, all is fine and build once when necessary, > the problem occurs only when I force the build -- 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: (CONTINUUM-740) Replace JDO/JPOX
[ http://jira.codehaus.org/browse/CONTINUUM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-740: -- Fix Version/s: (was: 1.1-alpha-1) Future not even on the table for alpha release or 1.1 I don't think > Replace JDO/JPOX > > > Key: CONTINUUM-740 > URL: http://jira.codehaus.org/browse/CONTINUUM-740 > Project: Continuum > Issue Type: Task > Components: Database >Reporter: Emmanuel Venisse > Fix For: Future > > > We'll look at JPA as a substitute. -- 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: (CONTINUUM-751) Create a table tag
[ http://jira.codehaus.org/browse/CONTINUUM-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-751: -- Fix Version/s: (was: 1.1-alpha-1) Future > Create a table tag > -- > > Key: CONTINUUM-751 > URL: http://jira.codehaus.org/browse/CONTINUUM-751 > Project: Continuum > Issue Type: Task > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Emmanuel Venisse >Priority: Minor > Fix For: Future > > > This tag will replace in jsp -- 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: (CONTINUUM-341) times should display the timezone and be a configurable format
[ http://jira.codehaus.org/browse/CONTINUUM-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-341: -- Fix Version/s: (was: 1.1-alpha-1) Future > times should display the timezone and be a configurable format > -- > > Key: CONTINUUM-341 > URL: http://jira.codehaus.org/browse/CONTINUUM-341 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Brett Porter >Priority: Minor > Fix For: Future > > -- 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: (CONTINUUM-731) New Example: XML-RPC Calls in Groovy
[ http://jira.codehaus.org/browse/CONTINUUM-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-731: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > New Example: XML-RPC Calls in Groovy > > > Key: CONTINUUM-731 > URL: http://jira.codehaus.org/browse/CONTINUUM-731 > Project: Continuum > Issue Type: Improvement > Components: XMLRPC Interface >Reporter: Michael Rimov >Priority: Minor > Fix For: 1.1-alpha-2 > > Attachments: getprojects.groovy > > > I spend the evening learning about XML-RPC in general, Groovy Client > Implementations, and finally, pulled it alltogether with some calls to my own > continuum repository. > So I figured I could at least clean up my work and submit it as a potential > for a documentation example. > It will have to be updated for authentication as soon as CONTINUUM-684 is > fixed, but until then I hope this helps. > -Mike (R) -- 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: (CONTINUUM-150) Continuum site needs screenshots
[ http://jira.codehaus.org/browse/CONTINUUM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-150: -- Fix Version/s: (was: 1.1-alpha-1) Future > Continuum site needs screenshots > > > Key: CONTINUUM-150 > URL: http://jira.codehaus.org/browse/CONTINUUM-150 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Reporter: Henri Yandell >Priority: Minor > Fix For: Future > > > The Continuum site needs to show screenshots to better sell Continuum to > interested parties. -- 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: (CONTINUUM-344) Complains about not finding m2 and then builds successfully
[ http://jira.codehaus.org/browse/CONTINUUM-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-344: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Complains about not finding m2 and then builds successfully > --- > > Key: CONTINUUM-344 > URL: http://jira.codehaus.org/browse/CONTINUUM-344 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0-beta-1 > Environment: Linux >Reporter: Mark Hobson >Priority: Minor > Fix For: 1.1-alpha-# > > Attachments: wrapper.log > > > When adding a m2 project it complains that it can't find m2 in the attached > log and then proceeds to build successfully. > m2 is actually at /usr/local/m2/bin/m2 and can be run from the command line > as the continuum user. -- 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: (CONTINUUM-711) Option to Update Maven Plugins on next build
[ http://jira.codehaus.org/browse/CONTINUUM-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-711: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Option to Update Maven Plugins on next build > > > Key: CONTINUUM-711 > URL: http://jira.codehaus.org/browse/CONTINUUM-711 > Project: Continuum > Issue Type: New Feature > Components: Core system >Affects Versions: 1.1-alpha-1 > Environment: Standalone server running continuum >Reporter: Lee Meador >Priority: Minor > Fix For: 1.1-alpha-# > > > It would be nice to click something to either kick off a mvn build with the > -U option or to cause the next build to use that option. (-U will force maven > 2 to update all used plugins from a remote repository if there is a newer > version available.) > If you are running continuum in an environment where it is difficult to do > that from the command line either because the command would be long and error > prone or because the environment is difficult to get to, it isn't easy to do > that updating. -- 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: (CONTINUUM-643) NPE in addPathInfo
[ http://jira.codehaus.org/browse/CONTINUUM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-643: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > NPE in addPathInfo > -- > > Key: CONTINUUM-643 > URL: http://jira.codehaus.org/browse/CONTINUUM-643 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.1-alpha-2 > > > I get this exception in the logs, coming from a velocity template: > java.lang.NullPointerException > at > org.codehaus.plexus.summit.util.UriBuilder.addPathInfo(UriBuilder.java:263) > It seems to be when the database might already have problems, so I'm > deferring this until WW is in place to see if it goes way. It doesn't seem to > have any major side effects. -- 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: (CONTINUUM-718) Build definitions, notifiers erroneously lost or deleted if created during initial checkout
[ http://jira.codehaus.org/browse/CONTINUUM-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-718: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Build definitions, notifiers erroneously lost or deleted if created during > initial checkout > --- > > Key: CONTINUUM-718 > URL: http://jira.codehaus.org/browse/CONTINUUM-718 > Project: Continuum > Issue Type: Bug > Components: Core system, Notification Subsystem >Affects Versions: 1.0.3 > Environment: Fedora Core 4, Java 1.4.2 also Windows XP Java 1.4.2. >Reporter: Jon Andersen >Priority: Minor > Fix For: 1.1-alpha-# > > > Immediately after a project is created, and the project name clicked on, an > automatic checkout happens. If the project is large, this checkout may take > some time to complete. During the checkout, build definitions and notifiers > may be added using the normal web interface. HOWEVER, these build > definitions and notifiers disappear once the checkout completes. > To reproduce the problem: > 1. Create a new (shell) project that does a large checkout. > 2. While the automatic checkout is proceeding, create a build definition > and/or a notifier. > 3. Wait until the checkout completes. > 4. Refresh the view of the project - what happened to the build definition > and notifier?! > Workaround: > Create the build definitions and notifiers AFTER the initial checkout > completes. -- 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: (CONTINUUM-693) Should have different "queued for build" icons for forced vs. scheduled.
[ http://jira.codehaus.org/browse/CONTINUUM-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-693: -- Fix Version/s: (was: 1.1-alpha-1) Future > Should have different "queued for build" icons for forced vs. scheduled. > > > Key: CONTINUUM-693 > URL: http://jira.codehaus.org/browse/CONTINUUM-693 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Christian Gruber >Priority: Minor > Fix For: Future > > > The current icon has a clock, so maybe a new icon with the gear and an > exclamation point over it? Something that indicates that something is > queued for a forced build. Also, the same exclamation point could be overtop > of the "now building" icon for forced builds. -- 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: (CONTINUUM-385) run.sh on MacOS X fails with problem in wrapper
[ http://jira.codehaus.org/browse/CONTINUUM-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-385: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > run.sh on MacOS X fails with problem in wrapper > --- > > Key: CONTINUUM-385 > URL: http://jira.codehaus.org/browse/CONTINUUM-385 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0 > Environment: Mac OS X 10.4 >Reporter: Mark Donszelmann >Priority: Minor > Fix For: 1.1-alpha-# > > > > Hi > > > > running continuum 1.0 on MacOS X 10.4 gives me the following when > > started > > as: > > > > bin/macosx/runs.h start > > > > or > > > > bin/macosx/runs.h console > > > > -- Output > > Running continuum... > > Removed stale pid file: ./continuum.pid wrapper | --> Wrapper Started > > as Console > > dyld: lazy symbol binding failed: Symbol not found: _ftime > > Referenced from: /Users/duns/java/continuum-1.0/bin/macosx/wrapper > > Expected in: /usr/lib/libcrypto.0.9.7.dylib > > > > dyld: Symbol not found: _ftime > > Referenced from: /Users/duns/java/continuum-1.0/bin/macosx/wrapper > > Expected in: /usr/lib/libcrypto.0.9.7.dylib > > > > Trace/BPT trap > > > > -- > > > > while if I run > > > > bin/plexus.sh > > > > all works fine (but only interactively. -- 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: (CONTINUUM-619) shell command line not preserved
[ http://jira.codehaus.org/browse/CONTINUUM-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-619: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > shell command line not preserved > > > Key: CONTINUUM-619 > URL: http://jira.codehaus.org/browse/CONTINUUM-619 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.2 >Reporter: Lee Meador >Priority: Minor > Fix For: 1.1-alpha-# > > > I have a shell project. > The executable is 'mvn.bat' and the argument is the long string: > -f 00Build/pom.xml --settings "C:\Program Files\Apache Software > Foundation\continuum-1.0.2\bin\win32\conf\settings.xml" clean install > This argument shows up on the "info" tab for the project correctly. There is > only one build for that project. > When I click "edit" to change the argument, the whole argument (as shown > above) does not appear in the text box on that web page. It's not that it > doesn't fit in the box and I would have to get it to scroll left and right to > see the text. It just ends where the first double quote is. I see the first > part of the argument and the last word shown is '--settings'. > I can work around it by copying the argument on the "info" tab to my > clipboard and then pasting it after I click the 'edit' link. -- 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: (CONTINUUM-524) editing mail notifier during a build
[ http://jira.codehaus.org/browse/CONTINUUM-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-524: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > editing mail notifier during a build > > > Key: CONTINUUM-524 > URL: http://jira.codehaus.org/browse/CONTINUUM-524 > Project: Continuum > Issue Type: Bug > Components: Notifier - Mail >Affects Versions: 1.0.2 > Environment: W2K, sp4, 1.7 GHz, 1 GB RAM >Reporter: Michael Fiedler >Priority: Minor > Fix For: 1.1-alpha-# > > > While editing the mail notifier entry, but not every time, an exception would > occur. When I did get an exception, it is similar to this: > jvm 1| 2005-12-20 13:03:34,253 [Thread-1] WARN SQL > - Object with id "1069" not found ! > jvm 1| 2005-12-20 13:03:34,503 [Thread-1] WARN SQL > - Object with id "1069" not found ! > jvm 1| 2005-12-20 13:03:34,643 [Thread-1] ERROR BuildController > - Error while building project. > jvm 1| javax.jdo.JDODataStoreException: Put request failed : INSERT INTO > PROJECTNOTIFIER_CONFIGURATION (STRING_VAL,ID_OID,STRING_KEY) VALUES (?,?,?) > jvm 1| at > org.jpox.store.rdbms.scostore.NormalMapStore.put(NormalMapStore.java:467) > jvm 1| at org.jpox.sco.Map.put(Map.java:709) > jvm 1| at > org.jpox.sco.SCOUtils.updateMapWithMapKeysValues(SCOUtils.java:626) > jvm 1| at org.jpox.sco.Map.attachCopy(Map.java:376) > jvm 1| at > org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107) > jvm 1| at > org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) > jvm 1| at > org.apache.maven.continuum.model.project.ProjectNotifier.jdoProvideField(ProjectNotifier.java) > jvm 1| at > org.apache.maven.continuum.model.project.ProjectNotifier.jdoProvideFields(ProjectNotifier.java) > jvm 1| at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) > jvm 1| at > org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) > jvm 1| at > org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) > jvm 1| at > org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) > jvm 1| at org.jpox.sco.List.attachCopy(List.java:326) > jvm 1| at > org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107) > jvm 1| at > org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) > jvm 1| at > org.apache.maven.continuum.model.project.Project.jdoProvideField(Project.java) > jvm 1| at > org.apache.maven.continuum.model.project.Project.jdoProvideFields(Project.java) > jvm 1| at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) > jvm 1| at > org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) > jvm 1| at > org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) > jvm 1| at > org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) > jvm 1| at org.jpox.sco.List.attachCopy(List.java:326) > jvm 1| at > org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107) > jvm 1| at > org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) > jvm 1| at > org.apache.maven.continuum.model.project.ProjectGroup.jdoProvideField(ProjectGroup.java) > jvm 1| at > org.apache.maven.continuum.model.project.ProjectGroup.jdoProvideFields(ProjectGroup.java) > jvm 1| at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) > jvm 1| at > org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) > jvm 1| at > org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446) > jvm 1| at > org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644) > jvm 1| at > org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:120) > jvm 1| at > org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394) > jvm 1| at > org.apache.maven.continuum.model.project.Project.jdoProvideField(Project.java) > jvm 1| at > org.apache.maven.continuum.model.project.Project.jdoProvideFields(Project.java) > jvm 1| at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732) > jvm 1| at > org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518) > jvm 1|
[jira] Updated: (CONTINUUM-702) Ability to show build output only if build fails
[ http://jira.codehaus.org/browse/CONTINUUM-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-702: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# I thought it worked like this already... > Ability to show build output only if build fails > > > Key: CONTINUUM-702 > URL: http://jira.codehaus.org/browse/CONTINUUM-702 > Project: Continuum > Issue Type: Wish > Components: Notifier - Mail >Reporter: Shinobu Kawai >Priority: Minor > Fix For: 1.1-alpha-# > > > It would be great if it was possible to toggle whether the build output is > put in the notification. > Depending on the project, build outputs can be several MBs, and we already > have a link to the online report. Instead of clogging the developer's > mailboxes with success outputs, an option to show the output only if the > build fails would be nice. -- 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: (CONTINUUM-698) using tooverride causes email for each notification set
[ http://jira.codehaus.org/browse/CONTINUUM-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-698: -- Fix Version/s: (was: 1.1-alpha-1) Future > using tooverride causes email for each notification set > --- > > Key: CONTINUUM-698 > URL: http://jira.codehaus.org/browse/CONTINUUM-698 > Project: Continuum > Issue Type: Bug > Components: Notifier - Mail >Affects Versions: 1.0.3 >Reporter: Brian Fox >Priority: Minor > Fix For: Future > > > If you set the to email override, this causes 1 email to be sent to this > address for each mail notification set in the pom. It's probably doing a > blind substitution without checking if it's already sent to that address -- 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: (CONTINUUM-706) XML-RPC Server does not support addition of BuildDefinitions
[ http://jira.codehaus.org/browse/CONTINUUM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-706: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-2 > XML-RPC Server does not support addition of BuildDefinitions > - > > Key: CONTINUUM-706 > URL: http://jira.codehaus.org/browse/CONTINUUM-706 > Project: Continuum > Issue Type: Bug > Components: XMLRPC Interface >Affects Versions: 1.0.3 > Environment: Win XP SP2 > jdk1.5.0_06 >Reporter: Adam Leggett >Priority: Minor > Fix For: 1.1-alpha-2 > > > When attempting to add a maven 2 project via ProjectsReader.addProject() it > is not possible to add a build definition. > This means that subsequent calls to ProjectReader.buildproject fail. -- 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: (CONTINUUM-404) add a way for admins to access the log from the web interface
[ http://jira.codehaus.org/browse/CONTINUUM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-404: -- Fix Version/s: (was: 1.1-alpha-1) Future > add a way for admins to access the log from the web interface > - > > Key: CONTINUUM-404 > URL: http://jira.codehaus.org/browse/CONTINUUM-404 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.0 > Environment: running on linux debian >Reporter: Adam Kiezun > Assigned To: Emmanuel Venisse >Priority: Minor > Fix For: Future > > > add a way for admins to see the logs from the web interface. -- 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: (CONTINUUM-911) Canceling the edit config page would go back to login page.
[ http://jira.codehaus.org/browse/CONTINUUM-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-911: -- Fix Version/s: (was: 1.1-alpha-1) 1.1-alpha-# > Canceling the edit config page would go back to login page. > --- > > Key: CONTINUUM-911 > URL: http://jira.codehaus.org/browse/CONTINUUM-911 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Teodoro Cue Jr. > Assigned To: Teodoro Cue Jr. >Priority: Minor > Fix For: 1.1-alpha-# > > > Canceling the edit config page after login will go back to the login 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
