[JBoss JIRA] (FORGE-1321) Failure to install addons when using Artifactory repositories using centrally secured passwords
by David Beer (JIRA)
[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ]
David Beer commented on FORGE-1321:
-----------------------------------
Artifactory can be configured as follows:
Install default setup and configuration add the jboss repositories to the remote repositories section and add them to the remote-repos virtual repository. Create a second user other than admin, set the users password. Change the General Settings to disallow anomous access. Log in as the new user and generate the maven file to point to repo (contains all repositories). Download the maven settings file and put in your m2 directory. Add your password in for the user in clear text resolution in forge2 fails.
Go back to artifactory login in as admin and change the security settings, make sure the Password Encryption Policy is set to Supported. Then login as the user and follow the instruction in the above article to get your encrypted key. Copy the key as it says to your maven settings file and try and resolve dependencies in forge2.
> Failure to install addons when using Artifactory repositories using centrally secured passwords
> -----------------------------------------------------------------------------------------------
>
> Key: FORGE-1321
> URL: https://issues.jboss.org/browse/FORGE-1321
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 2.0.0.Beta3
> Reporter: Vineet Reynolds
>
> After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon:
> {noformat}
> forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell
> Using Forge at forge-distribution-2.0.0.Beta2
> Warning: JAVA_HOME environment variable is not set.
> Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata...
> Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata...
> java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell
> at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199)
> at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
> at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88)
> > Forge version [2.0.0.Beta1]
> {noformat}
> The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords
> Additional info:
> {noformat}
> <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (FORGE-1322) Checks for versioned facet installation are insufficient
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1322:
--------------------------------------
Summary: Checks for versioned facet installation are insufficient
Key: FORGE-1322
URL: https://issues.jboss.org/browse/FORGE-1322
Project: Forge
Issue Type: Bug
Components: Java EE APIs
Affects Versions: 2.0.0.Beta3
Reporter: Vineet Reynolds
The current checks in the {{isInstalled}} method of most versioned Facets include the following line:
{noformat}
return super.isInstalled() && getConfigFile().exists();
{noformat}
This is insufficient since the config file could exist but could contain a different version. The facet should not be activated in such a case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (FORGE-1136) Forge fails to resolve dependencies across multiple password protected Maven repositories located on the same host
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1136?page=com.atlassian.jira.plugin... ]
Vineet Reynolds commented on FORGE-1136:
----------------------------------------
Just glanced through the furnace dependency tree and this looks like it is still an issue.
Furnace dep tree:
{noformat}
[INFO] +- org.apache.maven.wagon:wagon-http-lightweight:jar:2.4:compile
[INFO] | \- org.apache.maven.wagon:wagon-http-shared4:jar:2.4:compile
[INFO] | +- org.jsoup:jsoup:jar:1.7.1:compile
[INFO] | +- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
[INFO] | \- commons-io:commons-io:jar:2.0.1:compile
{noformat}
Forge 1.x project-model-maven dep tree:
{noformat}
[INFO] +- org.apache.maven.wagon:wagon-http-lightweight:jar:2.0:compile
[INFO] | \- org.apache.maven.wagon:wagon-http-shared4:jar:2.0:compile
[INFO] | +- org.jsoup:jsoup:jar:1.6.1:compile
[INFO] | +- org.apache.httpcomponents:httpcore:jar:4.0.1:compile (version managed from 4.1.2)
[INFO] | \- commons-io:commons-io:jar:2.0.1:compile
{noformat}
Wagon-http-lightweight continues to be used.
I'll run a more detailed test later.
> Forge fails to resolve dependencies across multiple password protected Maven repositories located on the same host
> ------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-1136
> URL: https://issues.jboss.org/browse/FORGE-1136
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.0.Final
> Reporter: Vineet Reynolds
>
> This is related to FORGE-1134.
> When attempting to resolve dependencies from multiple repositories present on the same host, Forge (actually Maven and Aether) fails to resolve certain dependencies.
> The following is an example:
> {noformat}
> [no project] vineet $ forge install-plugin arquillian
> Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
> ***INFO*** Preparing to install plugin: arquillian
> ***INFO*** Checking out plugin source files to [/tmp/forgetemp448150160827402029] via 'git'
> ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N]
> ***INFO*** Cleaning up temp workspace [/tmp/forgetemp448150160827402029]
> Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
> Deleted /tmp/forgetemp448150160827402029
> ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces)
> [no project] vineet $
> {noformat}
> In this case, some of the dependencies (present in M2 central) were resolved successfully, while others (present in the public repo group) were not. The underlying cause was that the resolved dependencies were present in a repository or repository group via a valid username+password combination. The unresolved dependencies were also present in a repository or repository group protected by a username+password combination. Although valid credentials were provided by Forge to Maven/Aether for the second repository, this was not used by Maven/Aether.
> The underlying reason is that the JVM caches the credentials used by the Maven LightweightHTTPWagon implementation since the credentials are supplied via a {{java.net.Authenticator}} instance. This forces only one set of credentials to be used at runtime; the second set of credentials will be ignored.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months