[opencms-dev] How to build ant-opencms-1.2.jar

Alberto Gallardo argrico at gmail.com
Tue Feb 12 18:02:14 CET 2013


Hi Tobias,

thanks for your prompt response. I don't use Eclipse, and I'd like to stay
as IDE agnostic as possible. I'd should also mention that my goal is to
have a CI environment building all OpenCms artifacts from the official
Alkacon repositories (with as few changes as possible).

Before addressing the manifest.xml issue, I'd like to first tackle the
generation of the artifacts under src-components. (To separate the source
part of the manifest from generated part, I don't see any clean workaround
but modifying that ensuredirmanifest task, and I don't want to do that
without proper scritps...)

>From my point of view, there is no need for keeping the
"ant-opencms-1.2.jar, gwt-opencms-1.0.jar, and langdetect-opencms-1.0.jar"
artifacts versioned: from the lack of scripts for building them, I assume
they are unimportant outside the opencms-core repository. Moreover, if they
were relevant outside this rep, I'd expect some git tags like
"ant_opencms_1_2" or similar. Thus,

   - I'd suggest to remove the versioning part of these artifacts and write
   a build.xml inside src-components that takes care of their building process.
   - This opencms-core/src-components/build.xml could be called from the
   parent opencms-core/build.xml, before (or during) the "init" target, so
   init can "taskdef" them.

I don't know exactly how big this enterprise will be, but I have began with
the build script for the ant-opencms.jar. If nothing gets in the way and I
get it working, I'll send a pull-request.

If this doesn't make sense, please let me know.


Best regards,

Alberto



> we build the ant-opencms jar and the other component libraries using
> jardesc files in the src-components folder.
>
> Regarding the manifest.xml files of the modules using GWT. It's true,
> these files are source and build artefacts at the same time. But this is
> not easily resolved, as we need the module configuration within that file
> and also the references to the generated resources at the same time.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20130212/d85389e4/attachment.htm>


More information about the opencms-dev mailing list