Home / Browse / Artifactory / Mail / Archive

Artifactory

Email Archive: artifactory-developers (read-only)

2007:	_Jan	_Feb	_Mar (84)	_Apr (76)	_May (60)	_Jun (50)	_Jul (152)	_Aug (26)	_Sep (35)	_Oct (47)	_Nov (40)	_Dec (37)
2008:	_Jan (25)	_Feb (24)	_Mar (32)	_Apr (37)	_May (11)	_Jun (53)	_Jul (39)	_Aug (123)	_Sep (98)	_Oct (63)	_Nov (113)	_Dec (131)
2009:	_Jan (55)	_Feb (42)	_Mar (31)	_Apr (26)	_May (26)	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec
2011:	_Jan	_Feb	_Mar	_Apr	_May	_Jun	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec (2)


S	M	T	W	T	F	S
					1	2

3	4	5	6	7	8	9
(1)		(5)	(15)	(5)
10	11	12	13	14	15	16
(16)	(6)	(6)	(4)	(3)		(1)
17	18	19	20	21	22	23
(2)		(12)	(4)	(3)	(8)	(4)
24	25	26	27	28	29	30
(2)	(5)	(4)	(2)	(3)	(5)
31
(7)

[Artifactory-developers] [JIRA jfrog] Created: (RTFACT-582) Use a dedicated property in fsitem info to record the creation date

From: Yoav Landman (JIRA) <jira@jf...> - 2008-08-25 23:06

Use a dedicated property in fsitem info to record the creation date
-------------------------------------------------------------------

                 Key: RTFACT-582
                 URL: http://www.jfrog.org/jira/browse/RTFACT-582
             Project: Artifactory
          Issue Type: Bug
          Components: Artifact Storage
            Reporter: Yoav Landman
            Assignee: Yoav Landman
            Priority: Minor
             Fix For: 1.3.0-beta3


since jcr:created is not updated when deploying over an existing node (see: RTFACT-581).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.jfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Artifactory-developers] [JIRA jfrog] Resolved: (RTFACT-582) Use a dedicated property in fsitem info to record the creation date

From: Yoav Landman (JIRA) <jira@jf...> - 2008-08-25 23:11

[ http://www.jfrog.org/jira/browse/RTFACT-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yoav Landman resolved RTFACT-582.
---------------------------------

    Resolution: Fixed

> Use a dedicated property in fsitem info to record the creation date
> -------------------------------------------------------------------
>
>                 Key: RTFACT-582
>                 URL: http://www.jfrog.org/jira/browse/RTFACT-582
>             Project: Artifactory
>          Issue Type: Bug
>          Components: Artifact Storage
>            Reporter: Yoav Landman
>            Assignee: Yoav Landman
>            Priority: Minor
>             Fix For: 1.3.0-beta3
>
>
> since jcr:created is not updated when deploying over an existing node (see: RTFACT-581).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.jfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Artifactory-developers] [JIRA jfrog] Created: (RTFACT-581) Random StaleItemStateException: has been modified externally on deploy

From: Yoav Landman (JIRA) <jira@jf...> - 2008-08-25 22:51

Random StaleItemStateException: has been modified externally on deploy
----------------------------------------------------------------------

                 Key: RTFACT-581
                 URL: http://www.jfrog.org/jira/browse/RTFACT-581
             Project: Artifactory
          Issue Type: Bug
          Components: Artifact Storage
            Reporter: Yoav Landman
            Assignee: Yoav Landman
            Priority: Critical
             Fix For: 1.3.0-beta3


This is caused by JCR-1554, due to the fact that we delete an exiting file/folder node prior to creating the newly deployed one

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.jfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Artifactory-developers] [JIRA jfrog] Resolved: (RTFACT-581) Random StaleItemStateException: has been modified externally on deploy

From: Yoav Landman (JIRA) <jira@jf...> - 2008-08-25 23:04

[ http://www.jfrog.org/jira/browse/RTFACT-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yoav Landman resolved RTFACT-581.
---------------------------------

    Resolution: Fixed

Worked around this by reusing the already exiting node for now (jcr:created date is now wrong).

> Random StaleItemStateException: has been modified externally on deploy
> ----------------------------------------------------------------------
>
>                 Key: RTFACT-581
>                 URL: http://www.jfrog.org/jira/browse/RTFACT-581
>             Project: Artifactory
>          Issue Type: Bug
>          Components: Artifact Storage
>            Reporter: Yoav Landman
>            Assignee: Yoav Landman
>            Priority: Critical
>             Fix For: 1.3.0-beta3
>
>
> This is caused by JCR-1554, due to the fact that we delete an exiting file/folder node prior to creating the newly deployed one

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.jfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Artifactory-developers] [JIRA jfrog] Created: (RTFACT-580) Make m2e index claculation file based

From: Yoav Landman (JIRA) <jira@jf...> - 2008-08-25 21:41

Make m2e index claculation file based
-------------------------------------

                 Key: RTFACT-580
                 URL: http://www.jfrog.org/jira/browse/RTFACT-580
             Project: Artifactory
          Issue Type: Improvement
          Components: Artifact Storage
            Reporter: Yoav Landman
            Assignee: Yoav Landman
             Fix For: 1.3.0-beta3


Use a temp file for the index, rather than using the Lucene RAMDirectory, which (temporarily) store the whole index in RAM. This is wasteful particularly with large indexes, such as repo1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.jfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira