Hey Andrus,
Sorry for not documenting this, I need to get to the wiki!
I'll drop the PDFBuilder code and itext as a dependency, the other
dependency was activation.jar but that now comes from the java.net
legacy maven repo so hopefully you got that OK.
The assembly currently requires you to be in the assembly directory.
I have it configured to create the assemblies on an install so from
the assemblies directory you can type 'mvn install' and get a .tar.gz
and .zip for all the platforms.
I'm just testing adding the assemblies to the modules in the root
pom. If it works I'll check that in so every install build from the
root will create an assembly. Then I'll add that to the profile so
that its also run at the same time the javadoc and source gen are run.
After running install from the assemblies you will have the .tar.gz
and .zip files in your local repo as well;
$ ls ~/.m2/repository/org/apache/cayenne/assembly/
cayenne-assembly-generic cayenne-assembly-parent
cayenne-assembly-osx cayenne-assembly-win
TTFN,
-bd-
On Aug 25, 2006, at 2:14 AM, Andrus Adamchik wrote:
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-
