Nabble - Artifactory-Developers

[JFrog JIRA] Resolved: (RTFACT-1028) Fetching index files failed

2008-11-22T01:02:16Z

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

Yoav Landman resolved RTFACT-1028.
----------------------------------

Fix Version/s: 1.3.0
Resolution: Fixed

Ok, we managed to reproduce it and the real cause of the problem is that when the central snapshot policy for a local repository is on non-unique (the default) snapshots are still deployed as unique. The workaround is either to use a unique snapshot policy or to use the deployer snapshot policy and specify non-unique for snapshots in the maven client's repository definition.
I have created RTFACT-1030 and we already fixed it. We might publish a minor beta upgrade for this.

> Fetching index files failed
> ---------------------------
>
> Key: RTFACT-1028
> URL: http://www.jfrog.org/jira/browse/RTFACT-1028
> Project: Artifactory
> Issue Type: Bug
> Affects Versions: 1.3.0-beta-6
> Environment: Jetty 5.1.14, JDK 6, Ubuntu Hardy
> Reporter: Craig
> Assignee: Yoav Landman
> Priority: Critical
> Fix For: 1.3.0
>
>
> I just installed artifactory 1.3.0 beta 6 and set up a local repository called "third-party." I was able to deploy a SNAPSHOT artifact to it (using mvn deploy). The two deployed artifacts are com.molecular.logger:loggerMaster and com.molecular.logger:logger. Then I attempting to build another project which depended on this SNAPSHOT and got this error from maven:
> [INFO] Error building POM (may not be this project's POM).
> Project ID: com.molecular.logger:logger:jar:1.0-SNAPSHOT
> Reason: Cannot find parent: com.molecular.logger:loggerMaster for project: com.molecular.logger:logger:jar:1.0-SNAPSHOT for project com.molecular.logger:logger:jar:1.0-SNAPSHOT
> So I looked in the artifactory logs, and saw this:
> 2008-11-22 06:01:29,630 [ERROR] (o.a.r.i.IndexerManagerImpl:176) - Fetching index files failed.
> java.lang.RuntimeException: Failed to index repository 'third-party'.
> at org.artifactory.repo.index.RepoIndexerData.createIndex(RepoIndexerData.java:133) [artifactory-core-1.3.0-beta-6.jar:na]
> at org.artifactory.repo.index.IndexerManagerImpl.findOrCreateIndex(IndexerManagerImpl.java:204) [artifactory-core-1.3.0-beta-6.jar:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na:1.6.0_0]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [na:1.6.0_0]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [na:1.6.0_0]
> at java.lang.reflect.Method.invoke(Method.java:616) [na:1.6.0_0]
> at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) [spring-aop-2.5.5.jar:2.5.5]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) [spring-aop-2.5.5.jar:2.5.5]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) [spring-aop-2.5.5.jar:2.5.5]
> at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) [spring-tx-2.5.5.jar:2.5.5]
> at org.artifactory.jcr.lock.LockingAdvice.invoke(LockingAdvice.java:79) [artifactory-core-1.3.0-beta-6.jar:na]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) [spring-aop-2.5.5.jar:2.5.5]
> at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) [spring-aop-2.5.5.jar:2.5.5]
> at $Proxy16.findOrCreateIndex(Unknown Source) [na:na]
> at org.artifactory.repo.index.IndexerManagerImpl$FindOrCreateIndexJob.onExecute(IndexerManagerImpl.java:174) [artifactory-core-1.3.0-beta-6.jar:na]
> at org.artifactory.repo.index.IndexerManagerImpl$FindOrCreateIndexJob.onExecute(IndexerManagerImpl.java:166) [artifactory-core-1.3.0-beta-6.jar:na]
> at org.artifactory.schedule.quartz.QuartzCommand.execute(QuartzCommand.java:43) [artifactory-core-1.3.0-beta-6.jar:na]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [quartz-1.6.2.jar:1.6.2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.6.0_0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.6.0_0]
> at java.lang.Thread.run(Thread.java:636) [na:1.6.0_0]
> Caused by: java.lang.RuntimeException: Indexing failed.
> at org.artifactory.repo.index.RepoIndexer.index(RepoIndexer.java:129) [artifactory-core-1.3.0-beta-6.jar:na]
> at org.artifactory.repo.index.RepoIndexerData.createIndex(RepoIndexerData.java:123) [artifactory-core-1.3.0-beta-6.jar:na]
> ... 20 common frames omitted
> Caused by: java.lang.NullPointerException
> at org.sonatype.nexus.index.DefaultArtifactContextProducer.getArtifactContext(DefaultArtifactContextProducer.java:84) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.processFile(DefaultScanner.java:131) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:113) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.scan.DefaultScanner.scan(DefaultScanner.java:46) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:261) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.sonatype.nexus.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:155) [nexus-indexer-1.0-beta-3.1.1.jar:na]
> at org.artifactory.repo.index.RepoIndexer.index(RepoIndexer.java:117) [artifactory-core-1.3.0-beta-6.jar:na]
> ... 21 common frames omitted
> This error is completely fatal - I cannot use artifactory as is, and unfortunately had to revert to 1.2.5.

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-1030) Non-uniques snapshots are deployed as unique

2008-11-22T00:56:12Z

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

Yoav Landman resolved RTFACT-1030.
----------------------------------

Resolution: Fixed

> Non-uniques snapshots are deployed as unique
> --------------------------------------------
>
> Key: RTFACT-1030
> URL: http://www.jfrog.org/jira/browse/RTFACT-1030
> Project: Artifactory
> Issue Type: Bug
> Components: Deployer
> Affects Versions: 1.3.0-beta-6
> Reporter: Yoav Landman
> Assignee: Yoav Landman
> Priority: Critical
> Fix For: 1.3.0
>
>
> This is causing later attempts to download the snapshots as non-unique to fail.

[JFrog JIRA] Created: (RTFACT-1030) Non-uniques snapshots are deployed as unique

2008-11-22T00:56:05Z

Non-uniques snapshots are deployed as unique
--------------------------------------------

Key: RTFACT-1030
URL: http://www.jfrog.org/jira/browse/RTFACT-1030
Project: Artifactory
Issue Type: Bug
Components: Deployer
Affects Versions: 1.3.0-beta-6
Reporter: Yoav Landman
Assignee: Yoav Landman
Priority: Critical
Fix For: 1.3.0

This is causing later attempts to download the snapshots as non-unique to fail.

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-1029) NPE from indexer when trying to index a jar with no pom

2008-11-21T23:01:05Z

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

Yoav Landman resolved RTFACT-1029.
----------------------------------

Resolution: Fixed

> NPE from indexer when trying to index a jar with no pom
> -------------------------------------------------------
>
> Key: RTFACT-1029
> URL: http://www.jfrog.org/jira/browse/RTFACT-1029
> Project: Artifactory
> Issue Type: Bug
> Components: Artifact Storage
> Affects Versions: 1.3.0-beta-6
> Reporter: Yoav Landman
> Assignee: Yoav Landman
> Fix For: 1.3.0
>
>

[JFrog JIRA] Created: (RTFACT-1029) NPE from indexer when trying to index a jar with no pom

2008-11-21T23:01:01Z

NPE from indexer when trying to index a jar with no pom
-------------------------------------------------------

Key: RTFACT-1029
URL: http://www.jfrog.org/jira/browse/RTFACT-1029
Project: Artifactory
Issue Type: Bug
Components: Artifact Storage
Affects Versions: 1.3.0-beta-6
Reporter: Yoav Landman
Assignee: Yoav Landman
Fix For: 1.3.0

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-1028) Fetching index files failed

2008-11-21T22:59:45Z

Fetching index files failed
---------------------------

Key: RTFACT-1028
URL: http://www.jfrog.org/jira/browse/RTFACT-1028
Project: Artifactory
Issue Type: Bug
Affects Versions: 1.3.0-beta-6
Environment: Jetty 5.1.14, JDK 6, Ubuntu Hardy
Reporter: Craig
Assignee: Yoav Landman
Priority: Critical

I just installed artifactory 1.3.0 beta 6 and set up a local repository called "third-party." I was able to deploy a SNAPSHOT artifact to it (using mvn deploy). The two deployed artifacts are com.molecular.logger:loggerMaster and com.molecular.logger:logger. Then I attempting to build another project which depended on this SNAPSHOT and got this error from maven:
[INFO] Error building POM (may not be this project's POM).
Project ID: com.molecular.logger:logger:jar:1.0-SNAPSHOT
Reason: Cannot find parent: com.molecular.logger:loggerMaster for project: com.molecular.logger:logger:jar:1.0-SNAPSHOT for project com.molecular.logger:logger:jar:1.0-SNAPSHOT

So I looked in the artifactory logs, and saw this:

2008-11-22 06:01:29,630 [ERROR] (o.a.r.i.IndexerManagerImpl:176) - Fetching index files failed.
java.lang.RuntimeException: Failed to index repository 'third-party'.
at org.artifactory.repo.index.RepoIndexerData.createIndex(RepoIndexerData.java:133) [artifactory-core-1.3.0-beta-6.jar:na]
at org.artifactory.repo.index.IndexerManagerImpl.findOrCreateIndex(IndexerManagerImpl.java:204) [artifactory-core-1.3.0-beta-6.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na:1.6.0_0]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [na:1.6.0_0]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [na:1.6.0_0]
at java.lang.reflect.Method.invoke(Method.java:616) [na:1.6.0_0]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) [spring-aop-2.5.5.jar:2.5.5]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) [spring-aop-2.5.5.jar:2.5.5]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) [spring-aop-2.5.5.jar:2.5.5]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) [spring-tx-2.5.5.jar:2.5.5]
at org.artifactory.jcr.lock.LockingAdvice.invoke(LockingAdvice.java:79) [artifactory-core-1.3.0-beta-6.jar:na]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) [spring-aop-2.5.5.jar:2.5.5]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) [spring-aop-2.5.5.jar:2.5.5]
at $Proxy16.findOrCreateIndex(Unknown Source) [na:na]
at org.artifactory.repo.index.IndexerManagerImpl$FindOrCreateIndexJob.onExecute(IndexerManagerImpl.java:174) [artifactory-core-1.3.0-beta-6.jar:na]
at org.artifactory.repo.index.IndexerManagerImpl$FindOrCreateIndexJob.onExecute(IndexerManagerImpl.java:166) [artifactory-core-1.3.0-beta-6.jar:na]
at org.artifactory.schedule.quartz.QuartzCommand.execute(QuartzCommand.java:43) [artifactory-core-1.3.0-beta-6.jar:na]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [quartz-1.6.2.jar:1.6.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.6.0_0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.6.0_0]
at java.lang.Thread.run(Thread.java:636) [na:1.6.0_0]
Caused by: java.lang.RuntimeException: Indexing failed.
at org.artifactory.repo.index.RepoIndexer.index(RepoIndexer.java:129) [artifactory-core-1.3.0-beta-6.jar:na]
at org.artifactory.repo.index.RepoIndexerData.createIndex(RepoIndexerData.java:123) [artifactory-core-1.3.0-beta-6.jar:na]
... 20 common frames omitted
Caused by: java.lang.NullPointerException
at org.sonatype.nexus.index.DefaultArtifactContextProducer.getArtifactContext(DefaultArtifactContextProducer.java:84) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.processFile(DefaultScanner.java:131) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:113) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.scanDirectory(DefaultScanner.java:74) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.scan.DefaultScanner.scan(DefaultScanner.java:46) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:261) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.sonatype.nexus.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:155) [nexus-indexer-1.0-beta-3.1.1.jar:na]
at org.artifactory.repo.index.RepoIndexer.index(RepoIndexer.java:117) [artifactory-core-1.3.0-beta-6.jar:na]
... 21 common frames omitted

This error is completely fatal - I cannot use artifactory as is, and unfortunately had to revert to 1.2.5.

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-1027) Retrieve e-mail addresses from LDAP

2008-11-21T08:36:20Z

Retrieve e-mail addresses from LDAP
-----------------------------------

Key: RTFACT-1027
URL: http://www.jfrog.org/jira/browse/RTFACT-1027
Project: Artifactory
Issue Type: New Feature
Components: Web UI
Affects Versions: 1.3.0-beta-6
Reporter: Tuomas Jormola
Assignee: Yoav Landman

Typically, when storing user information in LDAP, there's also an attribute for user's e-mail address. I think it would be pretty neat that you could configure search pattern for retrieving the user's email address and use this value as the e-mail address when creating the matching entry in the Archiva user database. Snippet from possible configuration:

<ldapSettings>
<ldapSetting>
<key>ldap1</key>
<enabled>true</enabled>
<ldapUrl>ldap://example.com</ldapUrl>
<search>
<searchFilter>sAMAccountName={0}</searchFilter>
<searchBase>dc=example,dc=com</searchBase>
<emailAttribute>mail</emailAttribute>
<emailFilter>sAMAccountName={0}</emailFilter>
<managerDn>cn=archivauser,dc=example,dc=com</managerDn>
<managerPassword>password</managerPassword>
</search>
</ldapSetting>
</ldapSettings>

So after the user's password has been verified, the query specified in <emailFilter/> is run against the LDAP server (with {0} replaced with the user name) and value of the attribute specified in <emailAttribute/> is used as the email address, provided that the search returned exactly one match and that the configured attribute exists in the result.

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-1026) Artifactory should work behind a frontend web server

2008-11-21T08:18:48Z

Artifactory should work behind a frontend web server
----------------------------------------------------

Key: RTFACT-1026
URL: http://www.jfrog.org/jira/browse/RTFACT-1026
Project: Artifactory
Issue Type: New Feature
Components: Web UI
Affects Versions: 1.3.0-beta-6
Reporter: Tuomas Jormola
Assignee: Yoav Landman

Hi,

At our company, we have following kind of setup:

Client <-> F5 BIG-IP LTM frontend device with public IP address for the Archiva server <-> Web server backend with private network

The Archiva service is accessed using HTTPS so that the frontend device first gets the request from clients, processes the SSL protected traffic, and passes the request to the backend server running Archiva (potentially, there could be several backends to choose from for high availability and load balancing, but for Archiva, we're just using a single server) using HTTP. The response from Archiva comes back to the frontend device, is wrapped to the existing SSL session and returned to client.

This works great unless the application is relying on the parameters of the server it's being run on, e.g. the port of the server, protocol scheme and so on. Archiva uses this information to constructs the links to repositories. If run like described above, for example the links to repositories at e.g. http://example.com/archiva/webapp/simplebrowserroot.html are currently broken.

The code that handles this seems to be webapp/src/main/java/org/artifactory/webapp/servlet/RequestUtils.java, method getServletContextUrl(). It uses the HttpServletRequest object provided by the servlet container to build the URL prefix. On our setup, when using Tomcat, the server is smart enough to return correct values for getServerName() (probably due to the Host HTTP Header of the request passed by the client, the value of this header points to the frontend host name the client tried to access, not the hostname of the backend server processing the request), but ports and protocol scheme are wrong, because there's no way Tomcat could know the initial request from the client was done using HTTPS.

My proposal is that Archiva should implement configuration option where one could specify the real URL prefix of the service and if specified, this would be used instead of the URL constructed from HttpServletRequest object. By default, this option would not be set, of course, and the current logic would take place when constructing the servlet context URL.

So e.g. in the artifactory.config.xml one might have

<frontendUrl>https://example.com/maven</frontendUrl>

which would result in repository URLs like

https://example.com/maven/example-repo/

even if the Archiva application is available as http://backend.example.com:10080/archiva/

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-1025) Front page of Artifactory is trying to access http://service.jfrog.org

2008-11-21T07:55:09Z

Front page of Artifactory is trying to access http://service.jfrog.org
----------------------------------------------------------------------

Key: RTFACT-1025
URL: http://www.jfrog.org/jira/browse/RTFACT-1025
Project: Artifactory
Issue Type: Bug
Components: Web UI
Affects Versions: 1.3.0-beta-6
Reporter: Tuomas Jormola
Assignee: Yoav Landman

Hi,

I'm evaluating Artifactory as our corporate Maven repository/proxy. It appears that the Wicket UI is trying to fetch some stuff from http://service.jfrog.org and it looks like there's no easy way to switch this behaviour off. Our policy forbids any direct outbound HTTP connections from the backend web servers (Artifactory will be able to access the resources on remote maven repositories via the internal HTTP proxy), and this policy is enforced at firewall level by blocking outbound access to port 80. I don't think this is unusual situation in corporate environments. Thus I think this kind of "phone home" functionality should be switched off by default, or at least it should be possible to disable without altering the source and recompiling the war. Looks like this functionality adds nothing relevant to the application. At the current state, when I log in, the browser will just hang forever since the server process can't render the front page as it's trying to access the remote HTTP server, but this is blocked by firewall. The quick workaround was to add entry

127.0.0.1 service.jfrog.org

to the /etc/hosts file of the server, but I'm sure you understand this is not ideal long term solution to the problem :)

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-1024) The ^ character causes the search query to fail

2008-11-20T07:25:25Z

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

Yossi Shaul resolved RTFACT-1024.
---------------------------------

Resolution: Fixed

Removing ^ characters from search expressions

> The ^ character causes the search query to fail
> -----------------------------------------------
>
> Key: RTFACT-1024
> URL: http://www.jfrog.org/jira/browse/RTFACT-1024
> Project: Artifactory
> Issue Type: Bug
> Components: Search, Web UI
> Reporter: Yossi Shaul
> Assignee: Yossi Shaul
> Priority: Minor
> Fix For: 1.3.0
>
>
> No idea why since this character doesn't require escaping according to the spec

[JFrog JIRA] Resolved: (RTFACT-656) No search results when search term contains "-"

2008-11-20T06:49:03Z

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

Yossi Shaul resolved RTFACT-656.
--------------------------------

Resolution: Fixed

Lucene indexes the artifactory name values in a certain way that causes some searches to return strange results. But usually it is good enough for the simple artifacts search.
We will continue to investigate when implementing different/advanced search.

> No search results when search term contains "-"
> -----------------------------------------------
>
> Key: RTFACT-656
> URL: http://www.jfrog.org/jira/browse/RTFACT-656
> Project: Artifactory
> Issue Type: Bug
> Components: Search
> Affects Versions: 1.3.0-beta-4
> Reporter: Yoav Landman
> Assignee: Yossi Shaul
> Priority: Minor
> Fix For: 1.3.0
>
>

[JFrog JIRA] Created: (RTFACT-1024) The ^ character causes the search query to fail

2008-11-20T06:47:09Z

The ^ character causes the search query to fail
-----------------------------------------------

Key: RTFACT-1024
URL: http://www.jfrog.org/jira/browse/RTFACT-1024
Project: Artifactory
Issue Type: Bug
Components: Search, Web UI
Reporter: Yossi Shaul
Assignee: Yossi Shaul
Priority: Minor
Fix For: 1.3.0

No idea why since this character doesn't require escaping according to the spec

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-1022) Search pages combo box is not refreshed correctly

2008-11-20T05:47:22Z

Search pages combo box is not refreshed correctly
-------------------------------------------------

Key: RTFACT-1022
URL: http://www.jfrog.org/jira/browse/RTFACT-1022
Project: Artifactory
Issue Type: Bug
Components: Web UI
Affects Versions: 1.3.0-beta-6
Reporter: Frederic Simon
Assignee: Yossi Shaul
Priority: Critical
Fix For: 1.3.0

See screen shot after searching "maven", "log" then "anno" in FF3

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-229) Navigation from search results to the artifact in the repo browser tree

2008-11-20T04:32:44Z

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

Tal Abramson resolved RTFACT-229.
---------------------------------

Fix Version/s: 1.3.0-beta-6
(was: 2.0.0)
Resolution: Fixed

> Navigation from search results to the artifact in the repo browser tree
> -----------------------------------------------------------------------
>
> Key: RTFACT-229
> URL: http://www.jfrog.org/jira/browse/RTFACT-229
> Project: Artifactory
> Issue Type: Task
> Components: Search, Web UI
> Affects Versions: 1.2.5
> Reporter: Yoav Landman
> Assignee: Yoav Landman
> Fix For: 1.3.0-beta-6
>
>

[JFrog JIRA] Resolved: (RTFACT-745) Css style for wicket warn messages

2008-11-20T00:58:10Z

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

Yoav Landman resolved RTFACT-745.
---------------------------------

Fix Version/s: 1.3.0-beta-6
(was: 1.3.0)
Resolution: Fixed

> Css style for wicket warn messages
> ----------------------------------
>
> Key: RTFACT-745
> URL: http://www.jfrog.org/jira/browse/RTFACT-745
> Project: Artifactory
> Issue Type: Cosmetic
> Components: Web UI
> Reporter: Yossi Shaul
> Assignee: Yoav Aharoni
> Fix For: 1.3.0-beta-6
>
>

[JFrog JIRA] Resolved: (RTFACT-945) Issue cleaning up space on my server where artifactory is configured and set up.

2008-11-18T04:10:10Z

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

Yoav Landman resolved RTFACT-945.
---------------------------------

Resolution: Duplicate

> Issue cleaning up space on my server where artifactory is configured and set up.
> ---------------------------------------------------------------------------------
>
> Key: RTFACT-945
> URL: http://www.jfrog.org/jira/browse/RTFACT-945
> Project: Artifactory
> Issue Type: Bug
> Components: Artifact Storage
> Affects Versions: 1.2.5
> Environment: DEV & ACP
> Reporter: Edgar Lanz
> Assignee: Yoav Landman
> Priority: Critical
> Fix For: 1.3.0-beta-6
>
>
> I have completely run out of space from my linux server and am unable to build/deploy artifacts, war files to my artifactory because of this. I logged into my artifactory web interface and manually deleted hundreds of old version war files and SNAPSHOTS which range from 50 to 60 megs. After deleting these files I noticed that my server remains the same and my storage size did not increase.
> Is there any other way to do this?
> Please let me know
> Thanks
> Edgar

[JFrog JIRA] Created: (RTFACT-996) Stopping the task service takes a lot of time and sometimes throws lock timeout

2008-11-18T01:08:59Z

Stopping the task service takes a lot of time and sometimes throws lock timeout
-------------------------------------------------------------------------------

Key: RTFACT-996
URL: http://www.jfrog.org/jira/browse/RTFACT-996
Project: Artifactory
Issue Type: Bug
Reporter: Yossi Shaul
Assignee: Yoav Landman
Priority: Blocker
Fix For: 1.3.0-beta-6

Got this once when i updated the configuration and once when i closed artifactory

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-980) Tail multiple log files

2008-11-17T05:01:59Z

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

Noam Y. Tenne resolved RTFACT-980.
----------------------------------

Resolution: Fixed

> Tail multiple log files
> -----------------------
>
> Key: RTFACT-980
> URL: http://www.jfrog.org/jira/browse/RTFACT-980
> Project: Artifactory
> Issue Type: Improvement
> Components: Logging, Web UI
> Affects Versions: 1.3.0-beta-6
> Reporter: Noam Y. Tenne
> Assignee: Noam Y. Tenne
> Fix For: 1.3.0-beta-6
>
>
> add the ability to switch tailing on access.log and nice error message if the file is not there

[JFrog JIRA] Created: (RTFACT-991) Backup create/update panel fields layout is messy

2008-11-17T04:48:59Z

Backup create/update panel fields layout is messy
-------------------------------------------------

Key: RTFACT-991
URL: http://www.jfrog.org/jira/browse/RTFACT-991
Project: Artifactory
Issue Type: Cosmetic
Components: Web UI
Reporter: Yossi Shaul
Assignee: Yoav Aharoni
Fix For: 1.3.0-beta-6

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-987) Allow overriding artifact details for generated/extracted POMs

2008-11-17T02:28:03Z

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

Yoav Landman resolved RTFACT-987.
---------------------------------

Resolution: Fixed

Done

> Allow overriding artifact details for generated/extracted POMs
> --------------------------------------------------------------
>
> Key: RTFACT-987
> URL: http://www.jfrog.org/jira/browse/RTFACT-987
> Project: Artifactory
> Issue Type: Improvement
> Components: Deployer
> Affects Versions: 1.3.0-beta-6
> Reporter: Yoav Landman
> Assignee: Yoav Landman
> Fix For: 1.3.0-beta-6
>
>

[JFrog JIRA] Created: (RTFACT-987) Allow overriding artifact details for generated/extracted POMs

2008-11-17T02:27:59Z

Allow overriding artifact details for generated/extracted POMs
--------------------------------------------------------------

Key: RTFACT-987
URL: http://www.jfrog.org/jira/browse/RTFACT-987
Project: Artifactory
Issue Type: Improvement
Components: Deployer
Affects Versions: 1.3.0-beta-6
Reporter: Yoav Landman
Assignee: Yoav Landman
Fix For: 1.3.0-beta-6

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Resolved: (RTFACT-968) Show IP Address in access log for anonymous

2008-11-16T08:21:59Z

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

Yossi Shaul resolved RTFACT-968.
--------------------------------

Resolution: Fixed

The IP address now also saved for non-ui requests

> Show IP Address in access log for anonymous
> -------------------------------------------
>
> Key: RTFACT-968
> URL: http://www.jfrog.org/jira/browse/RTFACT-968
> Project: Artifactory
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 1.3.0-beta-4
> Environment: linux, Java 1.6
> Reporter: Karl Toffel
> Assignee: Yossi Shaul
> Fix For: 1.3.0-rc1
>
>
> Hello,
> while browsing the access log, I mentioned missing IP addresses on "ACCEPTED DOWNLOAD" entries with anonymous access. The ip address is clearly available to artifactory, since it is logged for example by a debug statement of DownloadEngine in the ordinary log. Is it possible to add it to the access log?
> Thanks!

[JFrog JIRA] Resolved: (RTFACT-976) replace setResponsePage with ajax refresh

2008-11-16T05:38:59Z

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

Yossi Shaul resolved RTFACT-976.
--------------------------------

Resolution: Fixed

Replaced setResponsePage with Ajax request in the admin config pages

> replace setResponsePage with ajax refresh
> -----------------------------------------
>
> Key: RTFACT-976
> URL: http://www.jfrog.org/jira/browse/RTFACT-976
> Project: Artifactory
> Issue Type: Bug
> Components: Web UI
> Affects Versions: 1.3.0-rc1
> Reporter: Yoav Aharoni
> Assignee: Yossi Shaul
> Fix For: 1.3.0-rc1
>
>
> usages I found:
> - BackupCreateUpdatePanel
> - BackupsListPanel
> - GeneralSettingsPanel
> - PermissionTargetPanel
> - ProfilePanel
> - ServicesConfigPanel

[JFrog JIRA] Resolved: (RTFACT-908) Command line deployment intermitent

2008-11-16T03:54:03Z

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

Yoav Landman resolved RTFACT-908.
---------------------------------

Resolution: Fixed

Fixed

> Command line deployment intermitent
> -----------------------------------
>
> Key: RTFACT-908
> URL: http://www.jfrog.org/jira/browse/RTFACT-908
> Project: Artifactory
> Issue Type: Bug
> Components: Deployer
> Affects Versions: 1.3.0-rc1
> Environment: See description
> Reporter: William Lang
> Assignee: Yoav Landman
> Priority: Critical
> Fix For: 1.3.0-rc1
>
>
> Environment:
> artifactory-1.3.0-beta-4
> apache-maven-2.0.9
> Windows Maven located on a Samba share
> RedHat Linux install of Artifactory on the same host
> 4 repositories defined: snapshot, legacy, third party and releases
> Two Artifactory ID's defined, admin and developer
> developer password hard coded in Maven settings.xml
> admin password set as an environment variable in the admin users environments
> developers are allowed to deploy to snapshot repo only, read access to all others
> Admins can deploy from the GUI without issue, but are seeing intermittent "access denied" issues from the command line

[JFrog JIRA] Created: (RTFACT-976) replace setResponsePage with ajax refresh

2008-11-16T03:51:59Z

replace setResponsePage with ajax refresh
-----------------------------------------

Key: RTFACT-976
URL: http://www.jfrog.org/jira/browse/RTFACT-976
Project: Artifactory
Issue Type: Bug
Components: Web UI
Affects Versions: 1.3.0-rc1
Reporter: Yoav Aharoni
Assignee: Yossi Shaul
Fix For: 1.3.0-rc1

usages I found:
- BackupCreateUpdatePanel
- BackupsListPanel
- GeneralSettingsPanel
- PermissionTargetPanel
- ProfilePanel
- ServicesConfigPanel

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-973) UI does not work in Google Chrome

2008-11-15T08:49:59Z

UI does not work in Google Chrome
---------------------------------

Key: RTFACT-973
URL: http://www.jfrog.org/jira/browse/RTFACT-973
Project: Artifactory
Issue Type: Bug
Affects Versions: 1.3.0-beta-3
Reporter: Florian Huonder
Assignee: Yoav Landman

The UI does not work with Google's Chrome Browser.
There is no reaction on any click.

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers

[JFrog JIRA] Created: (RTFACT-959) NTLM Proxy credentials are ignored

2008-11-13T07:52:59Z

NTLM Proxy credentials are ignored
----------------------------------

Key: RTFACT-959
URL: http://www.jfrog.org/jira/browse/RTFACT-959
Project: Artifactory
Issue Type: Bug
Affects Versions: 1.3.0-beta-5
Reporter: Yoav Landman
Assignee: Noam Y. Tenne
Fix For: 1.3.0-rc1

--
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Artifactory-developers mailing list
Artifactory-developers@...
https://lists.sourceforge.net/lists/listinfo/artifactory-developers