bsf maven questions
by Orion Poplawski
I'm trying to build apache-commons-jexl 2.0.1 in rawhide and am getting:
Failed to resolve artifact.
Missing:
----------
1) org.apache.bsf:bsf-api:jar:3.0-beta3
It uses the javax.script API which as I understand it is included in Java 1.6.
The jexl pom.xml has:
<!-- For JSR-223 API -->
<dependency>
<groupId>org.apache.bsf</groupId>
<artifactId>bsf-api</artifactId>
<version>3.0-beta3</version>
<scope>provided</scope>
</dependency>
Short of patching that out of the pom.xml file (which works), is there some
way I (or something else) should express that bsf-api 3.0 is provided? Or is
jexl upstream misguided in adding this dependency?
Thanks!
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years
Rebase of log4j with bigger changes
by Stanislav Ochotnicky
Hi,
Just a few minutes ago I updated log4j to 1.2.16 (in rawhide). It is now
built with maven and there are other changes as well. If your packages
have dependency on log4j you might want to know that this change
happened. There might be something I missed when re-working the spec
file, so if any problems arise don't hesitate to file new bugs.
--
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Associate Software Engineer - Base Operating Systems Brno
PGP: 71A1677C
Red Hat Inc. http://cz.redhat.com
14 years
How to build SRPMs for Rawhide from Fedora 12
by Edmon Begoli
Hi,
I am working on a Fedora 12 machine, but I would like to build Java
packages for rawhide
without necessarily enabling rawhide repository for all the system (it
messes with the stable updates).
How can I create an RPM build environment for rpmbuild that accesses
all the dependencies available
in rawhide without affecting the host?
Thank you in advance.
EB
14 years
Re: [fedora-java] Could someone, please, clarify situation with *-javadoc
by Alexander Boström
(changing lists)
fre 2010-05-07 klockan 13:41 -0400 skrev Andrew Overholt:
> Hi,
>
> > Sometimes *-javadoc sub-packages explicitly requires main package, and
> > sometimes - not. I'm not a java-expert, so I don't know which is
> > correct.
>
> I don't think it really matters. In some cases, sure, it would be nice
> to ensure that the package is around if someone is looking at the API
> documentation. Other times someone may only want to peruse the APIs
> without installing the implementation.
Agreed. Those deps are now removed from the examples in
https://fedoraproject.org/wiki/User:Abo/JavaPackagingDraftUpdate which I
previously submitted as a proposed guideline update. (I hope I submitted
it the right way...)
Somehow I managed to not notice the java-devel list until recently so I
think this is the first time I've mentioned the draft here. Please read
and comment on it! The number of changes are growing...
I should move it out of the User:Abo namespace so it doesn't look like a
personal page.
/Alexander
14 years
maven : org.apache.maven:maven-model-v3:jar:2.0 is missing
by Mohamed El Morabity
Hi,
I'm trying to package clirr, which is a BuildRequires for the latest
version of apache-commons-math.
The rebuild of my package fails on the following errors (mvn-jpp is
called in my .spec as set in the Java guidelines):
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.maven:maven-model-v3:jar:2.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven
-DartifactId=maven-model-v3 -Dversion=2.0 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.maven
-DartifactId=maven-model-v3 -Dversion=2.0 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.maven.plugins:maven-one-plugin:maven-plugin:2.0.8
2) org.apache.maven.shared:maven-model-converter:jar:2.1
3) org.apache.maven:maven-model-v3:jar:2.0
----------
1 required artifact is missing.
for artifact:
org.apache.maven.plugins:maven-one-plugin:maven-plugin:2.0.8
from the specified remote repositories:
apache.snapshots (http://people.apache.org/maven-snapshot-repository),
__jpp_repo__ (file:///usr/share/maven2/repository),
central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Apr 09 22:33:01 CEST 2010
[INFO] Final Memory: 6M/107M
[INFO]
------------------------------------------------------------------------
Yet maven-shared-model-converter seems to be installed:
$ rpm -q maven-shared-model-converter
maven-shared-model-converter-2.3-3.fc12.noarch
Anyway I'm not a specialist of Maven ^^.
Any idea about this problem?
Thanks :)
14 years
Packaging from JPackage spec - any required changes to license, coordinating with commons rename?
by Edmon Begoli
Hi,
I am re-packaging html-unit from JPackage source to Fedora target
rawhide for submission for sponsorship.
1) JPackage requires retention of the comments including copyright and
license (see Appendix to e-mail).
Do I need to do any modifications to it?
2) Following commons packages are required:
BuildRequires: jakarta-commons-codec >= 0:1.3
BuildRequires: jakarta-commons-collections32
BuildRequires: jakarta-commons-fileupload >= 0:1.2.1
BuildRequires: jakarta-commons-httpclient >= 0:3.0.1
BuildRequires: jakarta-commons-io >= 0:1.3.1
BuildRequires: jakarta-commons-lang24
BuildRequires: jakarta-commons-logging >= 0:1.1
Packaging rename task specifies Rawhide Fedora 14 as target rename release:
https://fedoraproject.org/wiki/JakartaCommonsRename
Should I wait for rename of these for Rawhide Fedora 14 to appache-commons-...
before submiting package for review, or should I target earlier release?
Please advise.
14 years, 1 month
jakarta-commons rename
by Stanislav Ochotnicky
Hi,
as some of you are aware jakarta-commons changed name to apache-commons
some time ago. We should probably start process of renaming these
packages in Fedora as well to match upstream.
I made a list of -commons components that do not depend on other
-commons. This was done with a crude grep of checked out sources so
there might be omissions). Owners of packages included:
jakarta-commons-codec - mbooth
jakarta-commons-launcher - mbooth
jakarta-commons-logging - mbooth
jakarta-commons-pool - mbooth
jakarta-commons-daemon - pcheung
jakarta-commons-io - pcheung
jakarta-commons-lang - pcheung
jakarta-commons-net - pcheung
jakarta-commons-collections - devrim
jakarta-commons-compress - red
jakarta-commons-el - fnasser
Starting with these packages should make it easier to continue with the
rest (because for those we can already start using new names in Requires).
Any ideas/notes are welcome,
--
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Associate Software Engineer - Base Operating Systems Brno
PGP: 71A1677C
Red Hat Inc. http://cz.redhat.com
14 years, 1 month
Self-introduction - Java QA and Development
by Edmon Begoli
Hi,
My name is Edmon Begoli and I am a new active member of the Fedora Project.
I am an experienced Java developer, so I am contacting you guys to
introduce myself
and to offer help in:
- testing any Java related packages - it seems that JDK 7 may need a
testing owner and I would like to be a point person for this one
- helping developing or packaging anything related to Java
Thank you in advance and please feel free to engage me in Java related
tasks - testing, packaging or development.
Edmon Begoli
http://it.toolbox.com/blogs/lim
http://ebegoli.fedorapeople.org
14 years, 1 month
