strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
office-gobmx/bin
History
David Ostrovsky 78e4b97a18 Set up tool chain to install LO artifacts in Maven repositories 
Add <path_to_libo>/bin to your path.
After full LO compile, the LO Java artifacts can be installed in the local
Maven repository:

mvn.py -a install -v 4.2.0 -s juh🫙<path_to>/juh.jar
mvn.py -a install -v 4.2.0 -s jurt🫙<path_to>/jurt.jar
mvn.py -a install -v 4.2.0 -s ridl🫙<path_to>/ridl.jar
mvn.py -a install -v 4.2.0 -s unoil🫙<path_to>/unoil.jar

With the artifacts installed this way, it is now possible
to consume LO artifacts from custom pom.xml:

[...]
  <properties>
    <LibreOffice-Version>4.2.0</LibreOffice-Version>
  </properties>
[...]
  <dependencies>
    <dependency>
      <groupId>org.libreoffice</groupId>
      <artifactId>juh</artifactId>
      <version>${LibreOffice-Version}</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>org.libreoffice</groupId>
      <artifactId>jurt</artifactId>
      <version>${LibreOffice-Version}</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>org.libreoffice</groupId>
      <artifactId>ridl</artifactId>
      <version>${LibreOffice-Version}</version>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>org.libreoffice</groupId>
      <artifactId>unoil</artifactId>
      <version>${LibreOffice-Version}</version>
      <scope>provided</scope>
    </dependency>
  </dependencies>

Change-Id: I2ad982ae23c78242ed8f1ac4c88c6be424cc7a0d
Reviewed-on: https://gerrit.libreoffice.org/6453
Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>
2013-11-02 05:06:13 -05:00
..
text_cat
bash-completion.in
benchmark-document-loading
convwatch.py
count-todo-dialogs
distro-install-clean-up
distro-install-desktop-integration
distro-install-file-lists
distro-install-sdk
fake_pom.xml Set up tool chain to install LO artifacts in Maven repositories 2013-11-02 05:06:13 -05:00
find-german-comments
find-undocumented-classes
find-unusedheaders.pl
fixincludeguards.sh be verbose about which guard definition is problematic 2013-10-23 23:22:32 +02:00
fuzzfiles
generate-bash-completion
get-bugzilla-attachments-by-mimetype
get_config_variables
git-new-module-workdir
git-new-workdir
git-ps1
java-set-classpath.in
lint-ui.py
lo-commit-stat
lo-generate-source-tarball typo: s/helcontent2/helpcontent2/ 2013-10-22 11:03:53 +02:00
lo-pack-sources
lo-xlate-lang
module-deps.pl
moveglobalheaders.sh
mvn.py Set up tool chain to install LO artifacts in Maven repositories 2013-11-02 05:06:13 -05:00
README
striplanguagetags.sh
stubify.pl
unpack-sources
update_pch.sh
verify-custom-widgets-libs verify-custom-widgets-libs: check libraries in instdir 2013-10-31 14:52:59 +01:00

README 

Tools and scripts mostly not used during the build

This direction has a number of key pieces (?) that are used during the
build, or are simply generally useful. One example is

bin/find-german-comments <directory>

which will try to detect and extract all the German comments in a
given source code hireachy / directory.