[Building Sakai] Nightly build fails on site-manage (8 pm)
Anthony Whyte
arwhyte at umich.edu
Wed Sep 30 20:16:42 PDT 2009
The nightly build failed on the same build error as earlier in the day
(see far below) despite a quick patch specifying the site-manage-api
dependency in the base pom <dependencyManagement> section (in theory
not required since the api version dependency is specified and
inherited from the master pom but I decided to follow the pattern
adopted in entitybroker and search and explicitly reference it). The
build still failed when trying to build sakai-site-manage-hbm. I also
fixed the bad <relativePath> in the site-manage-link-helper pom. My
fixes were in well before 8 pm Eastern. No idea what is going on
here. site-manage installs cleanly for me against my local .m2 repo
sans site-manage artifacts. Could be a Maven version issue (I run
2.1.0), although I believe David checked that earlier.
I ran mvn dependency:analyze against the site-manage. Maven found a
number of unused dependencies. Many of these are inherited from the
master pom (e.g., junit). But focusing on dependencies declared in
site-manage poms, I find a number of declarations that look like they
could be deleted. For example, there are declared dependencies on the
course-management-api in the api and impl poms which do not appear to
be required: indeed the impl pom <dependency> section lists the cmi
api as a dependency twice (so one declaration can certainly go). Only
the tool and util projects actually depend on the course-management
api if you look at the Java code and their poms include a declared
dependency on the cm-api. site-manage-util is declared as a
dependency in the impl pom but doesn't look like it's ever used. The
same is true for the courier-api dependency in the site-manage-tool pom.
That said, Maven's analysis of unused declared dependencies should be
approached with some caution. Runtime or test dependencies won't be
found by Maven in the bytecode so it's not enough to comment out or
delete an unused declared dependency, do a mvn clean install and
declare victory when the project builds successfully. You need to
check what happens at runtime. But it looks to me like the site-
manage poms should be reviewed a bit more closely for possible cruft
that can be removed.
You can also run mvn dependency:tree to take a look at site-manage
direct and transitive dependencies. On the surface nothing looks out
of place; site-manage-hbm dependencies look normal.
[INFO] Building sakai-site-manage-hbm
[INFO] task-segment: [dependency:tree]
[INFO]
------------------------------------------------------------------------
[INFO] [dependency:tree]
[INFO] org.sakaiproject:sakai-site-manage-hbm:jar:2.7.0-SNAPSHOT
[INFO] +- org.sakaiproject:sakai-site-manage-api:jar:2.7.0-
SNAPSHOT:compile
[INFO] \- junit:junit:jar:3.8.1:test
Time to go to bed,
Anth
_________________________________________
mvn dependency:analyze
api
[WARNING] Unused declared dependencies found:
[WARNING] junit:junit:jar:3.8.1:test
[WARNING] org.sakaiproject:sakai-coursemanagement-api:jar:2.7.0-
SNAPSHOT:provided
impl
[[WARNING] Unused declared dependencies found:
[WARNING] junit:junit:jar:3.8.1:test
[WARNING] org.sakaiproject:sakai-coursemanagement-api:jar:2.7.0-
SNAPSHOT:provided
[WARNING] xerces:xercesImpl:jar:2.6.2:provided
[WARNING] org.sakaiproject:sakai-site-manage-util:jar:2.7.0-
SNAPSHOT:compile
[WARNING] org.hibernate:hibernate:jar:3.2.7.ga:provided
tool
[WARNING] Used undeclared dependencies found:
[WARNING] xml-apis:xml-apis:jar:1.0.b2:provided
[WARNING] Unused declared dependencies found:
[WARNING] org.sakaiproject:sakai-message-api:jar:2.7.0-
SNAPSHOT:provided
[WARNING] batik:batik:jar:1.5-fop-0.20-5:compile
[WARNING] org.springframework:spring-test:jar:2.5.6.SEC01:test
[WARNING] org.sakaiproject:sakai-courier-api:jar:2.7.0-
SNAPSHOT:provided
[WARNING] logkit:logkit:jar:1.2:compile
[WARNING] commons-beanutils:commons-beanutils:jar:1.7.0:compile
[WARNING] org.springframework:spring:jar:2.5.6.SEC01:test
[WARNING] org.jmock:jmock-legacy:jar:2.5.1:test
[WARNING] oro:oro:jar:2.0.8:compile
[WARNING] org.jmock:jmock-junit3:jar:2.5.1:test
[WARNING] org.sakaiproject:sakai-mock:jar:2.7.0-SNAPSHOT:test
[WARNING] velocity:velocity:jar:1.3.1:compile
site-pageorder-helper
[WARNING] Used undeclared dependencies found:
[WARNING] uk.org.ponder:ponderutilcore:jar:1.2.4:compile
[WARNING] uk.org.ponder.rsfutil:rsfutil:jar:0.7.4:compile
[WARNING] Unused declared dependencies found:
[WARNING] uk.org.ponder.sakairsf:SakaiRSFComponents-evolvers:jar:
0.7.4-sakai_2.2.x:compile
[WARNING] commons-lang:commons-lang:jar:2.1:provided
site-manage-group-helper
[WARNING] Used undeclared dependencies found:
[WARNING] uk.org.ponder:ponderutilcore:jar:1.2.4:compile
[WARNING] uk.org.ponder.rsfutil:rsfutil:jar:0.7.4:compile
[WARNING] Unused declared dependencies found:
[WARNING] commons-lang:commons-lang:jar:2.4:provided
[WARNING] uk.org.ponder.sakairsf:SakaiRSFComponents-evolvers:jar:
0.7.4-sakai_2.2.x:compile
[WARNING] uk.org.ponder.sakairsf:SakaiRSFComponents-templates:war:
0.7.4-sakai_2.2.x:compile
site-manage-group-section-role-helper
[WARNING] Used undeclared dependencies found:
[WARNING] uk.org.ponder:ponderutilcore:jar:1.2.4:compile
[WARNING] uk.org.ponder.rsfutil:rsfutil:jar:0.7.4:compile
[WARNING] Unused declared dependencies found:
[WARNING] commons-lang:commons-lang:jar:2.4:provided
[WARNING] uk.org.ponder.sakairsf:SakaiRSFComponents-evolvers:jar:
0.7.4-sakai_2.2.x:compile
[WARNING] uk.org.ponder.sakairsf:SakaiRSFComponents-templates:war:
0.7.4-sakai_2.2.x:compile
site-manage-group-section-role-helper-pack
[WARNING] Unused declared dependencies found:
[WARNING] org.sakaiproject.kernel:sakai-component-manager:jar:1.1.0-
beta02-SNAPSHOT:provided
[WARNING] commons-lang:commons-lang:jar:2.4:provided
[WARNING] org.sakaiproject.kernel:sakai-kernel-util:jar:1.1.0-
beta02-SNAPSHOT:compile
[WARNING] org.sakaiproject:sakai-site-manage-util:jar:2.7.0-
SNAPSHOT:compile
site-manage-participant-helper
[WARNING] Used undeclared dependencies found:
[WARNING] uk.org.ponder:ponderutilcore:jar:1.2.4:compile
[WARNING] uk.org.ponder.rsfutil:rsfutil:jar:0.7.4:compile
[WARNING] Unused declared dependencies found:
[WARNING] oro:oro:jar:2.0.8:compile
[WARNING] org.sakaiproject:sakai-velocity-tool-api:jar:2.7.0-
SNAPSHOT:provided
[WARNING] uk.org.ponder.sakairsf:SakaiRSFComponents-evolvers:jar:
0.7.4-sakai_2.2.x:compile
[WARNING] commons-lang:commons-lang:jar:2.1:provided
site-manage-link-helper
[WARNING] Unused declared dependencies found:
[WARNING] org.sakaiproject.kernel:sakai-component-manager:jar:1.1.0-
beta02-SNAPSHOT:provided
[WARNING] oro:oro:jar:2.0.8:compile
[WARNING] org.sakaiproject:sakai-velocity-tool-api:jar:2.7.0-
SNAPSHOT:provided
[WARNING] logkit:logkit:jar:1.2:compile
[WARNING] velocity:velocity:jar:1.3.1:compile
[INFO] Building sakai-site-manage-hbm
[INFO]
----------------------------------------------------------------------------
[INFO] [resources:resources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 4 resources
[INFO] snapshot org.sakaiproject:sakai-site-manage-api:2.7.0-SNAPSHOT:
checking for updates from sakai-maven2-snapshots
Downloading: http://source.sakaiproject.org/maven2-snapshots/org/sakaiproject/sakai-site-manage-api/2.7.0-SNAPSHOT/sakai-site-manage-api-2.7.0-SNAPSHOT.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.sakaiproject:sakai-site-manage-api:jar:2.7.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.sakaiproject -
DartifactId=sakai-site-manage-api \
-Dversion=2.7.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file -DgroupId=org.sakaiproject -
DartifactId=sakai-site-manage-api \
-Dversion=2.7.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/
file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.sakaiproject:sakai-site-manage-hbm:jar:2.7.0-SNAPSHOT
2) org.sakaiproject:sakai-site-manage-api:jar:2.7.0-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
org.sakaiproject:sakai-site-manage-hbm:jar:2.7.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
sakai-maven2-snapshots (http://source.sakaiproject.org/maven2-snapshots
),
apache-repo (http://myfaces.zones.apache.org/dist/maven-repository),
sakai-ibiblio-mirror (http://source.sakaiproject.org/maven2-ibiblio),
default (http://repo1.maven.org/maven2),
sakai-maven (http://source.sakaiproject.org/maven2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2417 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090930/d48536ea/attachment.bin
More information about the sakai-dev
mailing list