Greetings, java gurus!
Back to the crime scene, I'm trying my first java package in a very long
time. After reading the java packaging guidelines and the HOWTO I'm
making an attempt on first on a list of dependencies. When running maven
Plugin org.codehaus.mojo:animal-sniffer-maven-plugin:1.13 or one of its
dependencies could not be resolved: Cannot access central
(http://repo.maven.apache.org/maven2) in offline mode and the artifact
org.codehaus.mojo:animal-sniffer-maven-plugin:jar:1.13 has not been
downloaded from it before. -> [Help 1]
Problem is that I don't understand what this tells me. I have tried to
use %pom_remove_plugin and and %pom_remove_dep, to no avail: meven tells
me that the plugin :animal-sniffer-maven-plugin does not exist.
So, in short: what does this message *really* mean, and how should I
cope with it?
The yet-to-be spec: http://ur1.ca/jrl1h
Tnanks in advance,.
Gradle in Fedora has been working for some time and we'd like to execute
the integration test suite you mentioned earlier in November. Can you
provide some instructions about where to find them, what environment do
they need and how to execute them?
I am pleased to announce release of javapackages-tools 4.4.0.
* RPM dependency generators no longer generate requires on optional Maven dependencies
* %mvn_artifact macro now supports optional Maven dependencies
#1178560 -Incorrect flags and options quotation (Michael Simacek)
#1175281 -pom_xpath_replace - begin/end of code added by maintainer comments misplaced (Michael Simacek)
#1183761 -pom_change_dep -r removes possibly relevant information(Michael Simacek)
#1167988 -Prevent user errors from being handled by ABRT
I'm trying out the Fedora 21 Eclipse builds and I'm quite impressed with
all the things which can be cleanly installed through Yum/RPM!
However it appears that the m2e-wtp (1) plug-in hasn't been packaged
yet. It is the only missing piece for building and running Maven
projects in (at least) Tomcat in Fedora 21 out of the box.
Am I correct that such a package is currently unavailable at all? Would
it be possible for me to contribute such a package? Is there any guide
available on creating RPMs for Eclipse plug-ins?
Thanks in advance,
What's new in XMvn 2.3.1
XMvn 2.3.1 was released on 2015-02-13. Most important changes
* Major bugfixes
* Installation of multiple artifacts in one directory
Version 2.3.1 fixes a bug that caused XMvn Install to fail when
trying to install multiple artifacts to the same directory.
* Minor features
* Optional dependencies in effective POM
Since version 2.3.1 effective POMs generated by XMvn include
information whether given project dependency is optional or not.
What's new in XMvn 2.3.0
XMvn 2.3.0 was released on 2015-02-11. Most important changes
* Major features
* Ownership of generated directories
XMvn Install 2.3.0 generates RPM directory ownership (%dir) for
subdirectories it creates.
* Minimal compiler source/target 1.6
XMvn now enforces source and target values of at least 1.6 in
Maven Compiler Plugin.
* Deployer optional dependencies
Metadata format used in 2.3.0 contains new field, which can be
used to flag any artifact dependency as optional. XMvn deployer
and installer were modified to set this flag for generated
* Minor bugfixes
* Skip generating %attr for symbolic links
XMvn 2.3.0 doesn't generate RPM file attributes (%attr) for
symbolic links it creates, which prevents RPM warnings.
* Other changes
* Depmap support dropped
XMvn 2.3.0 removes support for depmaps, which was deprecated for
* Dependecy on Java 8
XMvn now requires Java 8 to run.
I'm considering bumping minimal source/target values in Maven Compiler
Plugin to 1.6 starting from Fedora 23. What is your opinion?
Java 9 is going to drop support for compiling for targets < 1.6.
This change would allow us to notice some problems earlier and give us
more time for fixing them.
Currently XMvn ensures that all Maven builds are compiled with
source/target of 1.5 and that target >= source (this is to avoid
problems caused by JSR-14).
The proposed change would adjust source/target used by Maven Compiler
Plugin when building RPM packages, according to the following snippet:
source = max(source, 1.6)
target = max(target, source)
Are there any objections?
Software Engineer, Red Hat
What's new in XMvn 2.2.1
XMvn 2.2.1 was released on 2015-02-04. Most important changes
* Major bugfixes
* Ivy connector regression bugfix
XMvn 2.1.1 introduced regression in Ivy connector, which
prevented parent POMs from being resolved correctly. Version
2.2.1 fixes this regression.
It came to my attention  that the settings dialog of tuxguitar
shows blank views. My Java and SWT knowledge is limited. No error
messages on the console except some GTK warnings:
(TuxGuitar:4682): Gtk-WARNING **: gtk_widget_size_allocate():
attempt to allocate widget with width -27 and height 26
The upstream for this software is inactive for the last 2-3 years. So
there was no change in the package itself for a while.
I thought maybe someone here might give me a hint about what is going
on. Maybe there's some incompatibility between SWT and GTK that got