[
http://jira.codehaus.org/browse/MNG-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146184#action_146184
]
Christian Gruber commented on MNG-2802:
---
Frankly, one could mitigate this substantially by
POJO tests have only partially implemented fixture support
--
Key: SUREFIRE-498
URL: http://jira.codehaus.org/browse/SUREFIRE-498
Project: Maven Surefire
Issue Type: Bug
[
http://jira.codehaus.org/browse/SUREFIRE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Gruber updated SUREFIRE-498:
--
Attachment: fixture.diff
This is a better diff, which is applied not to surefire-api but
[
http://jira.codehaus.org/browse/CONTINUUM-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103704
]
Christian Gruber commented on CONTINUUM-1356:
-
Tried it on my mac, and I still get the three failures. All
[
http://jira.codehaus.org/browse/MRELEASE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90825
]
Christian Gruber commented on MRELEASE-146:
---
Sadly, I can't. I have returned my laptop and now have a MacBook
Please sync israfil.net with ibiblio's maven2 repo
--
Key: MAVENUPLOAD-1342
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1342
Project: maven-upload-requests
Issue Type: New Feature
[ http://jira.codehaus.org/browse/MEV-474?page=all ]
Christian Gruber reopened MEV-474:
--
RE-opening, since it's not fixed, and Im going to attach the proper package.
I'm not affiliated with the hibernate project, but if someone wants to
[ http://jira.codehaus.org/browse/MEV-474?page=all ]
Christian Gruber updated MEV-474:
-
Attachment: hibernate-annotations-3.2.1.ga.package.jar
Attach package for deployment.
Hibernate Annotations 3.2.1ga is not deployed, though it was released, and
[ http://jira.codehaus.org/browse/MEV-474?page=all ]
Christian Gruber updated MEV-474:
-
Attachment: hibernate-annotations-3.2.1.ga.package.jar
Aaagh. Wrong pom.xml file was included. This version should be correct.
Hibernate Annotations 3.2.1ga is
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
Hibernate Annotations 3.2.1ga is not deployed, though it was released, and
hibernate core 3.2.1ga is released
-
Key: MEV-474
URL:
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
Remove button on project group actions is not available on a group that
contains no projects
--
Key: CONTINUUM-1019
URL: http://jira.codehaus.org/browse/CONTINUUM-1019
[ http://jira.codehaus.org/browse/CONTINUUM-993?page=all ]
Christian Gruber closed CONTINUUM-993.
--
Resolution: Fixed
Fix Version/s: 1.1
Fixed in trunk at some point since the bug was opened - not clear who fixed it
or how, but probably was
Insert the project group summary tab into the normal project view to allow
easy navigation back to project group level
Key: CONTINUUM-1020
[ http://jira.codehaus.org/browse/CONTINUUM-987?page=comments#action_79266
]
Christian Gruber commented on CONTINUUM-987:
Notifiers are present, at least under the hood. However, it's still not
showing the e-mail address of the
Project info details no longer showing up in UI, and the edit button is gone as
well.
-
Key: CONTINUUM-993
URL: http://jira.codehaus.org/browse/CONTINUUM-993
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
Email not captured when creating notifier
-
Key: CONTINUUM-985
URL: http://jira.codehaus.org/browse/CONTINUUM-985
Project: Continuum
Issue Type: Bug
Components: Web interface
Affects
After deleting a project from a group, the UI flow should return to the group
summary display.
--
Key: CONTINUUM-980
URL: http://jira.codehaus.org/browse/CONTINUUM-980
Remove button on group actions is ambiguous and should be renamed Delete
Group or Remove Group.
-
Key: CONTINUUM-981
URL:
Project Group Actions should be renamed Group Actions to avoid confusion.
-
Key: CONTINUUM-982
URL: http://jira.codehaus.org/browse/CONTINUUM-982
Project: Continuum
[ http://jira.codehaus.org/browse/CONTINUUM-986?page=comments#action_78962
]
Christian Gruber commented on CONTINUUM-986:
For example, unlike the delete button, which does:
[ http://jira.codehaus.org/browse/CONTINUUM-987?page=comments#action_78961
]
Christian Gruber commented on CONTINUUM-987:
They may actually be present - I got a set of notifications that I wasn't
expecting. However, they are not
Group information in group summary screen mistakenly has the heading Project
Group Actions. Should be Group Information or something similar.
--
Notifiers in the pom.xml files are no longer being picked up by Continuum.
---
Key: CONTINUUM-987
URL: http://jira.codehaus.org/browse/CONTINUUM-987
Project: Continuum
Edit group notifier gets a page not found problem
---
Key: CONTINUUM-986
URL: http://jira.codehaus.org/browse/CONTINUUM-986
Project: Continuum
Issue Type: Bug
Components: Web
typo of variable name projectGroupId on buildDefinitionGroupSummaryComponent.jsp
Key: CONTINUUM-959
URL: http://jira.codehaus.org/browse/CONTINUUM-959
Project: Continuum
deployment repository should be required and have a default in initial
continuum setup.
---
Key: CONTINUUM-955
URL: http://jira.codehaus.org/browse/CONTINUUM-955
[ http://jira.codehaus.org/browse/CONTINUUM-955?page=all ]
Christian Gruber updated CONTINUUM-955:
---
Attachment: make_deployment_dir_default.diff
Proper patch, since the earlier one only reflected the webapp project by
mistake.
deployment
Edit Build Definition action in xwork.xml has the wrong result defined
--
Key: CONTINUUM-947
URL: http://jira.codehaus.org/browse/CONTINUUM-947
Project: Continuum
Issue
xwork.xml has relative urls to target jsps causing problems with invocation
from any .jsp not in the webapp root folder.
Key: CONTINUUM-951
Cross Site Request Forgery protection
-
Key: CONTINUUM-838
URL: http://jira.codehaus.org/browse/CONTINUUM-838
Project: Continuum
Issue Type: Improvement
Components: Web interface
Affects
Editing a user changes the password to what's submitted, which by default is
(empty string).
---
Key: CONTINUUM-839
URL: http://jira.codehaus.org/browse/CONTINUUM-839
[ http://jira.codehaus.org/browse/SCM-213?page=comments#action_71617 ]
Christian Gruber commented on SCM-213:
--
Even if they're windows apps, the SVN app is (in the above case) from Cygwin,
and should understand c:/blah/foo as an absolute
Release tag with SVN under Cygwin fails when sending the svn command a bad
absolute path
Key: MRELEASE-146
URL: http://jira.codehaus.org/browse/MRELEASE-146
[ http://jira.codehaus.org/browse/CONTINUUM-741?page=comments#action_68510
]
Christian Gruber commented on CONTINUUM-741:
The other important thing (and I'm not sure if that needs to be stated here or
elsewhere), is that if you have a parent
[ http://jira.codehaus.org/browse/CONTINUUM-549?page=comments#action_65756
]
Christian Gruber commented on CONTINUUM-549:
I firmly support this as a build definition option. I believe that it should
be an option that it build in all cases of
Build Numbers are obscured by the queuing/building icon
---
Key: CONTINUUM-691
URL: http://jira.codehaus.org/browse/CONTINUUM-691
Project: Continuum
Type: Bug
Components: Web interface
Versions: 1.0.3
Add specific continuum values as variables on build parameters input
Key: CONTINUUM-692
URL: http://jira.codehaus.org/browse/CONTINUUM-692
Project: Continuum
Type: New Feature
Components: Web
Make builds optionally build even when there are no changes
---
Key: CONTINUUM-685
URL: http://jira.codehaus.org/browse/CONTINUUM-685
Project: Continuum
Type: Improvement
Components: Web interface, Core
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
[ http://jira.codehaus.org/browse/CONTINUUM-685?page=comments#action_64940
]
Christian Gruber commented on CONTINUUM-685:
I linked this to CONTINUUM-686 (separate workspaces per build per project)
because 686 is a possible solution for this
[ http://jira.codehaus.org/browse/CONTINUUM-37?page=comments#action_64947 ]
Christian Gruber commented on CONTINUUM-37:
---
Even simpler would be some basic ajax interaction with the server, to update
the build log, update the build status on the
[ http://jira.codehaus.org/browse/CONTINUUM-265?page=comments#action_64948
]
Christian Gruber commented on CONTINUUM-265:
This would be highly useful, especially in situations where you have peers in a
dependency chain, but would require a fair
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
[ http://jira.codehaus.org/browse/CONTINUUM-685?page=all ]
Christian Gruber closed CONTINUUM-685:
--
Resolution: Duplicate
Make builds optionally build even when there are no changes
---
[ http://jira.codehaus.org/browse/CONTINUUM-682?page=comments#action_64955
]
Christian Gruber commented on CONTINUUM-682:
Workaround is to set a schedule not in the past, but vastly in the future. (I
use 2061, 'cause I like Arthur C. Clarke).
Insecure html in build output leads to bad html rendering - could be used for
malicious cross-site scripting.
-
Key: CONTINUUM-679
URL:
Strange behaviour when guest enabled but has no privs.
--
Key: CONTINUUM-680
URL: http://jira.codehaus.org/browse/CONTINUUM-680
Project: Continuum
Type: Bug
Components: Web interface
Versions: 1.0.3
Run As Maven menu option no longer saves goals, now it acts like Run as
Maven...
-
Key: MNGECLIPSE-119
URL: http://jira.codehaus.org/browse/MNGECLIPSE-119
Project: Maven 2.x Extension for
51 matches
Mail list logo