[mazzag]

Well what am I missing?  In addition to federation/trunk and trust/trunk, what other JBoss projects do I need to download and build so I can do an mvn clean install of the PicketLink source code?  I presently can't import the code into Eclipse via mvn eclipse:eclipse because that command doesn't work if the mvn install doesn't complete.  (What other JBoss projects do you have on your machine so you can build Picketlink?)

So others don't have to ask this question and potentially lose multiple days in getting a response, please update your original posting in this thread, under Advanced Users, and let us know what additional JBoss projects we need to download so we can in fact do an mvn clean install eclipse:eclipse of Picketlink code.  Unless you let us know what the dependent projects are so we can do a build, the Advanced Users section really isn't all that helpful.  Thanks!

[anil.saldhana]

That advanced section is correct. If you are unable to build the workspace, then there is some issue in your maven settings (settings.xml)

http://community.jboss.org/wiki/MavenRepository

By the way, you asked the question on the 21st and I answered on the 22nd even though I was travelling.  Where did I answer late such that you lost multiple days?

And why exactly are you trying to build the workspaces?

[jaikiran]

Glen Mazza wrote:

Could not transfer artifact apache-log4j:log4j:pom:1.2.14 from/to repository.jboss.org (http://repository.jboss.org/maven2/): Access denied to: http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.14/log4j-1.2.14.pom -> [Help 1]

[ERROR]

This actually is a result of a combination of multiple issues related to JBoss Maven repos. It looks like the PicketLink project has a dependency on a deprecated  groupid/artifactid combination of log4j (i.e. apache-log4j:log4j). This is available in the JBoss Deprecated Repository http://community.jboss.org/wiki/JBossDeprecatedRepository and was (apparently) available in repository.jboss.org/maven2. The repository.jboss.org/maven2 no longer exists (It got disabled a few weeks back http://community.jboss.org/en/build/blog/2011/06/01/blocking-repositoryjbossorgmaven2).

The PicketLink build pom uses this repository.jboss.org/maven2 which no longer exists and the public repo of JBoss (which doesn't have this deprecated artifact). As a result, it runs into this issue of missing artifact (which can only be seen on a clean system which already doesn't have these maven artifacts downloaded).

The real solution would be to fix the pom to move away from the deprecated apache-log4j:log4j to log4j:log4j as mentioned here http://community.jboss.org/wiki/JBossDeprecatedRepository (the table showing deprecated and "correct" artifact ids). In the meantime, you can get around this issue by including the JBoss Deprecated Repository in your settings.xml as explained here http://community.jboss.org/wiki/MavenGettingStarted-Users (check Using Deprecated Dependencies section)

[jaikiran]

https://issues.jboss.org/browse/PLINK-47

[anil.saldhana]

Thanks JP.  I have applied the patch.  Ideally the groupid should be org.apache.log4j

[mazzag]

Thanks very much Anil and Jaikiran -- incidentally, should I be using Maven 3 or Maven 2.2.1 for the builds?

[mazzag]

I can answer my own question, it will build with Maven 3.0.3, *but* two more dependency updates are needed: https://issues.jboss.org/browse/PLINK-48.

Now both build OOTB with a simple "mvn clean install", no settings.xml or other modifications needed.  Awesome!

[kpeeples]

Why is the SAMLPrincipal in PL 1 but not in PL 2?

[dsutherland1492]

I would also like to know the answer to this question.