[jira] Closed: (MEV-510) Missing StrutsTestCase for servlet api 2.4
[ http://jira.codehaus.org/browse/MEV-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-510. -- Assignee: Carlos Sanchez Resolution: Incomplete Check http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Missing StrutsTestCase for servlet api 2.4 > -- > > Key: MEV-510 > URL: http://jira.codehaus.org/browse/MEV-510 > Project: Maven Evangelism > Issue Type: New Feature > Components: Missing POM >Reporter: Victor Letunovsky > Assigned To: Carlos Sanchez > > Missing in repository last version of StrutsTestCase 2.1.3 for JSP API 1.2 > and Servlet API 2.4. > StrutsTestCase hosted on sourceforge.net: > http://strutstestcase.sourceforge.net/ (files: > http://sourceforge.net/project/showfiles.php?group_id=39190) -- 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: (MEV-507) Remove ch/qos/logback/logback directory on ibiblio
[ http://jira.codehaus.org/browse/MEV-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-507. -- Resolution: Fixed those folders have been already removed > Remove ch/qos/logback/logback directory on ibiblio > -- > > Key: MEV-507 > URL: http://jira.codehaus.org/browse/MEV-507 > Project: Maven Evangelism > Issue Type: Task >Reporter: Ceki Gulcu > Assigned To: Carlos Sanchez > > The "ch/qos/logback/logback/" directory [1] on ibiblio exists due to a > syncronisation error. However, looking at [1], many logback users > errorneously think that the latest logback version on ibiblio is v0.5. Could > please remove the "ch/qos/logback/logback/" directory on the ibiblio repo? > Please note that this directory should have never existed. > Many thanks in advance, > [1] http://mirrors.ibiblio.org/pub/mirrors/maven2/ch/qos/logback/logback/ -- 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: (MEV-509) commons-discovery-0.2 invalid version
[ http://jira.codehaus.org/browse/MEV-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-509. -- Assignee: Carlos Sanchez Resolution: Fixed > commons-discovery-0.2 invalid version > - > > Key: MEV-509 > URL: http://jira.codehaus.org/browse/MEV-509 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Xavier Hanin > Assigned To: Carlos Sanchez > > The version od commons-discovery-0.2 seems to be incorrect in the following > pom: > http://repo1.maven.org/maven2/commons-discovery/commons-discovery/0.2/commons-discovery-0.2.pom > I believe it should be 0.2, but it's 0.2-dev -- 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: (MAVENUPLOAD-1407) Please sync with jguard repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1407. --- Assignee: Carlos Sanchez Resolution: Fixed > Please sync with jguard repo > > > Key: MAVENUPLOAD-1407 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1407 > Project: maven-upload-requests > Issue Type: Task >Reporter: charles gay > Assigned To: Carlos Sanchez > > Please sync with jguard's repo. The shell can be found at > http://jguard.sf.net/net.sf.jguard.sh > thanks for your great work!! > cheers, > Charles GAY. > www.jguard.net -- 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: (MAVENUPLOAD-1412) Springframework repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89798 ] Carlos Sanchez commented on MAVENUPLOAD-1412: - it is synce autmatically, what's the problem? > Springframework repository sync > --- > > Key: MAVENUPLOAD-1412 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1412 > Project: maven-upload-requests > Issue Type: Task >Reporter: Avi Cherry > > It appears that the spring framework is not being automatically synced with > the project's repository. The included URL points at the project's maven > repository. 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-811) Documentation of Deployment Repository Directory
[ http://jira.codehaus.org/browse/CONTINUUM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-811: -- Fix Version/s: 1.1-alpha-# > Documentation of Deployment Repository Directory > > > Key: CONTINUUM-811 > URL: http://jira.codehaus.org/browse/CONTINUUM-811 > Project: Continuum > Issue Type: Bug > Components: Documentation >Affects Versions: 1.0.3 >Reporter: Scott Cytacki > Fix For: 1.1-alpha-# > > > I can't find any good documenation on how the deployment repository directory > works. As far as I can tell continuum magically runs a special mvn deploy > goal after any sucess build. > But I can't find this in the log. Also it isn't clear how this relates to an > explicit mvn deploy. -- 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-814) change ContinuumActionSupport to ContinuumConfigurationInterceptor
[ http://jira.codehaus.org/browse/CONTINUUM-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-814. - Assignee: Jesse McConnell Resolution: Fixed Fix Version/s: 1.1-alpha-1 did this ages ago > change ContinuumActionSupport to ContinuumConfigurationInterceptor > -- > > Key: CONTINUUM-814 > URL: http://jira.codehaus.org/browse/CONTINUUM-814 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Jesse McConnell > Assigned To: Jesse McConnell > Fix For: 1.1-alpha-1 > > Attachments: configuration-interceptor.patch > > > a bit ago I submitted a patch in CONTINUUM-810 that added a > ContinuumActionSupport class that leveraged the prepare interceptor to always > call a prepare() method checking if the continuum configuration was > initialized and if it wasn't to redirect to configuration. > well shortly after that brett pointed me at how he had solved it in mrm so I > figured I would just back out that previous patch and redo it his way.. > that is what this patch does, makes the continuum configuration checking > match that of mrm. > as a byproduct of this the xwork.xml file now has multiple packages and > namespaces in it, so I took the oppurtunity to move all of the jsps into > src/main/webapp/jsp and the configuration ones into src/main/webapp/jsp/admin > this is largely cosmetic but it cleans up the -webapp module in ide's and I > was in the xwork.xml file anyway. -- 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-815) directory configuration
[ http://jira.codehaus.org/browse/CONTINUUM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-815: -- Fix Version/s: 1.1-alpha-# > directory configuration > --- > > Key: CONTINUUM-815 > URL: http://jira.codehaus.org/browse/CONTINUUM-815 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.0.3 >Reporter: Torsten Curdt > Fix For: 1.1-alpha-# > > > When I was installing maven it was not clear what the directories are for > that I had to specify. > - working directory > - build output directory > - local repository > The installation guide should explain values like these. Especially awkward > is that the builds happen in the working area - not in the build output area. > Just needs some documentation. -- 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: (MEV-455) bad checksums on repo1.maven.org
[ http://jira.codehaus.org/browse/MEV-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89800 ] Daniel Kulp commented on MEV-455: - It looks like there is a bug in the repositorytools:copy-repository plugin/goal. The md5's are correct in the staging area on people.apache.org. (~dkulp/public_html/stage_gpg/org/apache/maven/plugins/maven-gpg-plugin/1.0-alpha-3) It looks like the copy from staging to release screwed up the md5 and sha1 files. I'm not sure how that would have happened. I'll go ahead and copy the correct ones over manually. That kind of sucks. However, someone with access to the repositorytools plugin should look into the issue to make sure it's fixed. > bad checksums on repo1.maven.org > > > Key: MEV-455 > URL: http://jira.codehaus.org/browse/MEV-455 > Project: Maven Evangelism > Issue Type: Bug >Reporter: nicolas de loof > Assigned To: Daniel Kulp > > I'm using Archiva as a maven proxy, that verify checksums when downloading > artifact. My archiva.log shwo some invalid checksum on http://repo1.maven.org > : > commons-chain/commons-chain/1.1/commons-chain-1.1.pom > org/codehaus/plexus/plexus-compiler/1.5.2/plexus-compiler-1.5.2.pom > commons-validator/commons-validator/1.3.0/commons-validator-1.3.0-sources.jar > struts/struts/1.2.9/struts-1.2.9-sources.jar > junit/junit/3.8.2/junit-3.8.2.pom > junit/junit/3.8.2/junit-3.8.2.jar > junit/junit/3.8.2/junit-3.8.2-sources.jar > junit/junit/3.8.2/junit-3.8.2-javadoc.jar > easymock/easymock/1.2_Java1.3/easymock-1.2_Java1.3-sources.jar > org/codehaus/plexus/plexus-compilers/1.5.2/plexus-compilers-1.5.2.pom > org/apache/maven/surefire/surefire-providers/2.0/surefire-providers-2.0.pom > org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml > it/could/webdav/0.4/webdav-0.4.pom > com/jcraft/jsch/0.1.27/jsch-0.1.27.pom > com/jcraft/jsch/0.1.27/jsch-0.1.27.jar > it/could/webdav/0.4/webdav-0.4.pom > it/could/webdav/0.4/webdav-0.4.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-816) runas in run script
[ http://jira.codehaus.org/browse/CONTINUUM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-816: -- Fix Version/s: 1.1-alpha-# > runas in run script > --- > > Key: CONTINUUM-816 > URL: http://jira.codehaus.org/browse/CONTINUUM-816 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.3 > Environment: linux >Reporter: Torsten Curdt > Fix For: 1.1-alpha-# > > > When I installed continuum I've changed the "runas" user in the run script > but then started it via "run.sh console". Unfortunately the console mode is > ignoring the "runas" user setting so when I was trying to run it with "run.sh > start" afterwards I was getting exception because the continuum user could > not access the files. After fixing the ownerships everything was ok again. > I suggest that "run.sh console" should also use the "runas" 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-955) deployment repository should be required and have a default in initial continuum setup.
[ http://jira.codehaus.org/browse/CONTINUUM-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-955: -- Fix Version/s: 1.1-alpha-2 > deployment repository should be required and have a default in initial > continuum setup. > --- > > Key: CONTINUUM-955 > URL: http://jira.codehaus.org/browse/CONTINUUM-955 > Project: Continuum > Issue Type: Improvement > Components: Core system, Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Christian Gruber > Fix For: 1.1-alpha-2 > > Attachments: make_deployment_dir_default.diff, > make_deployment_dir_default.diff > > > Deployment repository should be required and have a default in initial > continuum setup. If it does not, and empty string is provided, then it > deploys to crazy places, and during jetty:run execution, it deploys in places > that really messes up the project folders. > Patch provided. -- 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-924) Add ability to edit group
[ http://jira.codehaus.org/browse/CONTINUUM-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-924: -- Fix Version/s: 1.1-alpha-# > Add ability to edit group > - > > Key: CONTINUUM-924 > URL: http://jira.codehaus.org/browse/CONTINUUM-924 > Project: Continuum > Issue Type: Sub-task > Components: Project Grouping >Affects Versions: 1.1-alpha-1 >Reporter: Carlos Sanchez > Assigned To: Henry S. Isidro > Fix For: 1.1-alpha-# > > > Now that groups are added it'd be nice to have the ability of changing group > name or moving projects from group. -- 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-564) Change focus of build from projects to Build Definitions
[ http://jira.codehaus.org/browse/CONTINUUM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-564: -- Fix Version/s: Future > Change focus of build from projects to Build Definitions > > > Key: CONTINUUM-564 > URL: http://jira.codehaus.org/browse/CONTINUUM-564 > Project: Continuum > Issue Type: Wish > Components: Core system >Affects Versions: 1.0.2 >Reporter: Geoff Gibbs > Fix For: Future > > > Rather than using projects as the mian focus for continumms build system, why > not use the build definitions? > For example: > Currently If I have a project with 3 build definitions, each scehduled to run > nightly at 1,2 and 3am then the first will be triggered at 1am, the Project > will be in a "Building" state and the cvs update will take place, assuming > changes have been made the required build is then run. > Assume a change is made before 2am. > At 2am the second build definition is triggered and agian the Project will be > in a "Building" state, if I were to view the "Show projects" page now, I > would not know if the first build was taking over an hour or if the second > build is taking place as the focus is on the project, not the build > definition. > Finally at 3am the next build is trigger, but nothing has changed, so the > third build definition is never built. > It seems more sensible for the Show Projects page to be replaced with a show > build definitions page and for the build definitions to be named (currently I > have to examine the output to see which build definition was used for a given > build of a project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1055) Allow a "suspend/activate" semantic on projects, to except them from non-forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1055: --- Fix Version/s: Future > Allow a "suspend/activate" semantic on projects, to except them from > non-forced builds. > > > Key: CONTINUUM-1055 > URL: http://jira.codehaus.org/browse/CONTINUUM-1055 > Project: Continuum > Issue Type: New Feature > Components: Core system, Database, Project Grouping, Web - UI >Affects Versions: 1.1-alpha-1 >Reporter: Christian Gruber > Fix For: Future > > > Currently, if a project is acting up in known ways, there's no way to quiesce > it until the problem is dealt with. On projects where continuum spams a list > on purpose, this can be a sort of "false negative" and can cause people who > can do nothing about the notification to start to stop paying attention. > It would be nice to allow a project to be in either an active or suspended > state, with the option for a project admin (not a normal developer) to > "suspend" the project, so that it will no longer be built. This is highly > risky functionality, but is helpful during project build structure > maintenance, for example, so that people aren't spammed with such false > negative project notifications. > It would also be good to have this on a project group basis. -- 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-1127) logic for whether to build is confusing
[ http://jira.codehaus.org/browse/CONTINUUM-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1127: --- Fix Version/s: 1.1-alpha-# > logic for whether to build is confusing > --- > > Key: CONTINUUM-1127 > URL: http://jira.codehaus.org/browse/CONTINUUM-1127 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > Looking at the logic in DefaultBuildcontroller's shouldBuild( BuildContext > context ), I see some potential problems: > - the second else clause is redundant - shouldBuild is always true at this > point > - the code is confusing - better to default to false, then set to true if > state/oldstate is new or checkedout, or if the build was forced > - move the dependency checking outside the other if. It doesn't need to be > conditional on whether there were changes or not. -- 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-1129) projects can be built out of order if some are already scheduled when a new batch get scheduled
[ http://jira.codehaus.org/browse/CONTINUUM-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1129: --- Fix Version/s: 1.1-alpha-# > projects can be built out of order if some are already scheduled when a new > batch get scheduled > --- > > Key: CONTINUUM-1129 > URL: http://jira.codehaus.org/browse/CONTINUUM-1129 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 >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-1128) continuum doesn't correctly handle SVN property changes as an update
[ http://jira.codehaus.org/browse/CONTINUUM-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1128: --- Fix Version/s: 1.1-alpha-# > continuum doesn't correctly handle SVN property changes as an update > > > Key: CONTINUUM-1128 > URL: http://jira.codehaus.org/browse/CONTINUUM-1128 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-alpha-1 >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > 2007-01-09 15:22:28,137 [Thread-2094] INFO ScmManager - > Unknown file status: ' ' in line U src/test/resources/ > projects/restore-backup-poms/basic-pom/pom.xml.releaseBackup. > 2007-01-09 15:22:28,138 [Thread-2094] INFO ScmManager - > Unknown file status: ' ' in line U src/test/resources/ > projects/restore-backup-poms/pom-with-modules/pom.xml.releaseBackup. > 2007-01-09 15:22:28,138 [Thread-2094] INFO ScmManager - > Unknown file status: ' ' in line U src/test/resources/ > projects/restore-backup-poms/pom-with-modules/subproject1/pom.xml.releaseBackup. > 2007-01-09 15:22:28,138 [Thread-2094] INFO ScmManager - > Unknown file status: ' ' in line U src/test/resources/ > projects/restore-backup-poms/pom-with-modules/subproject2/pom.xml.releaseBackup. > I assume that this update was actually ' U src/...', ie a property update, > not a file update -- 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-1130) can't delete default project group
[ http://jira.codehaus.org/browse/CONTINUUM-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1130: --- Fix Version/s: Future > can't delete default project group > -- > > Key: CONTINUUM-1130 > URL: http://jira.codehaus.org/browse/CONTINUUM-1130 > Project: Continuum > Issue Type: Bug > Components: Core system, Database >Affects Versions: 1.1-alpha-1 >Reporter: Brett Porter > Fix For: Future > > > I don't really want/need this - but after deleting it, it keeps coming back -- 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-826) Need report on disk space usage for continuum growth calculations.
[ http://jira.codehaus.org/browse/CONTINUUM-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-826: -- Affects Version/s: 1.1-alpha-1 Fix Version/s: 1.1-alpha-# > Need report on disk space usage for continuum growth calculations. > -- > > Key: CONTINUUM-826 > URL: http://jira.codehaus.org/browse/CONTINUUM-826 > Project: Continuum > Issue Type: New Feature > Components: Core system, Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Joakim Erdfelt > Fix For: 1.1-alpha-# > > > Need a report that show disk space utilization from a current and historical > point of view, in order to estimate the growth (past, present, and future) of > a large Continuum installation. > The report should contain ... > # Total disk/partition size. > # Total disk utilzation by Continuum and projects managed by Continuum. > # Historical graph of Total disk utilization. > # Total disk space per project. > # Historical graph of disk space per project. > # Total number of Projects. > # Average project disk space utilization. > # Estimated number of projects remaining disk space can assigned to. > (Remaining Disk Space) / ((Average project size) + 1) = (Room for X more > projects) -- 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-829) Summary / project group pages should be a tree view with relationship
[ http://jira.codehaus.org/browse/CONTINUUM-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-829: -- Fix Version/s: 1.1-alpha-# > Summary / project group pages should be a tree view with relationship > -- > > Key: CONTINUUM-829 > URL: http://jira.codehaus.org/browse/CONTINUUM-829 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Reporter: Kenney Westerhof > 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-634) Add notion of top level project with modules to prevent notification floods
[ http://jira.codehaus.org/browse/CONTINUUM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-634: -- Fix Version/s: 1.1-alpha-# > Add notion of top level project with modules to prevent notification floods > --- > > Key: CONTINUUM-634 > URL: http://jira.codehaus.org/browse/CONTINUUM-634 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.3 >Reporter: Vincent Massol > Fix For: 1.1-alpha-# > > > Take the Maven project which has tens of modules. If a change is made in some > core part, then lots of modules get rebuilt generating a flood of > notification emails... > If continuum knew about the list of modules making a project, then it could > decide which module need rebuilding and only send a single email for all > modules belonging to a project after they have been built. -- 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-1017) Project Information tab's link (in projectView while on another tab) doesn't contain the groupId param, and so the link fails
[ http://jira.codehaus.org/browse/CONTINUUM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1017: --- Fix Version/s: 1.1-alpha-1 > Project Information tab's link (in projectView while on another tab) doesn't > contain the groupId param, and so the link fails > - > > Key: CONTINUUM-1017 > URL: http://jira.codehaus.org/browse/CONTINUUM-1017 > Project: Continuum > Issue Type: Bug > Components: Web - UI, Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Christian Gruber > Fix For: 1.1-alpha-1 > > > If you're in a Project view, and you go to, say, build definitions, then you > click on Project Information to return to the main screen for project view, > you get a blank screen. Upon further investigation, I noticed that the > groupId parameter is not set on that action, which is necessary. Manually > adding projectGroupId= on the URL successfully goes to the expected 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
[jira] Updated: (CONTINUUM-834) continuum can get confused if wrong pom url is entered
[ http://jira.codehaus.org/browse/CONTINUUM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-834: -- Fix Version/s: 1.1-alpha-# > continuum can get confused if wrong pom url is entered > -- > > Key: CONTINUUM-834 > URL: http://jira.codehaus.org/browse/CONTINUUM-834 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Brett Porter > Fix For: 1.1-alpha-# > > > on codehaus, the following url was added as a pom: > http://svn.codehaus.org/livetribe/garden/livetribe-jsr223/trunk/pom.xml > this resulted in an HTML index file being downloaded as the file "trunk" to > the temp directory. It obviously fails, but when trying to add the correct > http://svn.codehaus.org/livetribe/garden/livetribe-jsr223/trunk/pom.xml, it > fails because trunk the directory can not be created. > We should remove the temp file if it previously failed. -- 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-977) Create web UI tests for "Add m1 & m2 projects" pages
[ http://jira.codehaus.org/browse/CONTINUUM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-977: -- Affects Version/s: 1.1-alpha-1 Fix Version/s: 1.1-alpha-# > Create web UI tests for "Add m1 & m2 projects" pages > > > Key: CONTINUUM-977 > URL: http://jira.codehaus.org/browse/CONTINUUM-977 > Project: Continuum > Issue Type: Task > Components: Testing >Affects Versions: 1.1-alpha-1 >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM-977-continuum-webapp-test.patch, > continuum-webapp-test-4.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-835) temp files not cleaned up
[ http://jira.codehaus.org/browse/CONTINUUM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-835: -- Fix Version/s: 1.1-alpha-2 > temp files not cleaned up > - > > Key: CONTINUUM-835 > URL: http://jira.codehaus.org/browse/CONTINUUM-835 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.3 >Reporter: Brett Porter > Fix For: 1.1-alpha-2 > > > there are thousands on maven-artifact.*.tmp files in the continuum temp > directory when using 1.0.3. It seems something is not using deleteOnExit -- 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-640) Auto Building triggered by svn commit
[ http://jira.codehaus.org/browse/CONTINUUM-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-640: -- Fix Version/s: 1.1-alpha-# > Auto Building triggered by svn commit > - > > Key: CONTINUUM-640 > URL: http://jira.codehaus.org/browse/CONTINUUM-640 > Project: Continuum > Issue Type: Improvement > Components: SCM >Affects Versions: 1.0.1 >Reporter: Kevin Wang > Fix For: 1.1-alpha-# > > > Should we add the function to support auto build while subversion commit? > just like CruiseContril. -- 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-866) Error parsing out SCM url
[ http://jira.codehaus.org/browse/CONTINUUM-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-866: -- Fix Version/s: 1.1-alpha-2 > Error parsing out SCM url > - > > Key: CONTINUUM-866 > URL: http://jira.codehaus.org/browse/CONTINUUM-866 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 > Environment: Continuum 1.0.3 running on CentOS 4.2 and jdk1.5.0_06 >Reporter: Marty Tremblay > Fix For: 1.1-alpha-2 > > > When trying to add an M2 POM URL (https://username:[EMAIL > PROTECTED]/repos/v6.x/modules.xml), > I get "[ The URL you provided doesn't exist ]" and the following in the logs: > INFO | jvm 1| 2006/09/13 09:54:36 | 2006-09-13 09:54:36,469 > [SocketListener0-0] INFO Validator:url-source - An error is > occurred. > INFO | jvm 1| 2006/09/13 09:54:36 | java.io.IOException: HTTPS hostname > wrong: should be > INFO | jvm 1| 2006/09/13 09:54:36 | at > sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.java:490) > INFO | jvm 1| 2006/09/13 09:54:36 | at > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:415) > INFO | jvm 1| 2006/09/13 09:54:36 | at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:170) > INFO | jvm 1| 2006/09/13 09:54:36 | at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:913) > INFO | jvm 1| 2006/09/13 09:54:36 | at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.formica.util.MungedHttpsURL.isValid(MungedHttpsURL.java:111) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.formica.validation.UrlSourceValidator.validate(UrlSourceValidator.java:63) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.formica.DefaultFormManager.validateElements(DefaultFormManager.java:195) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.formica.DefaultFormManager.validate(DefaultFormManager.java:124) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.formica.DefaultFormManager.validate(DefaultFormManager.java:114) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.formica.action.AbstractEntityAction.execute(AbstractEntityAction.java:107) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) > INFO | jvm 1| 2006/09/13 09:54:36 | at > javax.servlet.http.HttpServlet.service(HttpServlet.java:615) > INFO | jvm 1| 2006/09/13 09:54:36 | at > javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.HttpContext.handle(HttpContext.java:1807) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.HttpContext.handle(HttpContext.java:1757) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.HttpServer.service(HttpServer.java:879) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.HttpConnection.service(HttpConnection.java:789) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) > INFO | jvm 1| 2006/09/13 09:54:36 | at > org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) > INFO | jvm 1| 2006/09/13 09:54:36 |
[jira] Updated: (CONTINUUM-837) POM upload screen says file:// URLs are supported but fails if you try one
[ http://jira.codehaus.org/browse/CONTINUUM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-837: -- Fix Version/s: 1.1-alpha-2 > POM upload screen says file:// URLs are supported but fails if you try one > -- > > Key: CONTINUUM-837 > URL: http://jira.codehaus.org/browse/CONTINUUM-837 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Aaron Mulder > Fix For: 1.1-alpha-2 > > > The POM upload screen lists file:// among the supported URL types. However, > any file:// URL that you try results in a misleading error message. > In fact, the "file" protocol is disabled by default. > This screen should explain that "file" must be manually enabled, and the > resulting error message should say that the "file" protocol is disabled. > Ideally it would point you to the correct place to enable it, and mention > that until you've started continuum for the first time, the config file you > need to edit won't be there (the JAR has to be unpacked first). -- 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-1022) Validaiton Email not working
[ http://jira.codehaus.org/browse/CONTINUUM-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-1022. -- Resolution: Fixed Fix Version/s: 1.1-alpha-1 fixed quite some time ago > Validaiton Email not working > > > Key: CONTINUUM-1022 > URL: http://jira.codehaus.org/browse/CONTINUUM-1022 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Franz Allan Valencia See > Fix For: 1.1-alpha-1 > > > The validation email sent when you register is not working. -- 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-984) Group information in group summary screen mistakenly has the heading "Project Group Actions". Should be "Group Information" or something similar.
[ http://jira.codehaus.org/browse/CONTINUUM-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-984: -- Fix Version/s: 1.1-alpha-1 > Group information in group summary screen mistakenly has the heading "Project > Group Actions". Should be "Group Information" or something similar. > -- > > Key: CONTINUUM-984 > URL: http://jira.codehaus.org/browse/CONTINUUM-984 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Christian Gruber > Fix For: 1.1-alpha-1 > > > Summary says it all. -- 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-1027) Create tearDown for the continuum-webapp-test
[ http://jira.codehaus.org/browse/CONTINUUM-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1027: --- Affects Version/s: 1.1-alpha-1 Fix Version/s: 1.1-alpha-# > Create tearDown for the continuum-webapp-test > - > > Key: CONTINUUM-1027 > URL: http://jira.codehaus.org/browse/CONTINUUM-1027 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1-alpha-1 >Reporter: Franz Allan Valencia See > Fix For: 1.1-alpha-# > > > Some of the tests do not clean themselves. Also, some tests may require > identical tearDown()'s ( or at least, part of it ). It would be nice if > things are reverted back to the default every after tests, and that this be > done in AbstractContinuumTestCase ( to prevent tearDown() duplication ). -- 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-865) Continuum Build maven 1.0 project twice
[ http://jira.codehaus.org/browse/CONTINUUM-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-865: -- Fix Version/s: 1.1-alpha-# > Continuum Build maven 1.0 project twice > --- > > Key: CONTINUUM-865 > URL: http://jira.codehaus.org/browse/CONTINUUM-865 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: Linux red hat enterprise 3 > Firefox 1.5.0 >Reporter: Steve Pigache > Fix For: 1.1-alpha-# > > Attachments: continuum.log.zip, wrapper.log.zip > > > I use continuum with a Maven 1 project > I run the goal clean war and a custom goal When I click on the build button, > the generation of the project is ok but when the generation is finish, a > second build is launch at once. > I don't know if it is a bug or if there is a parameter setting to do to stop > the automatic second run. > It's not a double-clicked problem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-850) Continuum ignores a new given password for a cvs account until the cvsroot is also changed
[ http://jira.codehaus.org/browse/CONTINUUM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-850: -- Fix Version/s: 1.1-alpha-2 > Continuum ignores a new given password for a cvs account until the cvsroot is > also changed > -- > > Key: CONTINUUM-850 > URL: http://jira.codehaus.org/browse/CONTINUUM-850 > Project: Continuum > Issue Type: Bug > Components: SCM, Web interface >Affects Versions: 1.0.3 >Reporter: Peter Kehren > Fix For: 1.1-alpha-2 > > > I changed (only!) the password of a cvs account and set this new password in > a project definition in continuum by the web interface. The next build of the > project did not work, because of a wrong password (no access to cvs was > reported). It seems, that continuum uses the old password although a new > password was set. After changing the cvsroot (replaced ip number by dns > entry; 100% NOT the reason for this error) the cvs system could be accessed; > the new password was used. -- 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-836) Improve HTTP access to POMs for adding a multi-module project
[ http://jira.codehaus.org/browse/CONTINUUM-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-836: -- Fix Version/s: Future > Improve HTTP access to POMs for adding a multi-module project > - > > Key: CONTINUUM-836 > URL: http://jira.codehaus.org/browse/CONTINUUM-836 > Project: Continuum > Issue Type: New Feature > Components: Core system >Affects Versions: 1.0.3 >Reporter: Aaron Mulder > Fix For: Future > > > If you're not using SVN, there's no obvious way to load a multi-module POM > into continuum. > If you point it to a M2 repo, then the child module paths are all resolved > relative to the parent's group/artifact/version/ directory, which doesn't > work (parent-group/parent-artifact/parent-version/child-module-name/...) > If you point it to a file:// URL it doesn't work because that's disabled by > default. > If you're using CVS, there is no clear way to get the POMs into the web -- > perhaps exporting the whole source tree onto an HTTP server, but that's going > to be manual. > Ideally, you could point Continuum to the parent POM in the M2 repository and > it would check out the tree to access the child POMs, which would avoid this > whole issue. -- 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-1015) CLONE -velocity prevents display of date in cvs log
[
http://jira.codehaus.org/browse/CONTINUUM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-1015:
---
Fix Version/s: 1.1-alpha-#
> CLONE -velocity prevents display of date in cvs log
> ---
>
> Key: CONTINUUM-1015
> URL: http://jira.codehaus.org/browse/CONTINUUM-1015
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0
> Environment: WinXP,
> Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2115
> (client/server)
> Server: Concurrent Versions System (CVSNT) 2.0.34 (client/server)
>Reporter: Franck HUGOT
> Fix For: 1.1-alpha-#
>
>
> From the log:
> jvm 1| 2005-11-02 16:52:52,439 [SocketListener0-1] ERROR
> VelocityComponent - Left side of '>' operation is not a valid
> type. It is a class java.lang.Long. Currently only integers (1,2,3...) and
> Integer type is supported. screens/ProjectBuild.vm [line 59, column 31]
> The visible symptom, apart from this log message, is that the change log for
> a build, eg via...
> http://localhost:8081/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=9&id=1
> (insert your own build/project ids) only displays 2 columns: the author and
> the comment. I was taking a closer look at that because the information I'm
> seeing is fairly useless: all changes on the updated files back to the dawn
> of time, in no discernible order. Wondering why the date wasn't displayed too
> I checked the log.
> I believe the offending line is:
> #if ($changeSet.date > 0) $date.format('medium',$changeSet.date) #end
--
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-37) Add a professional user interface
[ http://jira.codehaus.org/browse/CONTINUUM-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-37: - Fix Version/s: Future > Add a professional user interface > - > > Key: CONTINUUM-37 > URL: http://jira.codehaus.org/browse/CONTINUUM-37 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Reporter: Emmanuel Venisse > Fix For: Future > > > I'd like to see a professional interface with some flash components like a > Macromedia Flex interface. > Laszlo provides an open source implementation of this technology (CPL > License). http://www.laszlosystems.com/ > You can see some demo here (http://www.laszlosystems.com/demos/). > The screen creation is very simple, it a very simple xml. > I'll hope you'll be interesting. -- 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-978) add web ui tests for all pages related to schedules
[ http://jira.codehaus.org/browse/CONTINUUM-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-978: -- Affects Version/s: (was: 1.1-alpha-2) 1.1-alpha-1 Fix Version/s: 1.1-alpha-# > add web ui tests for all pages related to schedules > --- > > Key: CONTINUUM-978 > URL: http://jira.codehaus.org/browse/CONTINUUM-978 > Project: Continuum > Issue Type: Test > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Marvin King > Assigned To: Marvin King > Fix For: 1.1-alpha-# > > Attachments: CONTINUUM978-continuum-webapp-test-11082006.patch, > CONTINUUM978-continuum-webapp-test.patch, > CONTINUUM978-maven-web-ui-tests.patch > > Time Spent: 15 minutes > Remaining Estimate: 0 minutes > -- 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-1094) Continuum does not build with Sun JDK 6
[
http://jira.codehaus.org/browse/CONTINUUM-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-1094:
---
Affects Version/s: 1.1-alpha-1
Fix Version/s: 1.1-alpha-1
Component/s: Environmental
> Continuum does not build with Sun JDK 6
> ---
>
> Key: CONTINUUM-1094
> URL: http://jira.codehaus.org/browse/CONTINUUM-1094
> Project: Continuum
> Issue Type: Bug
> Components: Environmental
>Affects Versions: 1.1-alpha-1
> Environment: continuum trunk r490449
> linux 2.6.12
> Sun JDK 6 (build 1.6.0-b105)
>Reporter: Minto van der Sluis
> Fix For: 1.1-alpha-1
>
>
> snippet of the build output (mvn clean install).
> ...
> [INFO]
>
> [INFO] Building Continuum Data Management API
> [INFO]task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Deleting directory
> /home/minto/rommel/svn-src/continuum/continuum-data-management/target
> [INFO] Deleting directory
> /home/minto/rommel/svn-src/continuum/continuum-data-management/target/classes
> [INFO] Deleting directory
> /home/minto/rommel/svn-src/continuum/continuum-data-management/target/test-classes
> [INFO] [plexus:descriptor {execution: generate}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> Compiling 2 source files to
> /home/minto/rommel/svn-src/continuum/continuum-data-management/target/classes
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> Compiling 1 source file to
> /home/minto/rommel/svn-src/continuum/continuum-data-management/target/test-classes
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
> /home/minto/rommel/svn-src/continuum/continuum-data-management/target/surefire-reports
> ---
> T E S T S
> ---
> Running org.apache.maven.continuum.management.DataManagementToolTest
> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 8.348 sec <<<
> FAILURE!
> Results :
> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> Builds with JDK 5 runs just fine.
--
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-798) Modules automatic discovery
[ http://jira.codehaus.org/browse/CONTINUUM-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-798: -- Affects Version/s: 1.1-alpha-1 Fix Version/s: 1.1-alpha-# > Modules automatic discovery > --- > > Key: CONTINUUM-798 > URL: http://jira.codehaus.org/browse/CONTINUUM-798 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Nicolas Cazottes > Assigned To: Jesse McConnell > Fix For: 1.1-alpha-# > > Attachments: add-modules-from-updated-project.diff > > > In the case of using continuum with a parent POM that all projects inherit > from, it should be a great feature to automatically discover addition of new > modules and include them as projects in continuum. > This is already done when the project is created the first time with its POM > URL and the same mechanism should be used when continuum discovers that the > pom has been updated. -- 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-1107) Continuum build failes in continuum-core on a clean system
[ http://jira.codehaus.org/browse/CONTINUUM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1107: --- Fix Version/s: 1.1-alpha-2 > Continuum build failes in continuum-core on a clean system > -- > > Key: CONTINUUM-1107 > URL: http://jira.codehaus.org/browse/CONTINUUM-1107 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Roald Bankras > Fix For: 1.1-alpha-2 > > Attachments: > org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.txt > > > MavenTwoContinuumProjectBuilderTest failes twice: -- 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-1109) Need a way to override all notifications
[ http://jira.codehaus.org/browse/CONTINUUM-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1109: --- Description: It is currently possible to override the "To:" address for all email notifications by setting the element in application.xml. This also needs to be done for IRC notifications, etc. Case in point, if you add Cargo to Continuum, it floods the #cargo channel with notices because there is an IRC notifier configured in Cargo's pom. was: It is currently possible to override the "To:" address for all email notifications by setting the element in application.xml. This also needs to be done for IRC notifications, etc. Case in point, if you add Cargo to Continuum, it floods the #cargo channel with notices because there is an IRC notifier configured in Cargo's pom. Fix Version/s: 1.1-alpha-2 > Need a way to override all notifications > > > Key: CONTINUUM-1109 > URL: http://jira.codehaus.org/browse/CONTINUUM-1109 > Project: Continuum > Issue Type: New Feature > Components: Notifier - AOL, Notifier - IRC, Notifier - Jabber, > Notifier - Mail, Notifier - MSN >Affects Versions: 1.1-alpha-1 >Reporter: Wendy Smoak > Fix For: 1.1-alpha-2 > > > It is currently possible to override the "To:" address for all email > notifications by setting the element in application.xml. > This also needs to be done for IRC notifications, etc. > Case in point, if you add Cargo to Continuum, it floods the #cargo channel > with notices because there is an IRC notifier configured in Cargo's pom. -- 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-687) Option to trigger the SCM system to tag successful builds with a build number or timestamp.
[ http://jira.codehaus.org/browse/CONTINUUM-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-687: -- Fix Version/s: Future > Option to trigger the SCM system to tag successful builds with a build number > or timestamp. > --- > > Key: CONTINUUM-687 > URL: http://jira.codehaus.org/browse/CONTINUUM-687 > Project: Continuum > Issue Type: New Feature > Components: Core system, SCM >Reporter: Christian Gruber > Fix For: Future > > > This is complex, because it would be different for each type. For maven2, > for example, it would be potentially compled on its own, insofar as tagging > is handled quite differently between CVS and SVN (to pick two). I could see > a potential workaround, if build defs were independent within a project, by > using a specific goal (say on a nightly build) and therefor "manually" > invoking scm:tag or something. > In short, I'm not sure if it's better to do this within the build system, or > continuum. Suggestions? Best practices anyone? -- 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-1112) Unable to use DB without username and password
[ http://jira.codehaus.org/browse/CONTINUUM-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1112: --- Fix Version/s: 1.1-alpha-# > Unable to use DB without username and password > -- > > Key: CONTINUUM-1112 > URL: http://jira.codehaus.org/browse/CONTINUUM-1112 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1-alpha-1 > Environment: mysql jdbc driver 5.0.3, mysql server 5.0.24 >Reporter: Carlos Sanchez > Fix For: 1.1-alpha-# > > Attachments: log.txt > > > Changed plexus.conf database definition to use mysql db that anyone can > access (no user / no password) and got an error because it's trying to use a > null username. > java.sql.SQLException: Access denied for user 'null'@'localhost' (using > password: YES) > > jdbc/continuum > javax.sql.DataSource > > > driverClassName > com.mysql.jdbc.Driver > > > url > jdbc:mysql://localhost/test > > > username > > > > password > > > > -- 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-1119) Creating a Group with an existing id errors
[ http://jira.codehaus.org/browse/CONTINUUM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1119: --- Affects Version/s: 1.1-alpha-1 Fix Version/s: 1.1-alpha-2 > Creating a Group with an existing id errors > --- > > Key: CONTINUUM-1119 > URL: http://jira.codehaus.org/browse/CONTINUUM-1119 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-alpha-1 > Environment: svn trunk, Tomcat 5.5 >Reporter: Henri Yandell > Fix For: 1.1-alpha-2 > > > If you create a new group with the same group id as another, you get: > Error Occurred > Show/hide Stack Trace > Clicking on the Show/hide doesn't show anything. A plexus user repeated the > issue and found this in the log: > ERROR Action:addProjectGroup- Error adding project group: Unable to > add the requested project group: groupId already exists. -- 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: (MAVENUPLOAD-1412) Springframework repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89803 ] Avi Cherry commented on MAVENUPLOAD-1412: - The problem is that the latest version of spring in their repository is 2.0.3, whereas the latest version in the maven repository is 2.0-m4. So, things don't seem to be syncing. > Springframework repository sync > --- > > Key: MAVENUPLOAD-1412 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1412 > Project: maven-upload-requests > Issue Type: Task >Reporter: Avi Cherry > > It appears that the spring framework is not being automatically synced with > the project's repository. The included URL points at the project's maven > repository. 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-1118) Adding an M2 project without a password has an odd error
[ http://jira.codehaus.org/browse/CONTINUUM-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1118: --- Fix Version/s: 1.1-alpha-# > Adding an M2 project without a password has an odd error > > > Key: CONTINUUM-1118 > URL: http://jira.codehaus.org/browse/CONTINUUM-1118 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Henri Yandell > Fix For: 1.1-alpha-# > > > If I add an M2 project, and delete the password field when submitting, I get > the following error: > The specified resource isn't a file or the protocol used isn't allowed. > It works fine if I let the password field stay as it is. -- 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-1104) Allow user to choose multiple projects for deletion and delete in one step.
[ http://jira.codehaus.org/browse/CONTINUUM-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1104: --- Fix Version/s: 1.1-alpha-# > Allow user to choose multiple projects for deletion and delete in one step. > --- > > Key: CONTINUUM-1104 > URL: http://jira.codehaus.org/browse/CONTINUUM-1104 > Project: Continuum > Issue Type: Improvement > Components: Web - UI, Web interface >Affects Versions: 1.0.3 >Reporter: Rahul Thakur > Fix For: 1.1-alpha-# > > > Have checkbox controls for each of the listed pojects (and subject to > user/role permissions) to allow deleting multiple projects in one shot. -- 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-1123) XMLStreamException on DataManagementToolTest with jdk6
[ http://jira.codehaus.org/browse/CONTINUUM-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1123: --- Fix Version/s: 1.1-alpha-# Component/s: Environmental > XMLStreamException on DataManagementToolTest with jdk6 > -- > > Key: CONTINUUM-1123 > URL: http://jira.codehaus.org/browse/CONTINUUM-1123 > Project: Continuum > Issue Type: Bug > Components: Environmental >Affects Versions: 1.1-alpha-1 >Reporter: fabrizio giustina > Fix For: 1.1-alpha-# > > > Tests on continuum-data-management are failing on jdk6/windows. Work fine > with jdk 1.5 > --- > Test set: org.apache.maven.continuum.management.DataManagementToolTest > --- > Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 3.219 sec <<< > FAILURE! > testBackupBuilds(org.apache.maven.continuum.management.DataManagementToolTest) > Time elapsed: 1.875 sec <<< ERROR! > org.apache.maven.continuum.ContinuumRuntimeException: Modello failure: unable > to write data to StAX writer > at > org.apache.maven.continuum.management.JdoDataManagementTool.backupBuildDatabase(JdoDataManagementTool.java:92) > at > org.apache.maven.continuum.management.DataManagementToolTest.testBackupBuilds(DataManagementToolTest.java:83) > Caused by: javax.xml.stream.XMLStreamException: Underlying stream encoding > 'Cp1252' and input paramter for writeStartDocument() method 'UTF-8' do not > match. > at > com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) > at > javanet.staxutils.IndentingXMLStreamWriter.writeStartDocument(IndentingXMLStreamWriter.java:142) > at > org.apache.maven.continuum.model.project.io.stax.ContinuumStaxWriter.write(ContinuumStaxWriter.java:87) > at > org.apache.maven.continuum.management.JdoDataManagementTool.backupBuildDatabase(JdoDataManagementTool.java:88) > ... 27 more > testRestoreBuilds(org.apache.maven.continuum.management.DataManagementToolTest) > Time elapsed: 0.765 sec <<< ERROR! > org.apache.maven.continuum.ContinuumRuntimeException: Modello failure: unable > to write data to StAX writer > at > org.apache.maven.continuum.management.JdoDataManagementTool.backupBuildDatabase(JdoDataManagementTool.java:92) > at > org.apache.maven.continuum.management.DataManagementToolTest.testRestoreBuilds(DataManagementToolTest.java:124) > Caused by: javax.xml.stream.XMLStreamException: Underlying stream encoding > 'Cp1252' and input paramter for writeStartDocument() method 'UTF-8' do not > match. > at > com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) > at > javanet.staxutils.IndentingXMLStreamWriter.writeStartDocument(IndentingXMLStreamWriter.java:142) > at > org.apache.maven.continuum.model.project.io.stax.ContinuumStaxWriter.write(ContinuumStaxWriter.java:87) > at > org.apache.maven.continuum.management.JdoDataManagementTool.backupBuildDatabase(JdoDataManagementTool.java:88) > ... 27 more -- 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-1108) Change of Working Directory does not affect existing projects
[ http://jira.codehaus.org/browse/CONTINUUM-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1108: --- Fix Version/s: 1.1-alpha-# > Change of Working Directory does not affect existing projects > - > > Key: CONTINUUM-1108 > URL: http://jira.codehaus.org/browse/CONTINUUM-1108 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-alpha-1 > Environment: 1.1-SNAPSHOT r490629 >Reporter: Wendy Smoak > Fix For: 1.1-alpha-# > > > In Configuration, changing the Working Directory does not affect projects > already in Continuum. It does take effect for newly added projects. > To reproduce: > 1. ChooseConfiguration (under Administration, at left) > 2. Edit, > 3. Change the Working Directory > 4. Save > 5. Stop Continuum > 6. Delete or move the old working copy directory > 7. Start Continuum > 8. Force a build of any project > Now check the old and new working copy directories. Continuum checks out the > project in the old directory, not the new one. -- 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-686) Provide each build definition for a given project with its own checked-out workspace.
[ http://jira.codehaus.org/browse/CONTINUUM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-686: -- Fix Version/s: 1.1-alpha-# > Provide each build definition for a given project with its own checked-out > workspace. > - > > Key: CONTINUUM-686 > URL: http://jira.codehaus.org/browse/CONTINUUM-686 > Project: Continuum > Issue Type: New Feature > Components: Core system >Affects Versions: 1.0.3 >Reporter: Christian Gruber > Fix For: 1.1-alpha-# > > > Each build definition should not work off of the same workspace as another > build definition. Otherwise, the notion of overlapping schedules is > meaningless. > This particularly affects configurations where several build definitions are > defined for varying situations, such as a seperate one for continuous (five > minute loop), one for a daily integration build, one to push the site > nightly, and a "never" scheduled build (scheduled for 2061 or something) that > can be used for full manually triggered builds, but will never build on its > own. These four build defs have different purposes, and change in the source > of one should imply change in the source of another. However, if they share > a workspace, then change in the shared workspace would be masked by the > five-minute-loop schedule, which would (presumably) succeed, thus impeding > any other builds. > Also, the changes between the build at 5:30 and the build at 12:00am would be > large, but if there were fifteen other builds in between because of > continuous build schedules, then the "changes" listing in the build process > will be masked by all those other changes. Having separate workspaces > provides a clean solution to many of the above issues, and allows problems to > be examined in isolation. -- 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-1088) Change Password Next Login is not enforced
[ http://jira.codehaus.org/browse/CONTINUUM-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-1088. -- Resolution: Fixed fixed a while back as a plxredback issue > Change Password Next Login is not enforced > -- > > Key: CONTINUUM-1088 > URL: http://jira.codehaus.org/browse/CONTINUUM-1088 > Project: Continuum > Issue Type: Bug > Components: Web - Security >Affects Versions: 1.1-alpha-1 >Reporter: Wendy Smoak > Assigned To: Jesse McConnell > > When 'Change Password Next Login' is checked, the user is presented with the > Change Password page after logging in. > However, at this point the user is _already_logged in, and is free to > navigate away from this page without ever changing his password. -- 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-983) There should be real "Group Actions" that affect members of the group, and can affect subsets of group members based on selection.
[ http://jira.codehaus.org/browse/CONTINUUM-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-983: -- Fix Version/s: 1.1-alpha-# > There should be real "Group Actions" that affect members of the group, and > can affect subsets of group members based on selection. > -- > > Key: CONTINUUM-983 > URL: http://jira.codehaus.org/browse/CONTINUUM-983 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Christian Gruber > Fix For: 1.1-alpha-# > > > There should be real "Group Actions" that affect members of the group, and > can affect subsets of group members based on selection. > In particular, there should be check-boxes before each member, which can > allow such "group actions" to affect one or more members. Group actions I > envision would include "Build (with default build def)" and > "Remove project from group". Any selected groups would be built or removed. > The current "Remove" button would be moved elsewhere, as it is not about the > contents of the group, but deletes the whole group. Possibly simply making > an "X" remove button on the main list of groups, much the way individual > projects have the same would 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-1156) Continuum will not successfully delete build directories containing symbolic links
[ http://jira.codehaus.org/browse/CONTINUUM-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1156: --- Fix Version/s: 1.1-alpha-# > Continuum will not successfully delete build directories containing symbolic > links > -- > > Key: CONTINUUM-1156 > URL: http://jira.codehaus.org/browse/CONTINUUM-1156 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 > Environment: Linux Fedora Core 5 >Reporter: Steve Pietrowicz > Fix For: 1.1-alpha-# > > Attachments: ContinuumFileUtils.java > > > FileUtils.cleanDirectory() will not remove symbolic links if they are located > in the directory that it is trying to clean. > This occurs for me when you set up a Shell project with the "Build Fresh" > option checked. > The project I'm building is invoked with a shell script. I download the > shell script through continuum and it kicks off the first build successfully. > On the next scheduled build, the following message occurs: > --- > org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error > executing action 'clean-working-directory' > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:432) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.cleanWorkingDirectory(DefaultBuildController.java:361) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:103) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) > at > edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) > at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528) > at java.lang.Thread.run(Thread.java:595) > Caused by: java.io.IOException: Directory > /scratch/home/srp/tomcat/apache-tomcat-5.5.17/webapps/continuum/WEB-INF/working-directory/1/dir/Linux/external/TclTk/8.5a4/bin > unable to be deleted. > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1332) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.apache.maven.continuum.core.action.CleanWorkingDirectoryAction.execute(CleanWorkingDirectoryAction.java:60) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:406) > ... 9 more > -- > A search in the directory mentioned above show a symbolic link that hasn't > been deleted. > The problem occurs because the Plexus class FileUtils.cleanDirectory() > doesn't work as advertised. I reported that bug on the Plexu Utils Jira, > which you can see here: > http://jira.codehaus.org/browse/PLXUTILS-28 > I was able to incorporate the fix in Continuum by creating a new class > ContinuumFileUtils, and changed all occurances of FileUtils.cleanDirectory to > call the new
[jira] Updated: (CONTINUUM-1157) invalid url might block project addition
[ http://jira.codehaus.org/browse/CONTINUUM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1157: --- Fix Version/s: 1.1-alpha-2 > invalid url might block project addition > > > Key: CONTINUUM-1157 > URL: http://jira.codehaus.org/browse/CONTINUUM-1157 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.0.3 > Environment: Linux Fedora Core 3 >Reporter: Joerg Knobloch > Fix For: 1.1-alpha-2 > > > Step 1: Trying to add a new project with the http url of pom's parent > directory (i.e. the pom.xml in the end is missing), the directory list is > retrieved resulting in a file > in the temp directory. > Step 2: Adding the full url including the pom.xml fails with the following > error: > Could not download http://repository/svn/repository/trunk/test/pom.xml: > /home/builduser/continuum-1.0.3/temp/continuum/svn/repository/trunk/test/pom.xml > (Not a directory) > For this example, this can easily be fixed by manually removing the file > "test" in the checkout directory. > The expected behavior would be that erroneously checked out files get cleaned > up, so they might not block other projects. In the worst case, someone would > add the > repository root (http://repository/svn/repository). So no one else might be > able to add projects from the same directory without prior admin intervention. -- 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-1958) we need a var that always points to the root direcotry in multi module builds
[
http://jira.codehaus.org/browse/MNG-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89805
]
Mark Proctor commented on MNG-1958:
---
We use a root directory as a temporary repository for jars:
http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/repository/
Its not always possible or desirable to have remote repositories for some jars,
so this is a good work around. However the location breaks for multi-module
builds when being run in continuum. So this would allow us to use this
approach, while still working in continuum.
> we need a var that always points to the root direcotry in multi module builds
> -
>
> Key: MNG-1958
> URL: http://jira.codehaus.org/browse/MNG-1958
> Project: Maven 2
> Issue Type: Improvement
>Reporter: Mark Proctor
> Fix For: 2.1.x
>
>
> ${basedir} always points to the local module. There are cases, when having a
> local relative repository, when it would be usefull to have a var that always
> pointed to the root project, ${rootdir}.
> In such a case you may want to think of having the names ${rootdir}
> ${moduledir}
--
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-1163) Flat SCM Structure + Continuum = broken module-links on site
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1163: --- Description: We have a flat project structure and we're gradually adding maven support. The layout looks like this: /masterproject/trunk/pom.xml /component/trunk/pom.xml /component/trunk/subcomponent1/pom.xml /component/trunk/subcomponent2/pom.xml in out masterproject/trunk/pom.xml, the module is defined like this: ../../component/trunk Building locally works fine, but when the build is run in continuum, it can't find the module because continuum has its own layout. The annoying result is, that our will print a href and text of "../../component/trunk" in the modules menu. The build output contains this: "[WARNING] No filesystem module-POM available" How do we get this to work locally as well as in continuum? was: We have a flat project structure and we're gradually adding maven support. The layout looks like this: /masterproject/trunk/pom.xml /component/trunk/pom.xml /component/trunk/subcomponent1/pom.xml /component/trunk/subcomponent2/pom.xml in out masterproject/trunk/pom.xml, the module is defined like this: ../../component/trunk Building locally works fine, but when the build is run in continuum, it can't find the module because continuum has its own layout. The annoying result is, that our will print a href and text of "../../component/trunk" in the modules menu. The build output contains this: "[WARNING] No filesystem module-POM available" How do we get this to work locally as well as in continuum? Fix Version/s: 1.1-alpha-2 > Flat SCM Structure + Continuum = broken module-links on site > > > Key: CONTINUUM-1163 > URL: http://jira.codehaus.org/browse/CONTINUUM-1163 > Project: Continuum > Issue Type: Wish > Components: Integration - Maven 2 >Affects Versions: 1.0.2 >Reporter: Patrick Huber > Fix For: 1.1-alpha-2 > > > We have a flat project structure and we're gradually adding maven support. > The layout looks like this: > /masterproject/trunk/pom.xml > /component/trunk/pom.xml > /component/trunk/subcomponent1/pom.xml > /component/trunk/subcomponent2/pom.xml > in out masterproject/trunk/pom.xml, the module is defined like this: > ../../component/trunk > Building locally works fine, but when the build is run in continuum, it can't > find the module because continuum has its own layout. > The annoying result is, that our will print a href and > text of "../../component/trunk" in the modules menu. > The build output contains this: "[WARNING] No filesystem module-POM available" > How do we get this to work locally as well as in continuum? -- 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-1171) add a "tail" page for the build output
[ http://jira.codehaus.org/browse/CONTINUUM-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1171: --- Fix Version/s: 1.1-alpha-# > add a "tail" page for the build output > -- > > Key: CONTINUUM-1171 > URL: http://jira.codehaus.org/browse/CONTINUUM-1171 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.0.3 >Reporter: Patrick Huber > Fix For: 1.1-alpha-# > > > add a servlet or something that acts like "tail -f" on the console so I don't > have to hit F5 and scroll down again every few seconds when I want to watch a > 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-1166) Integration test failures: AccountSecurityTest
[ http://jira.codehaus.org/browse/CONTINUUM-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1166: --- Fix Version/s: 1.1-alpha-2 > Integration test failures: AccountSecurityTest > -- > > Key: CONTINUUM-1166 > URL: http://jira.codehaus.org/browse/CONTINUUM-1166 > Project: Continuum > Issue Type: Task > Components: Testing >Affects Versions: 1.1-alpha-1 > Environment: WinXP Continuum 1.1-SNAPSHOT r507397 >Reporter: Wendy Smoak > Fix For: 1.1-alpha-2 > > Attachments: AccountSecurityTest-r507420.txt, > org.apache.continuum.web.test.AccountSecurityTest.txt > > > --- > Test set: org.apache.continuum.web.test.AccountSecurityTest > --- > Tests run: 5, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 107.797 sec > <<< FAILURE! > When editing a user, effective roles are displayed on the first page, but it > is necessary to click the 'Edit Roles' in order to add or delete roles. > Full Surefire report attached. -- 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-1174) add alternative view/filters for the frontpage
[ http://jira.codehaus.org/browse/CONTINUUM-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1174: --- Fix Version/s: 1.1-alpha-# > add alternative view/filters for the frontpage > -- > > Key: CONTINUUM-1174 > URL: http://jira.codehaus.org/browse/CONTINUUM-1174 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.0.3 >Reporter: Patrick Huber > Fix For: 1.1-alpha-# > > > add a new page filtering all but failed projects -- 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-1179) When the projects are viewed I would like to be able to expand/collapse pom's to their subpoms
[ http://jira.codehaus.org/browse/CONTINUUM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1179: --- Fix Version/s: 1.1-alpha-# > When the projects are viewed I would like to be able to expand/collapse > pom's to their subpoms > --- > > Key: CONTINUUM-1179 > URL: http://jira.codehaus.org/browse/CONTINUUM-1179 > Project: Continuum > Issue Type: New Feature > Components: Integration - Maven 2, Web - UI >Affects Versions: 1.0.3 >Reporter: Eric Helfrich > Fix For: 1.1-alpha-# > > > When the projects are viewed I would like to be able to expand/collapse > pom's to their subpoms > Projects page is too cluttered with multi-module projects of any size -- 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-1178) In Add New Maven 2 Project woudl like opportunity not to load modules
[ http://jira.codehaus.org/browse/CONTINUUM-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1178: --- Fix Version/s: 1.1-alpha-2 > In Add New Maven 2 Project woudl like opportunity not to load modules > - > > Key: CONTINUUM-1178 > URL: http://jira.codehaus.org/browse/CONTINUUM-1178 > Project: Continuum > Issue Type: New Feature > Components: Web - Configuration, Web - UI >Affects Versions: 1.0.3 >Reporter: Eric Helfrich > Fix For: 1.1-alpha-2 > > > I would like to be able to load a pom file without it recursively adding all > the modules -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1180) Add the revision number of the check out in the Build result screen
[ http://jira.codehaus.org/browse/CONTINUUM-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1180: --- Fix Version/s: 1.1-alpha-# > Add the revision number of the check out in the Build result screen > --- > > Key: CONTINUUM-1180 > URL: http://jira.codehaus.org/browse/CONTINUUM-1180 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Vincent Siveton > Fix For: 1.1-alpha-# > > > It should be helpful to know the SCM revision of a success build. So, a > developer can retry locally. -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
Subartifact (ejb-client for example) are not reselved as active project artifacts - Key: MNG-2871 URL: http://jira.codehaus.org/browse/MNG-2871 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.5, 2.0.4 Environment: Not platform dependent Reporter: Piotr Tabor I have prepared simple project to show the bug. It contains three artifacts: |-root \--- ejb3 \--- client Client depends on ejb3 with ejb-client. The local and remote repository must not contain those artifacts. When I do "mvn -X compile" (or even integration-tests) on root project I will get those errors: ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> [DEBUG] (f) filters = [] [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) resources = [EMAIL PROTECTED] [DEBUG] -- end configuration -- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected for compile) [DEBUG] Skipping disabled repository Newitech-repository [DEBUG] Skipping disabled repository central [DEBUG] ejb3: using locally installed snapshot [DEBUG] Trying repository Newitech-snapshots-repository Downloading: scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar [WARNING] Unable to get resource 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Newitech-snapshots-repository (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) [DEBUG] Skipping disabled repository Newitech-repository [DEBUG] Trying repository Newitech-publiczne Downloading: scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar [WARNING] Unable to get resource 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Newitech-publiczne (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) [DEBUG] Trying repository Maven Snapshots Downloading: http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar [WARNING] Unable to get resource 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven Snapshots (http://people.apache.org/maven-snapshot-repository) [DEBUG] Trying repository codehausSnapshots Downloading: http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar [WARNING] Unable to get resource 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) [DEBUG] Skipping disabled repository central [DEBUG] Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file Path to dependency: 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT from the specified remote repositories: Maven Snapshots (http://people.apache.org/maven-snapshot-repository), central (http://repo1.maven.org/maven2), codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), Newitech-snapshots-repository (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), Newitech-publiczne (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), Newitech-repository (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file Path to dependency: 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT -- 1 required artifact is missing. for artifact: pl.waw.tabor:client:jar:1.0-SNAPSHOT from the specified remote repositories: Maven Snapshots (http://people.apache.org/maven-snapshot-re
[jira] Created: (MJAR-68) multi module release fails because of test-jar
multi module release fails because of test-jar -- Key: MJAR-68 URL: http://jira.codehaus.org/browse/MJAR-68 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.1 Environment: maven 2.0.5 Reporter: Yuri Schimke The release plugin is failing in the prepare task mvn release:prepare seemingly because it can't find the test-jar that has just been built by the previous module i.e. built within. Are there some examples in the wild of using the test-jar on a multi module project that does releases? The (nasty) workaround I have for now, is to wait for the build to fail and then mvn install So the test-jar (and other artifacts) are in my local repository and then continue mvn release:prepare -- 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-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Tabor updated MNG-2871: - Attachment: root.tar The simple project - to repeat the bug. > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor > Attachments: root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install
[jira] Commented: (MNG-2871) Subartifact (ejb-client for example) are not reselved as active project artifacts
[ http://jira.codehaus.org/browse/MNG-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89813 ] Piotr Tabor commented on MNG-2871: -- The bug is very serious - because it happens every time you use mvn release:prepare plugin (because there are started integration-tests in embedded maven session) - and they always fail - because there is no such a artifact in maven local repository after increasing version number. > Subartifact (ejb-client for example) are not reselved as active project > artifacts > - > > Key: MNG-2871 > URL: http://jira.codehaus.org/browse/MNG-2871 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.4, 2.0.5 > Environment: Not platform dependent >Reporter: Piotr Tabor > Attachments: root.tar > > > I have prepared simple project to show the bug. > It contains three artifacts: > |-root > \--- ejb3 > \--- client > Client depends on ejb3 with ejb-client. > The local and remote repository must not contain those artifacts. > When I do "mvn -X compile" (or even integration-tests) on root project I will > get those errors: > ... > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' --> > [DEBUG] (f) filters = [] > [DEBUG] (f) outputDirectory = /home/ptab/m2/bug/root/client/target/classes > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] (f) resources = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [DEBUG] pl.waw.tabor:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT:compile (selected > for compile) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Skipping disabled repository central > [DEBUG] ejb3: using locally installed snapshot > [DEBUG] Trying repository Newitech-snapshots-repository > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots) > [DEBUG] Skipping disabled repository Newitech-repository > [DEBUG] Trying repository Newitech-publiczne > Downloading: > scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne//pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/) > [DEBUG] Trying repository Maven Snapshots > Downloading: > http://people.apache.org/maven-snapshot-repository/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository Maven > Snapshots (http://people.apache.org/maven-snapshot-repository) > [DEBUG] Trying repository codehausSnapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/pl/waw/tabor/ejb3/1.0-SNAPSHOT/ejb3-1.0-SNAPSHOT-client.jar > [WARNING] Unable to get resource > 'pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT' from repository > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2) > [DEBUG] Skipping disabled repository central > [DEBUG] Unable to download the artifact from any repository > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=pl.waw.tabor -DartifactId=ejb3 \ > -Dversion=1.0-SNAPSHOT -Dpackaging=ejb-client -Dfile=/path/to/file > Path to dependency: > 1) pl.waw.tabor:client:jar:1.0-SNAPSHOT > 2) pl.waw.tabor:ejb3:ejb-client:client:1.0-SNAPSHOT > pl.waw.tabor:ejb3:ejb-client:1.0-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://people.apache.org/maven-snapshot-repository), > central (http://repo1.maven.org/maven2), > codehausSnapshots (http://snapshots.maven.codehaus.org/maven2), > Newitech-snapshots-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech-snapshots), > Newitech-publiczne > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/publiczne/), > Newitech-repository > (scp://ivy.newitech.com/opt/maven/public_html/repozytoria/newitech) > [INFO] > > [ERROR] BUILD ERROR > [INFO] >
[jira] Updated: (CONTINUUM-1186) Application should unpack to continuum-${version}
[
http://jira.codehaus.org/browse/CONTINUUM-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-1186:
---
Affects Version/s: 1.1-alpha-1
Fix Version/s: 1.1-alpha-1
Component/s: Environmental
> Application should unpack to continuum-${version}
> -
>
> Key: CONTINUUM-1186
> URL: http://jira.codehaus.org/browse/CONTINUUM-1186
> Project: Continuum
> Issue Type: Improvement
> Components: Environmental
>Affects Versions: 1.1-alpha-1
> Environment: 1.1-SNAPSHOT r511964
>Reporter: Wendy Smoak
> Fix For: 1.1-alpha-1
>
>
> The Plexus app currently unpacks to 'continuum'. It should have the version
> number in the top level directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1181) Continuum aborts when running Postgres under JBoss
[ http://jira.codehaus.org/browse/CONTINUUM-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1181: --- Fix Version/s: 1.1-alpha-1 > Continuum aborts when running Postgres under JBoss > -- > > Key: CONTINUUM-1181 > URL: http://jira.codehaus.org/browse/CONTINUUM-1181 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1-alpha-1 > Environment: MS Windows XP Pro SP2 > postgres 8.1.4-1 with JDBC Driver postgresql-8.1-408.jdbc3 > JBoss 4.0.5.GA >Reporter: thierry lach > Fix For: 1.1-alpha-1 > > > I'm trying to get Continuum to store its data in a postgres database while > running under JBoss and I'm getting an exception. It seems that someone is > trying to change the transaction isolation during a transaction. > Excerpt from JBoss logs follows... > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - Starting Continuum. > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - < Continuum 1.1-SNAPSHOT started! > > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - --- > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -\ ^__^ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - \ (oo)\___ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -(__)\ )\/\ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -||w | > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -|| || > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO ContinuumInitializer:default > - Continuum initializer running ... > 2007-02-21 12:56:02,644 [ScannerThread] WARN LocalManagedConnectionFactory > - Error resetting transaction isolation > org.postgresql.util.PSQLException: Cannot change transaction isolation level > in the middle of a transaction. > at > org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection.java:733) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.cleanup(BaseWrapperManagedConnection.java:189) > at > org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java > :320) > at > org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.returnConnection(JBossManagedConnectionPool.java:620) > at > org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection > (BaseConnectionManager2.java:363) > at > org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:623) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle > (BaseWrapperManagedConnection.java:266) > at > org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129) > at > org.jpox.store.rdbms.adapter.DatabaseAdapter.getConnection(DatabaseAdapter.java > :928) > at > org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTransaction.java:324) > at > org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:356) > at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached > (PlexusJdoUtils.java:346) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached( > JdoContinuumStore.java:1287) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1282) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached > (JdoContinuumStore.java:1277) > at > org.apache.maven.continuum.store.JdoContinuumStore.getSystemConfiguration(JdoContinuumStore.java:1375) > at > org.apache.maven.continuum.initialization.DefaultContinuumInitializer.initialize > (DefaultContinuumInitializer.java:90) > at > org.apache.maven.continuum.DefaultContinuum.start(DefaultContinuum.java:2281) > at > org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java > :33) > at > org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.star
[jira] Updated: (CONTINUUM-1187) NumberFormatException on invalid scm url
[ http://jira.codehaus.org/browse/CONTINUUM-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1187: --- Fix Version/s: 1.1-alpha-2 > NumberFormatException on invalid scm url > > > Key: CONTINUUM-1187 > URL: http://jira.codehaus.org/browse/CONTINUUM-1187 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.0.3 > Environment: Debian Linux, AFS >Reporter: Adam Kiezun > Fix For: 1.1-alpha-2 > > > I entered scm:svn:svn+ssh://[EMAIL > PROTECTED]:/afs/csail.mit.edu/group/pag/projects/joe/repository/trunk/joe > as my scm ulr (note that there's a bogus colon after 'edu') > I got a NumberFormatException. > This should be flagged as invalid scm string and not show up as exception in > the 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-972) Unable to delete projects
[ http://jira.codehaus.org/browse/CONTINUUM-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-972: -- Fix Version/s: 1.1-alpha-2 > Unable to delete projects > - > > Key: CONTINUUM-972 > URL: http://jira.codehaus.org/browse/CONTINUUM-972 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.3 > Environment: Redhat Enterprise 3 >Reporter: Uri Moszkowicz > Fix For: 1.1-alpha-2 > > > I am unable to delete project sometimes. I've tried creating a simple project > and immediately deleting it. That seems to work. But when I create a real > project, let it run for a few days and then try to delete it I cannot. > To reproduce: > 1. Install continuum > 2. Create a project > 3. Let it run for at least one build (success or failure doesn't matter) > 4. Delete the project by clicking on "X" from main project page. A delete > confirmation page should then appear. > 5. Click on the "delete" button to confirm. The web browser then begins > loading but it never terminates. The logs show no exceptions. The delete just > hangs. > I've removed all the files from the build-output and working-directory and > tried deleting again. This makes no difference. If you interrupt the delete > and click on show projects the projects page ends up in an inconsistent state > (not as many columns, no buttons, an Apache copyright message). -- 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-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-663: -- Affects Version/s: 1.1-alpha-1 Fix Version/s: Future > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Issue Type: New Feature >Affects Versions: 1.1-alpha-1 > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 >Reporter: Rahul Thakur > Assigned To: Rahul Thakur > Fix For: Future > > Attachments: cm-plugin.tar.gz, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt > > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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-1190) Ability to edit nicely a build definition with scope group in a project
[ http://jira.codehaus.org/browse/CONTINUUM-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1190: --- Fix Version/s: 1.1-alpha-2 need to improve the rendering of what is 'default' build definition as well, thanks for filing this though > Ability to edit nicely a build definition with scope group in a project > --- > > Key: CONTINUUM-1190 > URL: http://jira.codehaus.org/browse/CONTINUUM-1190 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles, Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Stephane Nicoll > Fix For: 1.1-alpha-2 > > > When in a particular project, an administrator has the ability to edit a > build definition from the GROUP but the current behavior is confusing since > the changes is applicable to all projects in the group. > Suggestion. When a build definition with scope GROUP is edited within a > project, it is transformed automatically in a new build definition with > scope PROJECT (with eventually a confirmation message). > In general, editing stuff in a project page should only affect the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1192) Ability to disable a project group build definition per project
[ http://jira.codehaus.org/browse/CONTINUUM-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1192: --- Fix Version/s: 1.1-alpha-2 > Ability to disable a project group build definition per project > --- > > Key: CONTINUUM-1192 > URL: http://jira.codehaus.org/browse/CONTINUUM-1192 > Project: Continuum > Issue Type: New Feature > Components: Core - Profiles, Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Stephane Nicoll > Fix For: 1.1-alpha-2 > > > Project group's build definitions are automatically inherited to any project > created within the group which is fine. It would be even better if an > administrator had the ability to disable such a build definition per project. > For now, the only way is to override the default build definition which is > confusing since the group's default build definition is not disabled. -- 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-1191) editProject: NoSuchMethodException:
[
http://jira.codehaus.org/browse/CONTINUUM-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-1191:
---
Description:
I'm writing a small application that's intended to consolidate all build goals
and arguments for all our projects in continuum:
Client:
---
String address = "http://continuumhost:8000/continuum";;
ProjectsReader reader = new ProjectsReader(new URL(address));
for (Project project : reader.readProjects()) {
// reader.refreshProject(project);
List defs = project.getBuildDefinitions();
if (defs != null && defs.size() == 1) {
for (BuildDefinition def : defs) {
def.setGoals("clean deploy site:site site:deploy eclipse:eclipse
scm:checkin");
def.setArguments("--batch-mode --non-recursive
-Dincludes=\".project .classpath .settings\" -Dmessage=\"continuum checkin of
generated eclipse files\"");
}
}
else {
System.out.println("Project " + project.getId() + " " +
project.getName() + " has not exactly one build");
}
reader.editProject(project);
---
Exception:
---
Exception in thread "main" org.apache.xmlrpc.XmlRpcException:
java.lang.NoSuchMethodException:
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.updatenullProject(java.util.Hashtable)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:102)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:69)
at
org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:72)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:193)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:184)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:177)
at
org.apache.maven.continuum.rpc.ProjectsReader.editProject(ProjectsReader.java:127)
at SampleClient.main(SampleClient.java:55)
---
It doesn't matter wether or not "reader.refreshProject(project);" is active. Am
I doing something wrong here or is this a bug? The documentation only shows how
to read a project...
was:
I'm writing a small application that's intended to consolidate all build goals
and arguments for all our projects in continuum:
Client:
---
String address = "http://continuumhost:8000/continuum";;
ProjectsReader reader = new ProjectsReader(new URL(address));
for (Project project : reader.readProjects()) {
// reader.refreshProject(project);
List defs = project.getBuildDefinitions();
if (defs != null && defs.size() == 1) {
for (BuildDefinition def : defs) {
def.setGoals("clean deploy site:site site:deploy eclipse:eclipse
scm:checkin");
def.setArguments("--batch-mode --non-recursive
-Dincludes=\".project .classpath .settings\" -Dmessage=\"continuum checkin of
generated eclipse files\"");
}
}
else {
System.out.println("Project " + project.getId() + " " +
project.getName() + " has not exactly one build");
}
reader.editProject(project);
---
Exception:
---
Exception in thread "main" org.apache.xmlrpc.XmlRpcException:
java.lang.NoSuchMethodException:
org.apache.maven.continuum.xmlrpc.DefaultContinuumXmlRpc.updatenullProject(java.util.Hashtable)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:102)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:69)
at
org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:72)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:193)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:184)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:177)
at
org.apache.maven.continuum.rpc.ProjectsReader.editProject(ProjectsReader.java:127)
at SampleClient.main(SampleClient.java:55)
---
It doesn't matter wether or not "reader.refreshProject(project);" is active. Am
I doing something wrong here or is this a bug? The documentation only shows how
to read a project...
Fix Version/s: 1.1-alpha-2
> editProject: NoSuchMethodException:
> ---
>
> Key: CONTINUUM-1191
> URL: http://jira.codehaus.org/browse/CONTINUUM-1191
> Project: Continuum
> Issue Type: Bug
> Components: XMLRPC Interface
>Affects Versions: 1.0.3
>Reporter: Patrick Huber
> Fix For: 1.1-alpha-2
>
>
> I'm writing a small application that's intended to consolidate all build
> goals and arguments for
[jira] Created: (NMAVEN-13) Determine If Visual Studio 2005 SDK License is Compatible
Determine If Visual Studio 2005 SDK License is Compatible - Key: NMAVEN-13 URL: http://jira.codehaus.org/browse/NMAVEN-13 Project: NMaven Issue Type: Task Environment: Windows Reporter: Shane Isbell Priority: Minor Attachments: VS_2005_SDK_LICENSE.rtf I am considering on using the MS integration package for IDE integration, but do not know if it is compatible with open-source and the ASF. -- 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-1197) Continuum aborts when using Oracle database after applying patch in CONTINUUM-961
[ http://jira.codehaus.org/browse/CONTINUUM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1197: --- Fix Version/s: 1.1-alpha-# joakim found other issues with oracle that will exist past this point related to keywords and the security database, so this will have to be addressed once we get into redback and refactor some stuff soonish > Continuum aborts when using Oracle database after applying patch in > CONTINUUM-961 > - > > Key: CONTINUUM-1197 > URL: http://jira.codehaus.org/browse/CONTINUUM-1197 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1-alpha-1 > Environment: Oracle database 9.2.0.1.0 > Oracle jdbc driver 10.2.0.1.0 >Reporter: thierry lach > Fix For: 1.1-alpha-# > > > I changed the transaction isolation using the patch I just attached to > CONTINUUM-961 and rebuilt, but now I'm coming up with the following error. > I'm running against oracle 9.2.0.1.0 and using the oracle jdbc driver version > 10.2.0.1.0. According to their latest release documentation (release 10g, > http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements001.htm#i54330) > Oracle has a max length for varchar2 of 4000. > jvm 1 | 2007-03-01 14:19:05,953 [main] ERROR RDBMS - Error thrown executing > CREATE TABLE CHANGESET > jvm 1 | ( > jvm 1 | CHANGESET_ID NUMBER NOT NULL, > jvm 1 | AUTHOR VARCHAR2(256) NULL, > jvm 1 | "COMMENT" VARCHAR2(8192) NULL, > jvm 1 | "DATE" NUMBER NOT NULL, > jvm 1 | ID VARCHAR2(256) NULL, > jvm 1 | MODEL_ENCODING VARCHAR2(256) NULL, > jvm 1 | CHANGES_SCMRESULT_ID_OID NUMBER NULL, > jvm 1 | CHANGES_INTEGER_IDX NUMBER(10) NULL > jvm 1 | ) : ORA-00910: specified length too long for its datatype > jvm 1 | > jvm 1 | java.sql.SQLException: ORA-00910: specified length too long for its > datatype > jvm 1 | > jvm 1 | at > oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) > jvm 1 | at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) > jvm 1 | at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) > jvm 1 | at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) > jvm 1 | at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207) > jvm 1 | at > oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:946) > jvm 1 | at > oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168) > jvm 1 | at > oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1687) > jvm 1 | at > oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1653) > jvm 1 | at > org.jboss.resource.adapter.jdbc.WrappedStatement.execute(WrappedStatement.java:84) > jvm 1 | at > org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:614) > jvm 1 | at > org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:570) > jvm 1 | at > org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:297) > jvm 1 | at > org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:341) > jvm 1 | at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDBMSManager.java:3052) > jvm 1 | at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3313) > jvm 1 | at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2554) > jvm 1 | at > org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2406) > jvm 1 | at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:821) > jvm 1 | at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:835) > jvm 1 | at > org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1161) > jvm 1 | at org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1354) > jvm 1 | at > org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager.java:2324) > jvm 1 | at > org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:358) > jvm 1 | at > org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:342) > jvm 1 | at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302) > jvm 1 | at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1287) > jvm 1 | at > org.apache.maven.continuum.store.JdoContinuumStore.getAllProjectsByNameWithBuildDetails(JdoContinuumStore.java:843) > jvm 1 | at > org.apache.maven.continuum.DefaultContinuum.initialize(DefaultContinuum.java:2209) > jvm 1 | at > org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) > jvm 1 | at > org.codehaus.plexus.lifecycle.Abstract
[jira] Updated: (CONTINUUM-1194) Project is stuck in the "Build in Progress" state if the associated exception has more than 8192 chars
[ http://jira.codehaus.org/browse/CONTINUUM-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1194: --- Fix Version/s: 1.1-alpha-2 > Project is stuck in the "Build in Progress" state if the associated exception > has more than 8192 chars > -- > > Key: CONTINUUM-1194 > URL: http://jira.codehaus.org/browse/CONTINUUM-1194 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Stephane Nicoll > Fix For: 1.1-alpha-2 > > Attachments: screenshot.png > > > We have added unit tests to one of our project and some of them are crashing > from time to time due to a race condition with the database connections. > Since then, the project is always in the "Build In progress" state even if > the build is actually terminated in the log (Build failure because one test > failed). The project never leaves this state, if we consult the builds > summary we have a couple of builds in the Build In progress state (?!) > See screenshot. -- 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-1152) Using multiple Ant projects with Continuum and Perforce SCM - the perforce views are incorrectly created
[ http://jira.codehaus.org/browse/CONTINUUM-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1152: --- Fix Version/s: 1.1-alpha-# > Using multiple Ant projects with Continuum and Perforce SCM - the perforce > views are incorrectly created > > > Key: CONTINUUM-1152 > URL: http://jira.codehaus.org/browse/CONTINUUM-1152 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 > Environment: Windows Server 2003 > Ant 1.6.5 > Maven 2.0.4 > Continuum 1.0.3 > JDK 1.5.0_06 >Reporter: Joseph Heck > Fix For: 1.1-alpha-# > > > Using multiple Ant projects with Continuum and Perforce SCM - the perforce > views are incorrectly created > The first client created automagically works correctly. > The second project generates a client that references the first. From the log > files: > 1052282 [Thread-3] INFO org.apache.maven.continuum.scm.ContinuumScm - > Checking out project: 'GUR - Crc Generator', id: '2' to > 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\2'. > 1052282 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - Checkout > working directory: > C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\2 > 1052282 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - > Executing: p4 client -i > 1052282 [Thread-3] DEBUG org.apache.maven.scm.manager.ScmManager - Updating > clientspec: > Client: > webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1 > Root: C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\2 > Owner: webguest > View: > //p4-tss/gur/Development/CrcGenerator/1.0/... > //webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1/... > Description: > Created by maven-scm-provider-perforce > This client that has been generated should be references > working-directory\2/... not 1 > Adding a third project shows that it also references the first "client": > 1080922 [Thread-3] INFO org.apache.maven.continuum.scm.ContinuumScm - > Checking out project: 'GUR - Crc Local', id: '3' to > 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\3'. > 1080922 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - Checkout > working directory: > C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\3 > 1080922 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - > Executing: p4 client -i > 1080922 [Thread-3] DEBUG org.apache.maven.scm.manager.ScmManager - Updating > clientspec: > Client: > webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1 > Root: C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\3 > Owner: webguest > View: > //p4-tss/gur/Development/CrcLocalApi/1.0/... > //webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1/... > Description: > Created by maven-scm-provider-perforce > I haven't yet dug into the code to determine where the client view gets set, > but that appears to be where the mistake is being made. -- 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-1204) Fix permissons on the CONTINUUMUSER space
[ http://jira.codehaus.org/browse/CONTINUUM-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1204: --- Description: Unlike MAVENUSER, the public Continuum wiki space is not visible unless you're logged in. http://docs.codehaus.org/display/CONTINUUMUSER/Home was: Unlike MAVENUSER, the public Continuum wiki space is not visible unless you're logged in. http://docs.codehaus.org/display/CONTINUUMUSER/Home Fix Version/s: 1.1-alpha-1 > Fix permissons on the CONTINUUMUSER space > --- > > Key: CONTINUUM-1204 > URL: http://jira.codehaus.org/browse/CONTINUUM-1204 > Project: Continuum > Issue Type: Task > Components: Documentation >Reporter: Wendy Smoak > Fix For: 1.1-alpha-1 > > > Unlike MAVENUSER, the public Continuum wiki space is not visible unless > you're logged in. > http://docs.codehaus.org/display/CONTINUUMUSER/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-1199) Password Characters Not Supported in HTTP Authentication
[ http://jira.codehaus.org/browse/CONTINUUM-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1199: --- Fix Version/s: 1.1-alpha-2 Component/s: Web - UI > Password Characters Not Supported in HTTP Authentication > > > Key: CONTINUUM-1199 > URL: http://jira.codehaus.org/browse/CONTINUUM-1199 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-alpha-1 >Reporter: Stephen Duncan Jr > Fix For: 1.1-alpha-2 > > > When entering a url +username + password to download a pom to configure a > project, certain password characters will cause it to fail. This is because > the password is inserted into the url, so url special characters (@,?, etc) > will not work. The password should be provided in response to the challenge, > rather than as part of the url. -- 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-1200) Password Characters Not Supported in SCM Checkout
[ http://jira.codehaus.org/browse/CONTINUUM-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1200: --- Affects Version/s: 1.1-alpha-1 Fix Version/s: 1.1-alpha-2 Component/s: SCM > Password Characters Not Supported in SCM Checkout > - > > Key: CONTINUUM-1200 > URL: http://jira.codehaus.org/browse/CONTINUUM-1200 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-alpha-1 >Reporter: Stephen Duncan Jr > Fix For: 1.1-alpha-2 > > > Certain characters are not supported for the password for an SCM checkout. > For instance if a ')' is the first character, then the command fails. This > is because the password is provided as a CLI parameter, and is not surrounded > by quotes. Obviously, adding quotes might break other passwords, so it would > be best to pass the password along some other way. -- 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-737) Database log contains continuum user passwords in clear text
[ http://jira.codehaus.org/browse/CONTINUUM-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-737: -- Fix Version/s: 1.1-alpha-2 > Database log contains continuum user passwords in clear text > > > Key: CONTINUUM-737 > URL: http://jira.codehaus.org/browse/CONTINUUM-737 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Bernhard Wellhöfer >Priority: Minor > Fix For: 1.1-alpha-2 > > > Hello, > The database log contains the continuum user passwords in clear text. This is > kind of a security issue. > Regards, > Bernd -- 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-511) Continuum should use Server VM
[ http://jira.codehaus.org/browse/CONTINUUM-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-511: -- Fix Version/s: 1.1-alpha-2 > Continuum should use Server VM > -- > > Key: CONTINUUM-511 > URL: http://jira.codehaus.org/browse/CONTINUUM-511 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Matthew Beermann >Priority: Minor > Fix For: 1.1-alpha-2 > > Attachments: patch.txt > > > Continuum could (should?) use the Server VM rather than the default Client VM > when running as a service. I'm not fully versed in all the differences > between them, but from what I do know, it seems much more appropriate. > This would involve adding another "wrapper.java.additional" parameter to > bin/win32/wrapper.conf (-server). -- 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-565) Forced builds should say who (which continuum user) forced the build
[ http://jira.codehaus.org/browse/CONTINUUM-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-565: -- Fix Version/s: 1.1-alpha-# > Forced builds should say who (which continuum user) forced the build > > > Key: CONTINUUM-565 > URL: http://jira.codehaus.org/browse/CONTINUUM-565 > Project: Continuum > Issue Type: Improvement > Components: Core system >Reporter: Jamie Flournoy >Priority: Minor > Fix For: 1.1-alpha-# > > > Currently if a build is forced the build history and notifications don't say > who forced it. It would be nice if that was part of the history and > notifications. -- 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-671) Small visualization issue
[ http://jira.codehaus.org/browse/CONTINUUM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-671: -- Fix Version/s: 1.1-alpha-1 different security impl now, need to verify this isn't an issue anymore > Small visualization issue > - > > Key: CONTINUUM-671 > URL: http://jira.codehaus.org/browse/CONTINUUM-671 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Reinhard Spisser >Priority: Minor > Fix For: 1.1-alpha-1 > > > When Continuum is opened the first time with a browser and the user selects > the "build now" button, the actual status of the build is not shown (buttons > are not greyed out, "building" icon is not displayed in the Build column). > The issue occurs only when no build is already in progress. Builds are > performed correctly, the current state of the build is not correctly > displayed. > A click on "Show Projects" will show the real state of the build. > Guest users must be enabled to build projects to reproduce this issue. > This issue does not occur with authenticated users. -- 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-1002) build email cleanup
[ http://jira.codehaus.org/browse/CONTINUUM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-1002: --- Fix Version/s: 1.1-alpha-2 > build email cleanup > --- > > Key: CONTINUUM-1002 > URL: http://jira.codehaus.org/browse/CONTINUUM-1002 > Project: Continuum > Issue Type: Improvement > Components: Notifier - Mail >Reporter: Jon >Priority: Minor > Fix For: 1.1-alpha-2 > > Attachments: Picture 1.png > > > In the build emails, at the top it comes out something like this: > Online report : > http://build.365:8080/continuum/buildResult.action?buildId=68&projectId=17&projectName=Integration > Tests > It would be really cool if someone put a newline between the end of the url > and the "Tests" > jon -- 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-2872) Don't append artifactId when parent pom already has artifactId in URL
Don't append artifactId when parent pom already has artifactId in URL
-
Key: MNG-2872
URL: http://jira.codehaus.org/browse/MNG-2872
Project: Maven 2
Issue Type: Wish
Affects Versions: 2.0.5
Reporter: Papick G. Taboada
Priority: Trivial
I want to define the url for all my projects from one central pom. the pom
project itself has the same url structure as the child projects.
This is for all urls that can be inherited, e.g. distribution site, deployment
url, etc.
I would like to specify some complete url like
protocol:/my.server.com/some/path/to/the/${groupId}/${artifactId}
For example, with the actual implementation I get either the parent pom site
deployed to the groupId directory, or I get the child projects deployed to the
grouId/artifactId/artifactId directory.
At the moment I have add the urls on every project, although they always have
the same pattern.
--
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-656) Child Project / Module added twice
[ http://jira.codehaus.org/browse/CONTINUUM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-656: -- Fix Version/s: 1.1-alpha-2 > Child Project / Module added twice > -- > > Key: CONTINUUM-656 > URL: http://jira.codehaus.org/browse/CONTINUUM-656 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 > Environment: Red Hat Enterprise Linux; Java 1.5 >Reporter: David H. DeWolf >Priority: Minor > Fix For: 1.1-alpha-2 > > > Added parent project with 10 subprojects. Parent and all children were added > successfully. One of the modules was duplicated. Working to put together a > smaller test case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-700) Need of CVS in the PATH has to be stated
[ http://jira.codehaus.org/browse/CONTINUUM-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-700: -- Fix Version/s: 1.1-alpha-# > Need of CVS in the PATH has to be stated > > > Key: CONTINUUM-700 > URL: http://jira.codehaus.org/browse/CONTINUUM-700 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.0.3 >Reporter: Alex Mayorga Adame > Assigned To: Alex Mayorga Adame >Priority: Minor > Fix For: 1.1-alpha-# > > > The absence of CVS in the PATH for the Continuum environment can lead to > problems like the one described at http://jira.codehaus.org/browse/SCM-200 -- 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-774) Better support for multiprojects
[ http://jira.codehaus.org/browse/CONTINUUM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-774: -- Fix Version/s: 1.1-alpha-2 pretty sure I saw another issue like this one, have to track it down later > Better support for multiprojects > > > Key: CONTINUUM-774 > URL: http://jira.codehaus.org/browse/CONTINUUM-774 > Project: Continuum > Issue Type: Improvement > Components: Project Grouping >Reporter: Tomasz Pik >Priority: Minor > Fix For: 1.1-alpha-2 > > > Currently when multiproject is being added to continuum, then top project is > being registered as 'non-recursive' and all submodules are being added as > separate projects. > It will be nice to have the possibility to define (during initiial POM > loading) if project should be treat that way or as a multiproject with full > recursive build and without adding subprojects. > I'm doing that manually, by redefining build section for top project and > removing subprojects. -- 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-931) Project Group Summary page has no internationalization.
[ http://jira.codehaus.org/browse/CONTINUUM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-931: -- Fix Version/s: 1.1-alpha-# none of it does anymore, we need to capture all text back into properties files > Project Group Summary page has no internationalization. > --- > > Key: CONTINUUM-931 > URL: http://jira.codehaus.org/browse/CONTINUUM-931 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Henry S. Isidro > Assigned To: Henry S. Isidro >Priority: Minor > 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-572) Web interface doesn't say anything about notification depending on state changes
[ http://jira.codehaus.org/browse/CONTINUUM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-572: -- Fix Version/s: 1.1-alpha-# > Web interface doesn't say anything about notification depending on state > changes > > > Key: CONTINUUM-572 > URL: http://jira.codehaus.org/browse/CONTINUUM-572 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.2 >Reporter: Jamie Flournoy >Priority: Minor > Fix For: 1.1-alpha-# > > > This is related to CONTINUUM-446. > I've read the mailing list and I understand (now) that Continuum doesn't send > notification messages unless the build state changes. I also see that > CONTINUUM-446 is an enhancement request to make this behavior configurable. > However this is an undocumented behavior, and the web interface very clearly > has checkboxes for build outcomes that are not heeded because of this > behavior. By that I mean, the build succeeded and I checked "Send on success" > and yet no message was sent. So, the UI says one thing and the code does > something else. > This could be fixed quickly by simply adding a note that explains that no > matter what, notifications will never be sent if the state remains the same. > This note would then become a checkbox for "Send notification even if state > doesn't change" after CONTINUUM-446 is implemented. -- 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: (NMAVEN-12) Support for Invoking the MavenEmbedder Methods from .NET Applications
[ http://jira.codehaus.org/browse/NMAVEN-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89826 ] Shane Isbell commented on NMAVEN-12: I successfully got a .NET web service client to communicate build instructions with xFire running on Apache. However, it looks as though the MavenEmbedder itself is not mature enough to use right now (according to Jason wait until 2.1-alpha-1). Other options include, 1) new MavenEmbedder; 2) MavenCli; 3) execute through a process. Options 2, 3 are workable but there is a problem of getting the build output to the IDE console in a timely way. > Support for Invoking the MavenEmbedder Methods from .NET Applications > - > > Key: NMAVEN-12 > URL: http://jira.codehaus.org/browse/NMAVEN-12 > Project: NMaven > Issue Type: New Feature > Environment: Windows, Linux >Reporter: Shane Isbell >Priority: Minor > > As part of the IDE integration, Visual Studio and Sharp Develop need to use > maven functionality. This feature will support a way for .NET applications to > invoke the MavenEmbedder methods. -- 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-467) observe folder for changes which can trigger a build
[ http://jira.codehaus.org/browse/CONTINUUM-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-467: -- Fix Version/s: 1.1-alpha-2 this would also be served by the xml-rpc build pushing getting cleaned up a bit > observe folder for changes which can trigger a build > > > Key: CONTINUUM-467 > URL: http://jira.codehaus.org/browse/CONTINUUM-467 > Project: Continuum > Issue Type: New Feature > Components: Core system > Environment: all >Reporter: yo >Priority: Minor > Fix For: 1.1-alpha-2 > > > It would be nice if another way to trigger a build would be to observe a > folder for changes. everytime someone commits something back to the repo a > file is created in a folder which continuum observes and triggers the build > of the project by the name of the file. That was conitnuum does not have to > say query a hundreds svnrepos if something changed. > Greetings > Yo -- 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-34) Keep trying till build works, notify via email what is required
[ http://jira.codehaus.org/browse/CONTINUUM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-34: - Fix Version/s: Future > Keep trying till build works, notify via email what is required > --- > > Key: CONTINUUM-34 > URL: http://jira.codehaus.org/browse/CONTINUUM-34 > Project: Continuum > Issue Type: Wish > Components: Core system >Reporter: David Blevins >Priority: Minor > Fix For: Future > > > I don't know if this is relevant to continuum's style of building, but > I have a script that scm updates then builds an m1 project with the default, > i.e. using just 'maven' with no goals supplied. This works the majority of > time, but every once in a while someone refactors something and i need to do > a clean build to really get everything to build. > The idea: > Have the concept of escalating the depth of the build till it works (or until > you've tried everything). If you find one that works send an email that > lists the exact steps (or maven command) required to get your build to work > again. > Example scenario 1: > $ cvs update -dP > $ maven > > BUILD FAILED > > $ maven clean default > > BUILD SUCCESSFUL > (email sent suggesting people do a 'maven clean default' after updating) > Example scenario 2: > $ cvs update -dP > $ maven > > BUILD FAILED > > $ maven clean default > > BUILD FAILED > $ cvs co alanparsons > $ cd alanparsons > $ maven > > BUILD SUCCESSFUL > (email sent suggesting people get a clean checkout of the alanparsons project > before attempting to 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-801) Maven2: Add Project Homepage URL to the project info page and build result page.
[ http://jira.codehaus.org/browse/CONTINUUM-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-801: -- Fix Version/s: 1.1-alpha-2 > Maven2: Add Project Homepage URL to the project info page and build result > page. > > > Key: CONTINUUM-801 > URL: http://jira.codehaus.org/browse/CONTINUUM-801 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Sharmarke Aden >Priority: Minor > Fix For: 1.1-alpha-2 > > Attachments: continuum_webinterface_homepage.patch > > > In maven 2 you can specify a URL for your project's homepage in the pom.xml. > It would be nice if a link to this URL could be show on the project info page > and the build result page of continuum web interface. > Attached is a patch that adds a row containing project homepage to both > View.vm and ProjectBuild.vm if the property "$project.url" exists. -- 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: (NMAVEN-2) NMaven Support for Classifiers
[ http://jira.codehaus.org/browse/NMAVEN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89830 ] Shane Isbell commented on NMAVEN-2: --- Some discussions occurred on the nmaven-dev list on this issue. According to Brett, the intended behavior of maven is to have one pom for multiple classifiers. Defaulting to this behavior may solve the issue, but still need to investigate the implications since NMaven is centered about the nmaven-settings file, not the profiles within the pom.xml file. > NMaven Support for Classifiers > -- > > Key: NMAVEN-2 > URL: http://jira.codehaus.org/browse/NMAVEN-2 > Project: NMaven > Issue Type: Improvement >Reporter: Shane Isbell >Priority: Minor > > NMaven should support classifiers to allow: 1) multiple builds (depending on > framework) of the NMaven .NET assembly plugins; 2) the use of 3rd party > assemblies that target a specific framework version. Support may require a > change with Maven core. One possible approach would be that whatever methods > (within Maven core) that are invoking > ArtifactRepositoryLayout.pathOf(pomArtifact) should set the classifier > information within the pomArtifact. > To provide context of this issue, I prototyped a version of NMaven that > supported classifiers but ran into an issue with Maven. NMaven does not put > meta-data - like the version or classifier - in the file name but rather > within the artifact directory structure. In the case of version, this is > fairly easy to handle because both the pomArtifact and the binaryArtifact > contain the version information: the ArtifactRepositoryLayout.pathOf method > can append the version to the artifact path. In the case of classifier, the > pomArtifact does not contain the classifier information ( > artifact.getClassifier() returns null): the ArtifactRepositoryLayout.pathOf > method has no way to append the classifier to the artifact path for the pom. > Thus under the current Maven version, we are unable to handle transitive > dependencies for artifacts with classifiers (due to not finding the pom > artifact). -- 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-932) Admin Connection to embedded derby database
[ http://jira.codehaus.org/browse/CONTINUUM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-932. - Assignee: Jesse McConnell Resolution: Fixed Fix Version/s: 1.1-alpha-1 I captured this tidbit in http://docs.codehaus.org/display/CONTINUUM/Database+Configuration > Admin Connection to embedded derby database > --- > > Key: CONTINUUM-932 > URL: http://jira.codehaus.org/browse/CONTINUUM-932 > Project: Continuum > Issue Type: New Feature > Components: Database >Reporter: Michael Locher > Assigned To: Jesse McConnell >Priority: Minor > Fix For: 1.1-alpha-1 > > Attachments: embeddedDerby.xml > > > Please include an ant projectfile which can be invoked to get an ij Session > on the embedded Derby database. > This is usefull if the database is corrupt and the admin needs to issue some > sql statements. > e.g The file could be located in the bin directory and be named as > 'embeddedDerby.xml' > the admin would attach to the database with the following command: 'ant -f > embeddedDerby.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-789) Show SCM branch/tag on summary screen
[ http://jira.codehaus.org/browse/CONTINUUM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-789: -- Fix Version/s: 1.1-alpha-# > Show SCM branch/tag on summary screen > - > > Key: CONTINUUM-789 > URL: http://jira.codehaus.org/browse/CONTINUUM-789 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: thierry lach >Priority: Minor > Fix For: 1.1-alpha-# > > > Since there may be multiple revisions of a project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-969) Problem with french characters in subversion log
[ http://jira.codehaus.org/browse/CONTINUUM-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-969: -- Fix Version/s: 1.1-alpha-# > Problem with french characters in subversion log > > > Key: CONTINUUM-969 > URL: http://jira.codehaus.org/browse/CONTINUUM-969 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 > Environment: french language >Reporter: Dominique Jean-Prost >Priority: Minor > Fix For: 1.1-alpha-# > > > In the changes area of the build result, the scm log doesn't deal french > characters from subversion correctly : it shows > correction des d?\195?\169pendances suite ?\195?\160 erreur de manip > instead of > correction des dépendances suite à erreur de manip -- 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
