You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(20) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(6) |
Feb
(7) |
Mar
(45) |
Apr
(9) |
May
(9) |
Jun
(11) |
Jul
(13) |
Aug
(2) |
Sep
(33) |
Oct
(10) |
Nov
(5) |
Dec
(6) |
2008 |
Jan
(4) |
Feb
(46) |
Mar
(18) |
Apr
(14) |
May
(7) |
Jun
(34) |
Jul
(16) |
Aug
(7) |
Sep
(5) |
Oct
|
Nov
(4) |
Dec
|
2009 |
Jan
|
Feb
(2) |
Mar
|
Apr
(3) |
May
(10) |
Jun
|
Jul
(16) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
2010 |
Jan
(9) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(9) |
Sep
(14) |
Oct
|
Nov
|
Dec
(4) |
2011 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(4) |
Nov
(2) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(4) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jeremy T. <je...@th...> - 2008-03-19 17:51:06
|
Peter, Okay, I've been looking through Fisheye, and found that revision 1216 was the last revision before you made the 2.1.0 release. So, could you possibly run the following command on SVN to create the 2.1.0 tag? This will make it easier for folks like me, who are deploying a custom version of 2.1.0 into production. We can check out that tag, and apply our patches to it, build from it, etc. svn copy -r 1216 http://j-trac.svn.sourceforge.net/viewvc/j-trac/trunk/jtrac http://j-trac.svn.sourceforge.net/viewvc/j-trac/tags/jtrac-2.1.0 -m "Forgot to tag at 2.1.0 release" Let me know what you think. Thanks! Jeremy Thomerson |
From: Peter T. <ptr...@gm...> - 2008-03-16 07:30:52
|
Hi, Posting a message from the forums to the mailing list: ===== I would love to use Jtrac on my macbook but cant seem to find the right way. I did a mv start.bat start.sh. If from within the finder i run start.sh something happens but no luck. With a sudo start.sh no thing happens. Please can one of the unix experts give me som tips? ===== If you have a solution, do reply on the forum thread here: https://sourceforge.net/forum/message.php?msg_id=4839861 Thanks, Peter. |
From: Peter T. <ptr...@gm...> - 2008-03-11 12:11:54
|
On 3/11/08, Saurabh Banerjee <sau...@ac...> wrote: > > My proposal is to have a space specific default "Assign To" target, so > that is never mandatory to fill in the "Assign To" > Okay. Under feature-requests, some users have asked for the option to allow the "Assign To" to be empty as well. Let's see if we can make this flexible. ------------------------------ > > *From:* j-t...@li... [mailto: > j-t...@li...] *On Behalf Of *Mihails > Agafonovs > *Sent:* Monday, March 10, 2008 9:08 PM > *To:* JTrac users mailing-list > *Subject:* Re: [jtrac-users] Question about JTrac > > > > Hey, you are right! For some projects it would be useful to have such a > bug report without assignment. > If you have a source code, I think it's not difficult to modify this. > > Quoting *thomas mauch <Tho...@sw...>*: > > Hi > > I just installed JTrac 2.1.0 and started browsing around. Here are a few > points: > > - I downloaded the User/Developer Guide. But I'am missing some very basic > information like (Introduction of the concepts used like users or spaces, > what standard fields exist, etc.) - is there another documentation? > > - Why is the "Assign To:" field mandatory? The normal situation that some > user/tester wants to enter a new bug report, but he will not care who will > fix the bug. The developers will then look at the list of newly created bug > reports and pick these which they are responsible for - how should this > situation be handled? > > - I tried to modify the default workflow with only Open and Closed to > modify to example shown in the user guide, but did not succeed. In the state > line of "New", only Open is clickable and I am not able to delete "Open" as > the "Delete" button is disabled - what am I missing? > > - If I export a search result to Excel, only the custom defined fields > (Severity, Priority) get a text in the header line, the other fields remain > blank > > Many Thanks, > > Thomas > > This message may contain legally privileged or confidential information > and is therefore addressed to the named persons only. The recipient should > inform the sender and delete this message, if he/she is not named as > addressee. The sender disclaims any and all liability for the integrity and > punctuality of this message. The sender has activated an automatic virus > scanning, but does not guarantee the virus free transmission of this > message. > > > > > Ar cieņu, Mihails > > |
From: Saurabh B. <sau...@ac...> - 2008-03-11 05:35:36
|
My proposal is to have a space specific default “Assign To” target, so that is never mandatory to fill in the “Assign To” _____ From: j-t...@li... [mailto:j-t...@li...] On Behalf Of Mihails Agafonovs Sent: Monday, March 10, 2008 9:08 PM To: JTrac users mailing-list Subject: Re: [jtrac-users] Question about JTrac Hey, you are right! For some projects it would be useful to have such a bug report without assignment. If you have a source code, I think it's not difficult to modify this. Quoting thomas mauch <Tho...@sw...>: Hi I just installed JTrac 2.1.0 and started browsing around. Here are a few points: - I downloaded the User/Developer Guide. But I'am missing some very basic information like (Introduction of the concepts used like users or spaces, what standard fields exist, etc.) - is there another documentation? - Why is the "Assign To:" field mandatory? The normal situation that some user/tester wants to enter a new bug report, but he will not care who will fix the bug. The developers will then look at the list of newly created bug reports and pick these which they are responsible for - how should this situation be handled? - I tried to modify the default workflow with only Open and Closed to modify to example shown in the user guide, but did not succeed. In the state line of "New", only Open is clickable and I am not able to delete "Open" as the "Delete" button is disabled - what am I missing? - If I export a search result to Excel, only the custom defined fields (Severity, Priority) get a text in the header line, the other fields remain blank Many Thanks, Thomas This message may contain legally privileged or confidential information and is therefore addressed to the named persons only. The recipient should inform the sender and delete this message, if he/she is not named as addressee. The sender disclaims any and all liability for the integrity and punctuality of this message. The sender has activated an automatic virus scanning, but does not guarantee the virus free transmission of this message. Ar cieņu, Mihails |
From: Peter T. <ptr...@gm...> - 2008-03-11 04:37:18
|
On 3/10/08, Mihails Agafonovs <_m...@in...> wrote: > > Hey, you are right! For some projects it would be useful to have such a > bug report without assignment. > If you have a source code, I think it's not difficult to modify this. > > Quoting *thomas mauch <Tho...@sw...>*: > > Hi > I just installed JTrac 2.1.0 and started browsing around. Here are a few > points: > - I downloaded the User/Developer Guide. But I'am missing some very basic > information like (Introduction of the concepts used like users or spaces, > what standard fields exist, etc.) - is there another documentation? > > Thanks for the feedback, we will try to improve the documentation to address this. You can think of Space as nothing but a "Project" the rest of the terms are straightforward. - Why is the "Assign To:" field mandatory? The normal situation that some > user/tester wants to enter a new bug report, but he will not care who will > fix the bug. The developers will then look at the list of newly created bug > reports and pick these which they are responsible for - how should this > situation be handled? > > Yes, this can be considered a limitation of JTrac at the moment and there is an open feature request for this. To work around this fo now, you could probably create a dummy user called "developers team" or something and ask your end-users to assign to this one. - I tried to modify the default workflow with only Open and Closed to modify > to example shown in the user guide, but did not succeed. In the state line > of "New", only Open is clickable and I am not able to delete "Open" as the > "Delete" button is disabled - what am I missing? > > At the moment the New and the Closed states are kind of fixed. You can have a look at this open feature request for more details: http://sourceforge.net/tracker/index.php?func=detail&aid=1776047&group_id=162983&atid=825944 - If I export a search result to Excel, only the custom defined fields > (Severity, Priority) get a text in the header line, the other fields remain > blank > > Try running a search specific to a Space (i.e. click on "SEARCH" where the Space name appears on the same line. If you have values for Severity and Priority but they don't appear in the Excel output, you can raise a bug. Many Thanks, > Thomas > > > > > Ar cieņu, Mihails > > > |
From: Mihails A. <_m...@in...> - 2008-03-10 15:37:48
|
Hey, you are right! For some projects it would be useful to have such a bug report without assignment. If you have a source code, I think it's not difficult to modify this. Quoting thomas mauch : /**/ Hi I just installed JTrac 2.1.0 and started browsing around. Here are a few points: - I downloaded the User/Developer Guide. But I'am missing some very basic information like (Introduction of the concepts used like users or spaces, what standard fields exist, etc.) - is there another documentation? - Why is the "Assign To:" field mandatory? The normal situation that some user/tester wants to enter a new bug report, but he will not care who will fix the bug. The developers will then look at the list of newly created bug reports and pick these which they are responsible for - how should this situation be handled? - I tried to modify the default workflow with only Open and Closed to modify to example shown in the user guide, but did not succeed. In the state line of "New", only Open is clickable and I am not able to delete "Open" as the "Delete" button is disabled - what am I missing? - If I export a search result to Excel, only the custom defined fields (Severity, Priority) get a text in the header line, the other fields remain blank Many Thanks, Thomas This message may contain legally privileged or confidential information and is therefore addressed to the named persons only. The recipient should inform the sender and delete this message, if he/she is not named as addressee. The sender disclaims any and all liability for the integrity and punctuality of this message. The sender has activated an automatic virus scanning, but does not guarantee the virus free transmission of this message. Ar cieņu, Mihails Links: ------ [1] mailto:Tho...@sw... |
From: thomas m. <Tho...@sw...> - 2008-03-10 15:26:52
|
Hi I just installed JTrac 2.1.0 and started browsing around. Here are a few points: - I downloaded the User/Developer Guide. But I'am missing some very basic information like (Introduction of the concepts used like users or spaces, what standard fields exist, etc.) - is there another documentation? - Why is the "Assign To:" field mandatory? The normal situation that some user/tester wants to enter a new bug report, but he will not care who will fix the bug. The developers will then look at the list of newly created bug reports and pick these which they are responsible for - how should this situation be handled? - I tried to modify the default workflow with only Open and Closed to modify to example shown in the user guide, but did not succeed. In the state line of "New", only Open is clickable and I am not able to delete "Open" as the "Delete" button is disabled - what am I missing? - If I export a search result to Excel, only the custom defined fields (Severity, Priority) get a text in the header line, the other fields remain blank Many Thanks, Thomas This message may contain legally privileged or confidential information and is therefore addressed to the named persons only. The recipient should inform the sender and delete this message, if he/she is not named as addressee. The sender disclaims any and all liability for the integrity and punctuality of this message. The sender has activated an automatic virus scanning, but does not guarantee the virus free transmission of this message. |
From: Peter T. <ptr...@gm...> - 2008-03-07 17:03:21
|
There were quite a few bugs in yesterdays development build, this one should be much better. For the benefit of those who just joined the mailing list, this version introduces bookmarkable search result URLs. So just after clicking "Submit" on the search filter screen, when you see the first page of results - this should be bookmarkable. This build also should take care of security, you should not be able to see items belonging to Spaces that you are not allocated to. Instructions as always: http://jtrac.info/doc/html/interim-builds.html Do help test this! Thanks, Peter. |
From: Peter T. <ptr...@gm...> - 2008-03-06 19:07:37
|
Hi, A new development build that includes the bookmarkable search results feature (mentioned in the previous mail) has been uploaded. This would need testing as it is a somewhat extensive change to the internals. Instructions on interim builds here: http://jtrac.info/doc/html/interim-builds.html There are no database schema changes. Thanks, Peter. |
From: Peter T. <ptr...@gm...> - 2008-03-06 14:59:00
|
Hi, A somewhat extensive set of updates were just committed as r1229, it would be great if those building out of version control can help test this, not sure yet when an interim build can be uploaded. This change makes it possible to bookmark search results. When you click submit on the search screen the URL of the search results page would have a URL that you can save as a bookmark. Hopefully this change would make that most requested feature "saved searches" possible soon as well as RSS feeds. However this may open up some security issues - changing stuff in the URL could potentially allow you to see search results from spaces you have not been allocated to, this needs a little more work. The reason for stepping up work on this front is primarily for Mylar integration: https://bugs.eclipse.org/bugs/show_bug.cgi?id=221113 So those who have been asking for Mylar integration can keep track of this development. Thanks, Peter. |
From: Eric B. <be...@su...> - 2008-03-06 08:57:12
|
Thanks for your answers. The problem is that group email are not allowed in my organisation. I still think a functionality like I describe have to be included in jtrac. Regards, On Thu, Mar 6, 2008 at 5:42 AM, Saurabh Banerjee < sau...@ac...> wrote: > Using a group email ID is the way to go. Create a dummy user with a group > email ID and use it as an assignment target. > > > -----Original Message----- > From: j-t...@li... > [mailto:j-t...@li...] On Behalf Of TimP > Sent: Thursday, March 06, 2008 1:15 AM > To: JTrac users mailing-list > Subject: Re: [jtrac-users] Set multiple email to a jtrac user > > On Wednesday 05 March 2008 16:31, Eric Bellard wrote: > > Hi, > > In order to adapt jtrac to my company I'd like to add more than one > email > > to a single jtrac user. > > For us it's particularly useful during a new item creation: the item is > > assigned to a un-personified user with multiple email > > => everyone in the team is informed, someone take the item and the item > is > > assigned to him. > > [snip] > > > > Maybe you could add something like this in the main version. > > > > Regards, > > Would not the same requirement be easier handled by using a group alias > email address? > > The item is initially assigned to the group, > all members of which get a copy of the email, > one can then 'take' the item. > > I think this works better than breaking the one to one relationship > between > actors and email addresses. > > yours > TimP > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > j-trac-users mailing list > j-t...@li... > https://lists.sourceforge.net/lists/listinfo/j-trac-users > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > j-trac-users mailing list > j-t...@li... > https://lists.sourceforge.net/lists/listinfo/j-trac-users > |
From: Saurabh B. <sau...@ac...> - 2008-03-06 04:43:08
|
Using a group email ID is the way to go. Create a dummy user with a group email ID and use it as an assignment target. -----Original Message----- From: j-t...@li... [mailto:j-t...@li...] On Behalf Of TimP Sent: Thursday, March 06, 2008 1:15 AM To: JTrac users mailing-list Subject: Re: [jtrac-users] Set multiple email to a jtrac user On Wednesday 05 March 2008 16:31, Eric Bellard wrote: > Hi, > In order to adapt jtrac to my company I'd like to add more than one email > to a single jtrac user. > For us it's particularly useful during a new item creation: the item is > assigned to a un-personified user with multiple email > => everyone in the team is informed, someone take the item and the item is > assigned to him. [snip] > > Maybe you could add something like this in the main version. > > Regards, Would not the same requirement be easier handled by using a group alias email address? The item is initially assigned to the group, all members of which get a copy of the email, one can then 'take' the item. I think this works better than breaking the one to one relationship between actors and email addresses. yours TimP ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ j-trac-users mailing list j-t...@li... https://lists.sourceforge.net/lists/listinfo/j-trac-users |
From: TimP <tim...@pa...> - 2008-03-05 19:47:20
|
On Wednesday 05 March 2008 16:31, Eric Bellard wrote: > Hi, > In order to adapt jtrac to my company I'd like to add more than one email > to a single jtrac user. > For us it's particularly useful during a new item creation: the item is > assigned to a un-personified user with multiple email > => everyone in the team is informed, someone take the item and the item is > assigned to him. [snip] > > Maybe you could add something like this in the main version. > > Regards, Would not the same requirement be easier handled by using a group alias email address? The item is initially assigned to the group, all members of which get a copy of the email, one can then 'take' the item. I think this works better than breaking the one to one relationship between actors and email addresses. yours TimP |
From: Eric B. <be...@su...> - 2008-03-05 16:31:17
|
Hi, In order to adapt jtrac to my company I'd like to add more than one email to a single jtrac user. For us it's particularly useful during a new item creation: the item is assigned to a un-personified user with multiple email => everyone in the team is informed, someone take the item and the item is assigned to him. - In the user creation/edit windows: multiple emails are set (separated with a comma, no space) - I've modified the MailSender.java class to manage multiple email: + in the send mail method i've modified the set TO part: // set TO if (item.getAssignedTo() != null) { setTos(helper, item.getAssignedTo().getEmail()); } else { setTos(helper, item.getLoggedBy().getEmail()); } + I've added the following setTos method to handle multiple email in set TO /** * Set multiple recipient in a message. The multiple recipient are separated * with a comma. * * @param helper * spring mime message helper * @param s * recipients * @throws MessagingException */ public final static void setTos(MimeMessageHelper helper, String s) throws Exception { if (s == null || s.equals("") || !s.contains(",")) { helper.setTo(s); } else { StringTokenizer st = new StringTokenizer(s, ","); while (st.hasMoreTokens()) { helper.addTo(st.nextToken()); } } } Maybe you could add something like this in the main version. Regards, -- Eric Bellard |
From: Michael G. <mic...@gm...> - 2008-03-04 21:02:36
|
Hi Peter, thanks you for JTrack. It's really a great piece of software. It's very light compared to Jira but has the core features that are really important. Looking at the roadmap I'm really keen on the timetracking facility. @ldap I would appreciate if there'd be an interface to authorize user from ldap. That would make central administration possible. Regards, Michael Gerzabek -- michaelgerzabek.com® - Business The Artist's Way ptrthomas wrote: > > From what little I've seen of LDAP so far, it looks like people have > widely > different conventions and requirements for auto-mapping. I was thinking > that for now we could make this pluggable - so end users can implement an > interface, add the class to the classpath and have this work the way they > want. Do let me know what you think. > -- View this message in context: http://www.nabble.com/Extending-LDAP-support-to-include-authorization-tp12653643p15836997.html Sent from the j-trac-users mailing list archive at Nabble.com. |
From: Manos B. <man...@ge...> - 2008-03-03 15:10:45
|
> On Wednesday 20 February 2008 09:06, Manos Batsis wrote: >> Quoting Peter Thomas : >>> This feature - of being able to move items across spaces has not been >>> implemented yet. There was a patch submitted for this which I have >>> not >>> fully gone through - but you may be able to try it out: >> http://sourceforge.net/tracker/index.php?func=detail&aid=1793860&group_id=1 >> 62983&atid=825943 >> >> >> Actually we did this "the right way" a week after submitting the patch, >> but haven't found the time to submit a new one. Will try to do this >> against the trunk if the OP is interested. Just added the updated version of the patch to [1], along with some documentation. Please send an email to info at abiss.gr if you need anything regarding this patch, including a signed contributor agreement if you feel too formal ;-) [1] http://sourceforge.net/tracker/index.php?func=detail&aid=1793860&group_id=162983&atid=825943 Cheers, Manos |
From: Peter T. <ptr...@gm...> - 2008-03-02 17:07:39
|
Finally JTrac 2.1.0 (final) has been released. Go get it now: http//jtrac.info |
From: Peter T. <ptr...@gm...> - 2008-02-28 20:05:13
|
Hi, The Chinese translation is ready and JTrac 2.1.0 will be released over the weekend, and that is a promise! Do take a minute to see (and contribute to) the brand new "References & Testimonials" page that is up on the web-site: http://j-trac.wiki.sourceforge.net/references With this release out of the way - it will be time to discuss how to go about all the feature requests that have piled up. Thanks, Peter. On Tue, Feb 26, 2008 at 11:39 PM, Peter Thomas <ptr...@gm...> wrote: > Hi, > > JTrac 2.1.0 final will be released as soon as the Chinese translation that > someone promised will be ready soon - is checked in. > > So far no problems have been reported for the last interim build > 2.1.0-dev10. So if you have held off on using 2.1.0-beta till now just > because of the 'beta' - you can consider putting into production the latest > interim build - in case you are impatient. > > Details on how to get the latest interim build are here: > http://jtrac.info/doc/html/interim-builds.html > > Thanks, > > Peter. > > > > On 2/15/08, Peter Thomas <ptr...@gm...> wrote: > > > > Hi, > > > > Apologies for the increased activity on the mailing list. I guess this > > happens when there is an impending release. > > > > Please do take some time to review the JTrac web-site [ > > http://jtrac.info ] - especially the documentation. The site has just > > been refreshed (you may need to refresh your browser) and for example, there > > is an updated FAQ section which provides links to the JTrac bug and feature > > requests trackers. There are couple of TODO items which is still work in > > progress. But do respond with your comments on: > > > > - do you see any of your favourite features missing in the online > > documentation? > > - do you have any suggestions for more content - for example an > > additional FAQ item? > > - would a couple more screenshots help? > > > > Also if you have contributed a translation (or can update an existing > > one) please help before we release 2.1.0 final. > > > > Thanks, > > > > Peter. > > > > > |
From: Peter T. <ptr...@gm...> - 2008-02-26 18:09:24
|
Hi, JTrac 2.1.0 final will be released as soon as the Chinese translation that someone promised will be ready soon - is checked in. So far no problems have been reported for the last interim build 2.1.0-dev10. So if you have held off on using 2.1.0-beta till now just because of the 'beta' - you can consider putting into production the latest interim build - in case you are impatient. Details on how to get the latest interim build are here: http://jtrac.info/doc/html/interim-builds.html Thanks, Peter. On 2/15/08, Peter Thomas <ptr...@gm...> wrote: > > Hi, > > Apologies for the increased activity on the mailing list. I guess this > happens when there is an impending release. > > Please do take some time to review the JTrac web-site [ http://jtrac.info] - especially the documentation. The site has just been refreshed (you may > need to refresh your browser) and for example, there is an updated FAQ > section which provides links to the JTrac bug and feature requests > trackers. There are couple of TODO items which is still work in progress. > But do respond with your comments on: > > - do you see any of your favourite features missing in the online > documentation? > - do you have any suggestions for more content - for example an > additional FAQ item? > - would a couple more screenshots help? > > Also if you have contributed a translation (or can update an existing one) > please help before we release 2.1.0 final. > > Thanks, > > Peter. > > |
From: TimP <tim...@pa...> - 2008-02-20 18:14:39
|
On Wednesday 20 February 2008 09:06, Manos Batsis wrote: > Quoting Peter Thomas : > > This feature - of being able to move items across spaces has not been > > implemented yet. There was a patch submitted for this which I have > > not > > fully gone through - but you may be able to try it out: > > http://sourceforge.net/tracker/index.php?func=detail&aid=1793860&group_id=1 >62983&atid=825943 > > > Actually we did this "the right way" a week after submitting the patch, > but haven't found the time to submit a new one. Will try to do this > against the trunk if the OP is interested. > > Cheers, > > Manos I have hacked my particular problem now, so I don't need it, happy to wait until it comes into the trunk. cheers timp |
From: Manos B. <man...@ge...> - 2008-02-20 09:06:58
|
Quoting Peter Thomas <ptr...@gm...>: > > This feature - of being able to move items across spaces has not been > implemented yet. There was a patch submitted for this which I have > not > fully gone through - but you may be able to try it out: > > http://sourceforge.net/tracker/index.php?func=detail&aid=1793860&group_id=162983&atid=825943 Actually we did this "the right way" a week after submitting the patch, but haven't found the time to submit a new one. Will try to do this against the trunk if the OP is interested. Cheers, Manos |
From: Peter T. <ptr...@gm...> - 2008-02-20 04:47:50
|
On 2/20/08, TimP <tim...@pa...> wrote: > > Hi, > > I have looked at the manual but couldn't spot the answer to this. > > How does one move an item to a newly created space? > > I achieved it by changing the space key of the item, (using Melati) > which seems to have worked, the item still has its id from the old space, > but nothing seems to have actually broken. > > cheers > TimP This feature - of being able to move items across spaces has not been implemented yet. There was a patch submitted for this which I have not fully gone through - but you may be able to try it out: http://sourceforge.net/tracker/index.php?func=detail&aid=1793860&group_id=162983&atid=825943 - Peter. |
From: TimP <tim...@pa...> - 2008-02-19 19:06:25
|
Hi, I have looked at the manual but couldn't spot the answer to this. How does one move an item to a newly created space? I achieved it by changing the space key of the item, (using Melati) which seems to have worked, the item still has its id from the old space, but nothing seems to have actually broken. cheers TimP |
From: TimP <tim...@pa...> - 2008-02-19 18:47:10
|
On Tuesday 19 February 2008 12:17, Peter Thomas wrote: > On 2/19/08, TimP wrote: > > Hi, > > > > I have been using jtrac with Melati (http://melati.org/). > > > > > > I am not suggesting that this is attractive or of use to anyone else, > > but it may be of interest. > > > > I attach a patch against the current SVN tree, (very top level). > > > > It also fixes the recent 'Version 0.0.0' issue. > > > > > > cheers > > TimP > > Regarding the 'Version 0.0.0' so-called issue IMHO the right way to fix > this is to just have a "jtrac-version.properties" file in the classpath ( > src/main/resources ) containing the entry "version=2.1.0" If this file > does not exist, JTrac defaults to 0.0.0 (which IMHO is better than not > starting at all). > > When a JTrac release is made, the build process takes care of managing the > jtrac-version.properties file. If you are building JTrac yourself, you > should manage this process yourself. OK, so running with mvn jetty:run 0.0.0 is the expected behaviour. thanks TimP |
From: TimP <tim...@pa...> - 2008-02-19 18:45:49
|
On Tuesday 19 February 2008 11:38, Mihails Agafonovs wrote: > Hi! > Can you describe how to install it to work with JTrac? Do not use this with a jtrac installation. It is just a demonstration, for info only. It is a patch and so should be applied using subversion to a clean checkout of the topmost jtrac tree. > I can't even checkout it :( Not sure what you are doing, happy to help. Again, do not apply this patch to a valuable installation, it is just for information and demonstration. cheers TimP |