hi
an other fix for
nailgun: https://bugzilla.redhat.com/show_bug.cgi?id=1307790https://bugzilla.redhat.com/show_bug.cgi?id=1239704
regards
.g
p.s. suggestion, split the package:
%package all
Summary: Nailgun Parent POM
BuildArch: noarch
%description all
This package provides Nailgun Parent POM.
%package examples
Summary: Examples for %{name}
BuildArch: noarch
%description examples
This package contains examples for %{name}.
%build
# Split the package in its own sub-projects
%mvn_build -s
%install
%mvn_install
%files -f .mfiles-%{name}-server
%doc README.md
%files all -f .mfiles-%{name}-all
%files examples -f .mfiles-%{name}-examples
%files javadoc -f .mfiles-javadoc
----- Original Message -----
>
>
> Il 18/02/2016 02:36, Ding Yi Chen ha scritto:
> > Background information:
> > Upstream of package saxon (http://saxon.sourceforge.net/) has changed the
> > Open source branch to Saxon-HE, as well as the maven artifact since version
> > 9.4.
> >
> > I would like to update the Saxon version, that will also change the maven
> > artifactId from
> > saxon to Saxon-HE.
> >
> > As far as I can see, if I just update the saxon version to >= 9.4,
> > the packages that requires mvn(net.sf.saxon:saxon) will break:
> > pmd
> > shrinkwrap-descriptors
> >
> > Packages that requires saxon might also affected:
> > olfs
> > scilab
> > writer2latex
> >
> > Should I create a new package Saxon-HE, or just update the saxon?
> Hi
> is not enought append net.sf.saxon:saxon to mvn_alias macros
> or is (also) a problem with break compatibility with newer apis ?
> in this last case you should create a compact package (see log4j12,
> lucene3/4, solr3 as e.g. )
> regards
> .g
> p.s. please, for this purpose send the email @ Fedora Java Development
> List java-devel(a)lists.fedoraproject.org
According to http://www.saxonica.com/documentation/#!changes/api/9.3-9.4
It does not seem to have breaking change.
So I will probably use mvn_alias.
Thanks!
--
Ding-Yi Chen
Software Engineer
Globalization Group
DID: +61 7 3514 8239
Email: dchen(a)redhat.com
Red Hat, Asia-Pacific Pty Ltd
Level 1, 193 North Quay
Brisbane 4000
Office: +61 7 3514 8100
Fax: +61 7 3514 8199
Website: www.redhat.com
Red Hat, Inc.
Facebook: Red Hat APAC | Red Hat Japan | Red Hat Korea | JBoss APAC
Twitter: Red Hat APAC | Red Hat ANZ
LinkedIn: Red Hat APAC | JBoss APAC
Hi folks,
It's been a while. I am giving a shot to update our tuxguitar package
from 1.2 to the recent 1.3. The new release comes with a build system
switch from ant to maven. I do not have much experience with maven, so
I tried to follow the packaging instructions [1] which I found quite
useful. I managed to build the package from source, but I still have 4
problems:
1- tuxguitar-1.3 has an itext5 dependency, but we only ship itext2 in
Fedora. I tried to disable the tuxguitar-pdf plugin (which uses itext)
by various combinations of %pom_remove_dep, %pom_remove_plugin,
%pom_disable_module. The following takes me a couple steps further
%pom_remove_dep -r com.itextpdf:itextpdf
%pom_remove_dep -r com.itextpdf.tool:xmlworker
but I end up getting:
[ERROR] Failed to execute goal on project tuxguitar-pdf: Could not
resolve dependencies for project
org.herac.tuxguitar:tuxguitar-pdf:jar:1.3.0: The following artifacts
could not be resolved: com.itextpdf:itextpdf:jar:SYSTEM,
com.itextpdf.tool:xmlworker:jar:SYSTEM: Cannot access swt-repo
(https://swt-repo.googlecode.com/svn/repo/) in offline mode and the
artifact com.itextpdf:itextpdf:jar:SYSTEM has not been downloaded from
it before. -> [Help 1]
So, I worked around by patching the pom.xml file and removed the
dependency by hand. I am pretty sure there is a better way of doing
this with the maven macros.
2- When the package is built with %mvn_build and installed with
%mvn_install the jar files get installed into
/usr/share/java/tuxguitar/. But looking at the launcher script, the
application expects the jar files to be in /usr/share/tuxguitar/. Is
there a way to tell maven to install the jar files there instead
(these are application jars, not shared libraries) ?
3- I manually moved the jar files into /usr/share/tuxguitar/. The
launcher calls the entry point in tuxguitar.jar. But this jar doesn't
find the other jars, for example the tuxguitar-editor-utils.jar, and
the application doesn't launch. I can add this jar file and the other
15 jar files to the CLASSPATH in the lancher script, but I am not sure
this is the right way. I didn't have to do this with ant. With ant,
the tuxguitar.jar somehow knew about the other jars. How can we fix
this?
4- There are a bunch of supplementary files (.desktop file, icons,
mime xmls, the launcher script etc) which are listed in the main
pom.xml file, but %mvn_install doesn't install them. I had to copy
them manually to the $RPM_BUILD_ROOT. Is there a way to do this with
better?
My current work is at
https://oget.fedorapeople.org/tuxguitar/tuxguitar.spechttps://oget.fedorapeople.org/tuxguitar/tuxguitar-1.3.0-0.fc23.src.rpm
Note that I had to remove some SF2, EXE and DLL files from the source
tarball, as their license situations were unclear.
I would be happy if someone knowledgeable with maven could take a look
and give me some clues.
Best,
Orcan
[1] https://fedorahosted.org/released/javapackages/doc/#maven