Just did a build with clean repo. I got a few dependency failures in
the build-tools project. itext & confluence-soap. So I removed the
PDFBuilder that required itext - we are not using it anyways, and
uploaded confluence-soap to ObjectStyle maven repo.
Also how do you build an assembly. I am getting an error when doing
it from the root:
# mvn assembly:assembly
[... after doing the full build for a few minutes ... ]
[INFO] [assembly:assembly]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] No assembly descriptors found.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 minutes 50 seconds
[INFO] Finished at: Fri Aug 25 12:11:09 MSD 2006
[INFO] Final Memory: 17M/31M
[INFO]
------------------------------------------------------------------------
Andrus
On Aug 25, 2006, at 2:41 AM, Bill Dudney wrote:
Hi All,
I've just committed the maven2 plugin that invokes the confluence
export.
I think we should change the way we do this stuff to invoke the
'exportSpace' instead. Unfortunately I am not a confluence admin so
I could not test it myself. If someone that has admin could add me
as an admin I'd be glad to update the build-tools and test the
exportSpace.
After I get this working I'll be adding a profile to the build for
doing a release that will remove the javadoc from the default build.
What does everyone think of generating a source jar with the build?
I like having the source in the m2 repo so that my eclipse
debugging goes into the code instead of the 'class editor' but it
does take longer to build so I could remove that from the default
build as well. Thoughts?
Thanks!
-bd-
