Re: Packages required for trunk build of OpenMRS with MavenBuilder - next steps?
Hi Ludovic:
On Thu, Nov 18, 2010 at 5:45 PM, Ludovic Claude
<ludovic.claude@laposte.net> wrote:
>
> Hello Misha,
>
> I have fixed this NullPointerException, plus another one (my earlier
> fix, which I thought would apply to your issue).
> Try again with the latest packages in my PPA.
Thank you. You are indeed correct! The NullPointerException is gone :)
Thank you _very_ much.
>
>> Some additional questions:
>> i) I assume no one is packaging
>> org.databene:databene-benerator:debian
>> org.azeckoski:reflectutils:debian
>> ?
>
> Databene-benerator is a medium sized package, with quite a few
> dependencies not yet packaged. As it's used for testing, maybe you can
> skip this package and disable testing for your package.
That seems like a good approach. The only caveat of which I can think
is that any Maven-based OpenMRS
modules (we have a module system within OpenMRS) will depend on the
OpenMRS test Maven module, and that is why, I believe it was moved
into a separate module. (Sorry if that was confusing - to _build_ a
Maven-based OpenMRS module we require the _Maven_ test module of
OpenMRS... hope that is clearer, if not let me know).
Here is the relevant link in the OpenMRS JIRA:
http://tickets.openmrs.org/browse/TRUNK-241?focusedCommentId=161985&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_161985
Of course the big caveat is that currently (to my knowledge) no
maven-based OpenMRS modules exist. But... it's a matter of time ;)
Not sure if/when there will be intent to package OpenMRS modules as
Debian packages at any point in time...
Just in case, I have asked Matt Blanchette, our Maven guru:
http://tickets.openmrs.org/browse/TRUNK-1812?focusedCommentId=163443&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_163443
(I also added him as a cc - sorry Matt :( ).
Thank you again for the suggestion!
>
> Reflectutils is quite easy to package. Run this command and you get a
> good packaging:
> mh_make
> --from-svn=http://reflectutils.googlecode.com/svn/tags/reflectutils-0.9.14/
> Can you take care of this little package? I think it's good training!
Ludovic, wow that is quite a command! I was note aware of that kind of
"magic" at all. It seemed to have
worked beautifully. I have linked the packages below as well as the
debian folder in case you have any comments.
The only question I would have, before filing an ITP, is whether this
should go through the debian-med team and Andreas Tille (who has been
a wonderful sponsor!) or, as this is not really a "medical" package
per se, whether this would be better through the pkg-java team. (fyi I
am not a "Debian developer" and so would have to go through a
"sponsor" to my understanding.)
In any case, here are the relevant files (I was not 100% sure whether
to just upload the .dsc and .changes and/or .tar.gz files so I have
just uploaded them all)
https://bigfile.bcm.tmc.edu/outbound/mk144210/debian.tar1.bz2
https://bigfile.bcm.tmc.edu/outbound/mk144210/libreflectutils-java_0.9.14-1_all.deb
https://bigfile.bcm.tmc.edu/outbound/mk144210/libreflectutils-java-doc_0.9.14-1_all.deb
https://bigfile.bcm.tmc.edu/outbound/mk144210/reflectutils_0.9.14.orig.tar.gz
https://bigfile.bcm.tmc.edu/outbound/mk144210/reflectutils_0.9.14-1.debian.tar.gz
https://bigfile.bcm.tmc.edu/outbound/mk144210/reflectutils_0.9.14-1.dsc
https://bigfile.bcm.tmc.edu/outbound/mk144210/reflectutils_0.9.14-1_i386.changes
Just fyi, for fun, I tried the same command with openmrs, i.e.:
mh_make --from-svn=http://svn.openmrs.org/openmrs/trunk
This worked very well (I changed the name of the package manually to
OpenMRS; I used trunk as this is currently
the only Maven-based version) _until_ it got to the spring-test
dependency. Rather oddly, although it is installed:
misha@debian:~/maven/trunk$ dpkg -l | grep libspring
ii libspring-core-java 3.0.5.RELEASE-1
modular Java/J2EE application framework - Core
ii libspring-test-java 3.0.5.RELEASE-1
modular Java/J2EE application framework - Test helpers
mh_make was not happy and kept insisting I install it again:
In test/pom.xml:
This dependency cannot be found in the Debian Maven repository. Ignore
this dependency?
org.springframework:spring-test:jar:debian
y/[n] >
> dpkg --search /usr/share/maven-repo/org/springframework/spring-test
libspring-test-java: /usr/share/maven-repo/org/springframework/spring-test
Found libspring-test-java
Please install the missing dependency using
sudo apt-get install libspring-test-java
Try again to resolve the dependency?
[y]/n >
Resolving org.springframework:spring-test:jar:debian of scope runtime...
Please install the missing dependency using
sudo apt-get install libspring-test-java
Try again to resolve the dependency?
[y]/n >
I even did an apt-get purge and reinstalled it, then _re_ran mh_make,
but lo and behold got the same effect!
Not sure if this has something to do with it being in the experimental
repo, but that repo is in my /etc/apt/sources.list:
misha@debian:~/maven/trunk$ more /etc/apt/sources.list
# deb http://ftp.us.debian.org/debian/ squeeze main
deb http://ftp.us.debian.org/debian/ squeeze main
deb-src http://ftp.us.debian.org/debian/ squeeze main
deb http://security.debian.org/ squeeze/updates main
deb-src http://security.debian.org/ squeeze/updates main
deb http://ftp.debian.org/debian/ experimental main
deb-src http://ftp.debian.org/debian/ experimental main
deb http://ppa.launchpad.net/ludovicc/ppa/ubuntu maverick main
deb-src http://ppa.launchpad.net/ludovicc/ppa/ubuntu maverick main
Anyway, thought I'd report this, as it seems to be part of maven-debian-helper:
misha@debian:~/maven/trunk$ dpkg -S mh_make
maven-debian-helper: /usr/share/man/man1/mh_make.1.gz
maven-debian-helper: /usr/bin/mh_make
Sorry for all the reports of things _not_ working :( The reflectutils
version worked perfectly! And I am very impressed with how far mh_make
proceeded with OpenMRS :)
(for reference I had done a sudo apt-file update before running this
command, so I believe my apt-file index is up to date).
>
> I have not filed an ITP for the buildnumber Maven plugin, I'm always
> behind when it comes to documenting my work...
No worries. Is there any way to get access to your current work for
testing OpenMRS compile?
I looked in both pkg-java SVN repository:
http://svn.debian.org/wsvn/pkg-java/trunk/#_trunk_
and your PPA:
http://svn.debian.org/wsvn/pkg-java/trunk/#_trunk_
but only found
build-helper-maven-plugin
which seems to be something else.
In any case, no rush. Please take your time.
(Reminder: to use this plug-in, I will have to change the subversion
provider from javasvn to svn, and then add a dependency on the
subversion package as
misha@debian:~/maven/trunk$ dpkg -S /usr/bin/svn
subversion: /usr/bin/svn
. Please let me know if this is somehow _not_ okay. Thank you.)
>
>> web/pom.xml: Dependency is not packaged in the Maven repository for
>> Debian: org.openmrs.api:openmrs-api:debian
> It looks like an old bug. Can you send me the full build log and the
> commands you use, as well as your debian folder.
Sent in private email. Still there in new version unfortunately:
pom.xml: Plugin is not packaged in the Maven repository for Debian:
org.openmrs.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4-mod
test/pom.xml: Dependency is not packaged in the Maven repository for
Debian: org.databene:databene-benerator:0.5.9
api/pom.xml: Dependency is not packaged in the Maven repository for
Debian: org.springframework:spring-beans:3.0.2.RELEASE
web/pom.xml: Dependency is not packaged in the Maven repository for
Debian: org.openmrs.api:openmrs-api:1.8.0-SNAPSHOT
webapp/pom.xml: Plugin is not packaged in the Maven repository for
Debian: org.apache.maven.plugins:maven-war-plugin:2.1-beta-1
>
>> I found the following is now added to debian/maven.cleanIgnoreRules
>> org.openmrs.api openmrs-api s/1\\..*/1.x/ s/.*/debian/ * *
>> is this indeed an indication that this dependency will be ignored?
>
> No, this means that this dependency will be ignored during the clean
> phase of the Maven build, which is what you want (you don't want mvn
> clean to look for a dependency which Maven will build later.)
Ah makes sense. Thank you.
>
> The maven-repo-helper and maven-debian-helper are still under heavy
> development, in particular I will transition from using CDBS in the
> rules file to using debhelper 7, but it's getting more usable now. I
> hope that the new version will reach Debian unstable by the end of the
> year.
Thank you. I am quite impressed with the packages - it seems like a
lot of work to make Maven build offline when, in fact, the whole
system almost is built from the ground up with the expectation the
user will be online. Almost like fitting a square peg into a round
hole... but obviously a very, very important need.
Thank you again for all this hard work, from myself, the OpenMRS
developers, and I'm sure the debian med developers as well.
Misha
p.s. Sorry for the long email :(
>
> Ludovic
>
> On 11/17/2010 10:16 PM, Misha Koshelev wrote:
>> Hi Ludovic,
>>
>> On Wed, Nov 17, 2010 at 1:45 PM, Misha Koshelev <misha680@gmail.com> wrote:
>>> Hello Misha,
>>>
>>> Thanks for the bug report, I have updated my packages and it should fix
>>> this bug.
>> Great news! Minor caveat :(
>>
>> I uploaded to what I believe are the latest versions per:
>> https://launchpad.net/~ludovicc/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick
>>
>> misha@debian:~/maven/trunk$ dpkg -l | grep maven- | grep helper
>> ii maven-debian-helper 1.3.0ubuntu1~ppa5
>> Helper tools for building Debian packages with Maven
>> ii maven-repo-helper 1.4ubuntu0~ppa7
>> Helper tools for including Maven metatada in Debian packages
>>
>> but I seem to still be getting the bug :( Any ideas? (Please see
>> output of dpkg-buildpackage command (attached, relevant blurb is here:
>> ...
>> The list of POM files is now in debian/openmrs.poms
>> /usr/share/maven-debian-helper/copy-repo.sh /home/misha/maven/trunk/debian
>> mh_patchpoms -popenmrs --debian-build --keep-pom-version
>> --maven-repo=/home/misha/maven/trunk/debian/maven-repo
>> --build-no-docs --ignore-rules=debian/maven.ignoreRules
>> --clean-ignore-rules=debian/maven.cleanIgnoreRules
>> Nov 17, 2010 2:34:27 PM org.debian.maven.repo.ListOfPOMs foreachPoms
>> SEVERE: null
>> java.lang.NullPointerException
>> at org.debian.maven.repo.ListOfPOMs.contains(ListOfPOMs.java:155)
>> at org.debian.maven.repo.POMTransformer.keepParentVersion(POMTransformer.java:220)
>> at org.debian.maven.repo.POMTransformer$3.handlePOM(POMTransformer.java:234)
>> at org.debian.maven.repo.ListOfPOMs.foreachPoms(ListOfPOMs.java:98)
>> at org.debian.maven.repo.POMTransformer.transformPoms(POMTransformer.java:230)
>> at org.debian.maven.repo.POMTransformer.main(POMTransformer.java:1073)
>> touch debian/stamp-poms-patched
>> cd . && /usr/lib/jvm/java-6-openjdk/bin/java -noverify -cp
>> /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/java-6-openjdk/lib/tools.jar
>> -Dclassworlds.conf=/etc/maven2/m2-debian.conf
>> org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
>> -Dmaven.repo.local=/home/misha/maven/trunk/debian/maven-repo clean
>> [INFO]
>> NOTE: Maven is executing in offline mode. Any artifacts not already in
>> your local
>> repository will be inaccessible.
>> ...
>> ). It does seem to get farther now, so that is good, but the error is
>> still there.
>>
>> Just in case, before running this command, I deleted debian/*.poms and
>> debian/maven.* files, in case there were any changes in these from the
>> old to new version.
>>
>> Some additional questions:
>> i) I assume no one is packaging
>> org.databene:databene-benerator:debian
>> org.azeckoski:reflectutils:debian
>> ?
>>
>> I tried to search for ITP's using Google (it works for ITP openmrs),
>> but was not even able to find ITP buildnumber which I know you are
>> working on :(
>>
>> Also, regarding
>>
>> web/pom.xml: Dependency is not packaged in the Maven repository for
>> Debian: org.openmrs.api:openmrs-api:debian
>>
>> this dependency is provided by the api module of the project, which
>> will be built before Web. Do I understand that build will proceed with
>> this error, or do I need to explicitly tell maven buildnumber helper
>> or maven repo helper to ignore it somehow?
>>
>> I found the following is now added to debian/maven.cleanIgnoreRules
>> org.openmrs.api openmrs-api s/1\\..*/1.x/ s/.*/debian/ * *
>> is this indeed an indication that this dependency will be ignored?
>>
>>>
>>> About the following bug:
>>> [INFO] Error building POM (may not be this project's POM).
>>>
>>> Project ID: org.openmrs.codehaus.mojo:buildnumber-maven-plugin
>>>
>>> Reason: POM 'org.openmrs.codehaus.mojo:buildnumber-maven-plugin' not
>>> found in repository: System is offline.
>>>
>>> This bug simply means that you will need to package the
>>> buildnumber-maven-plugin. I'm currently working on this particular
>>> plugin, but using the Codehaus version. Is there any reason why OpenMRS
>>> uses their version of the plugin?
>> In order to release valid source tarballs, we would like our sources
>> to compile without .svn folders.
>>
>> This is also (to my understanding) an issue for debian packaging of
>> OpenMRS or any other package.
>>
>> The underlying bug is this
>> http://jira.codehaus.org/browse/MOJO-1539
>> and apparently is related to
>> http://jira.codehaus.org/browse/MOJO-1524
>> The relevant patch is, to my understanding
>> http://jira.codehaus.org/secure/attachment/49652/getScmBranchPatch.txt
>>
>> The OpenMRS bug report is
>> http://tickets.openmrs.org/browse/TRUNK-1747
>> specifically please see the first comment
>> http://tickets.openmrs.org/browse/TRUNK-1747?focusedCommentId=162093&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_162093
>>
>> I hope this clarifies the difference. Thus, I believe we would still
>> need our version of the plug-in, _especially_ if we're using it to
>> build a deb package.
>>
>> I imagine others using this maven plugin might have similar
>> requirements, since they are, by definition, going to be making a deb
>> package.
>>
>> However, if they are _not_ using the javasvn provider for some reason
>> (which does not require native svn), they should be safe.
>>
>> I suppose another fix for a deb would be to require subversion and
>> have a package-specific patch that removes use of the javasvn
>> provider. However, I would imagine other users might need this feature
>> as well, and would _also_ require such a patch.
>>
>> Is there any place I could get a binary version of your efforts?
>> Obviously, this is not necessary until the other plug-ins are packaged
>> (please see previous question), but I am just not clear on the exact
>> status of your buildnumber package as I did not find any relevant ITP
>> or additional info.
>>
>>>
>>> About Spring 3: this package is now in experimental, but once Squeeze is
>>> released, it will move to Unstable then Testing.
>> Great to hear! Thank you.
>>
>> Please pardon my ignorance - I believe that Debian releases do not
>> happen on a _schedule_ as Ubuntu releases do, but would you have any
>> ballpark estimate of when this might happen (OpenMRS 1.8 will be
>> released most likely by end of year, so that would be targeted date
>> for trying to submit a new package to FTP Masters; thank you).
>>
>>> This means that with
>>> some luck it will be picked up automatically by the next Ubuntu,
>>> otherwise it's always possible to file a sync request at Ubuntu and
>>> manually include the latest package into the Universe repository of
>>> Ubuntu. The same applies to my packages.
>> Thank you.
>>
>> Just to clarify, if I am making a package for _debian_, should I still
>> use the package from the standard debian repository? I would imagine
>> that this would be a requirement for submitting such a package to FTP
>> Masters (OpenMRS trunk will be released probably by years' end, so we
>> would, I imagine, have to use the version in debian itself at that
>> time?)
>>
>> Thank you so much for your help and feedback and I appreciate your comments.
>>
>> Misha
>>
>>>
>>> On 11/16/2010 05:41 AM, Misha Koshelev wrote:
>>>>
>>>> Hi Ludovic:
>>>>
>>>> Thank you for your comments.
>>>>
>>>> I downloaded and installed the two packages from your PPA:
>>>> rm -rf /tmp/test > /dev/null 2>&1
>>>> mkdir /tmp/test
>>>> cd /tmp/test
>>>> wget -c https://launchpad.net/~ludovicc/+archive/ppa/+build/2046440/+files/maven-debian-helper_1.3.0ubuntu1~ppa4_all.deb
>>>> wget -c https://launchpad.net/~ludovicc/+archive/ppa/+build/2046441/+files/maven-repo-helper_1.4ubuntu0~ppa6_all.deb
>>>> sudo dpkg -i *.deb
>>>>
>>>> Then added the experimental repository to my /etc/apt/sources.list:
>>>> deb http://ftp.debian.org/debian experimental main
>>>>
>>>> And finally made some changes to my debian folder which are saved here:
>>>> rm -rf /tmp/test > /dev/null 2>&1
>>>> cd /tmp/test
>>>> wget https://bigfile.bcm.tmc.edu/outbound/mk144210/debian.tar.bz2
>>>> svn checkout http://svn.openmrs.org/openmrs/trunk --quiet
>>>> cd trunk
>>>> tar xvjf ../debian.tar.bz2
>>>>
>>>> Finally ran:
>>>> dpkg-buildpackage -rfakeroot -us -uc
>>>>
>>>> You were right in terms of dependencies. However, I thought you might
>>>> be interested in the following NullPointerException:
>>>> dpkg-buildpackage -rfakeroot -us -uc
>>>> dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2
>>>> dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor):
>>>> dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2
>>>> dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2
>>>> dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor):
>>>> dpkg-buildpackage: source package openmrs
>>>> dpkg-buildpackage: source version 1.6.1-1
>>>> dpkg-buildpackage: source changed by Misha Koshelev <misha680@gmail.com>
>>>> dpkg-buildpackage: host architecture i386
>>>> dpkg-source --before-build trunk
>>>> fakeroot debian/rules clean
>>>> test -x debian/rules
>>>> dh_testroot
>>>> mkdir -p "."
>>>> /usr/share/maven-debian-helper/copy-repo.sh /home/misha/maven/trunk/debian
>>>> mh_patchpoms -popenmrs --debian-build --keep-pom-version
>>>> --maven-repo=/home/misha/maven/trunk/debian/maven-repo
>>>> --build-no-docs --ignore-rules=debian/maven.ignoreRules
>>>> --clean-ignore-rules=debian/maven.cleanIgnoreRules
>>>> Nov 15, 2010 10:26:04 PM org.debian.maven.repo.ListOfPOMs foreachPoms
>>>> SEVERE: null
>>>> java.lang.NullPointerException
>>>> at org.debian.maven.repo.ListOfPOMs.contains(ListOfPOMs.java:139)
>>>> at org.debian.maven.repo.POMTransformer.keepParentVersion(POMTransformer.java:204)
>>>> at org.debian.maven.repo.POMTransformer$3.handlePOM(POMTransformer.java:218)
>>>> at org.debian.maven.repo.ListOfPOMs.foreachPoms(ListOfPOMs.java:82)
>>>> at org.debian.maven.repo.POMTransformer.transformPoms(POMTransformer.java:214)
>>>> at org.debian.maven.repo.POMTransformer.main(POMTransformer.java:1037)
>>>> touch debian/stamp-poms-patched
>>>> cd . && /usr/lib/jvm/java-6-openjdk/bin/java -noverify -cp
>>>> /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/java-6-openjdk/lib/tools.jar
>>>> -Dclassworlds.conf=/etc/maven2/m2-debian.conf
>>>> org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
>>>> -Dmaven.repo.local=/home/misha/maven/trunk/debian/maven-repo clean
>>>> [INFO]
>>>> NOTE: Maven is executing in offline mode. Any artifacts not already in
>>>> your local
>>>> repository will be inaccessible.
>>>>
>>>> [INFO] Scanning for projects...
>>>> [INFO] Reactor build order:
>>>> [INFO] OpenMRS
>>>> [INFO] openmrs-test
>>>> [INFO] openmrs-api
>>>> [INFO] openmrs-web
>>>> [INFO] openmrs-webapp
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building OpenMRS
>>>> [INFO] task-segment: [clean]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Error building POM (may not be this project's POM).
>>>>
>>>>
>>>> Project ID: org.openmrs.codehaus.mojo:buildnumber-maven-plugin
>>>>
>>>> Reason: POM 'org.openmrs.codehaus.mojo:buildnumber-maven-plugin' not
>>>> found in repository: System is offline.
>>>>
>>>> org.openmrs.codehaus.mojo:buildnumber-maven-plugin:pom:1.0-beta-4-mod
>>>>
>>>>
>>>> for project org.openmrs.codehaus.mojo:buildnumber-maven-plugin
>>>>
>>>>
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] For more information, run Maven with the -e switch
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Total time: < 1 second
>>>> [INFO] Finished at: Mon Nov 15 22:26:04 CST 2010
>>>> [INFO] Final Memory: 2M/7M
>>>> [INFO] ------------------------------------------------------------------------
>>>> make: [cleanbuilddir] Error 1 (ignored)
>>>> rm -f -r /home/misha/maven/trunk/debian/maven-repo debian/stamp-maven-build
>>>> /usr/bin/make -f debian/rules unpatch-poms
>>>> make[1]: Entering directory `/home/misha/maven/trunk'
>>>>
>>>> Hope that is helpful and something that, if a problem, can be fixed.
>>>>
>>>> We are now looking at making the first official Debian version of
>>>> OpenMRS the 1.8.0 version (to be released later this year), which is a
>>>> Maven based build.
>>>>
>>>> Please let me know if you have any comments with regards to this
>>>> (e.g., what does it mean that libspring-test-java is in experimental;
>>>> would this mean our package would also need to be in experimental???
>>>> My understanding is this would mean end users, even those of squeeze,
>>>> _still_ would not then be able to do apt-get install openmrs, and,
>>>> furthermore, I do not believe it would be merged into Ubuntu
>>>> automatically ???)
>>>>
>>>> Thank you
>>>> Yours
>>>> Misha
>>>> ---
>>>>
>>>> Hello Misha,
>>>>
>>>> I am the author of Maven builder, so I hope I can help here.
>>>>
>>>> First, the tools are still under development, they are usable for
>>>> simple libraries and Maven plugins, but not quite yet for big
>>>> projects.
>>>>
>>>> You will have more luck by taking the latest versions of
>>>> maven-repo-helper and maven-debian-helper at my repository:
>>>> https://launchpad.net/~ludovicc/+archive/ppa/
>>>>
>>>> To build OpenMRS for Debian, we will need to package all dependencies
>>>> and plugins in Debian. Some are already there and an apt-get install
>>>> away:
>>>>
>>>> libmaven-javadoc-plugin-java contains
>>>> org.apache.maven.plugins:maven-javadoc-plugin:2.6.1,
>>>> libantlr-maven-plugin-java contains org.codehaus.mojo:antlr-maven-plugin:2.1
>>>> libmaven-antrun-plugin-java contains
>>>> org.apache.maven.plugins:maven-antrun-plugin:1.4 libspring-java (in
>>>> experimental) contains org.springframework:spring-test:3.0.2.RELEASE
>>>>
>>>> The other dependencies are not packaged in Debian (as far as I can
>>>> tell), but it should be quite easy to do the packaging yourself using
>>>> mh_make. You need to file an ITP (Intention to package) bug request
>>>> following the guidelines at http://www.debian.org/devel/wnpp/. Or file
>>>> a RFP (request for package) at the same place, hoping that somebody
>>>> else will do the job (hint: some requests are more than 1000 days old)
>>>> but I will try to help you of course. Consider also joining the
>>>> pkg-java team, you don't need to be a Debian Developer to participate.
>>>> http://pkg-java.alioth.debian.org/
>>>>
>>>> I will animate a little workshop on Maven & packaging at the Debian
>>>> mini Debconf on Oct 30th, I'll try to publish some material after that
>>>> and bring the wiki pages up to date.
>>>>
>>>> Ludovic
>>>>
>>>>
>>>
>
>
Reply to: