On Sun, Jul 3, 2011 at 6:06 AM, Martin Gainty <mgai...@hotmail.com> wrote:
> > there are 4 classpath properties you pass to the maven-ant runtime > environment > <property name="compile_classpath" > refid="maven.compile.classpath"/> > <property name="runtime_classpath" > refid="maven.runtime.classpath"/> > <property name="test_classpath" > refid="maven.test.classpath"/> > <property name="plugin_classpath" > refid="maven.plugin.classpath"/if the missing jar is located on > maven.runtime.classpath then the ant runtime should resolve the classpath > > http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html > > when you get a chance could you explain why you are repackaging maven in an > ant environment > seems like you're effort is to stuff a mercedes engine in a yugo > ? > You are missing the point. We are not running ant inside maven. We use ant only for packaging maven itself (bootstrapping). That's the solution for the hen and egg problem in maven. There is no need of AntRun plugin. Thanks for trying to help anyway. --Kasun > Martin Gainty > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > From: kasu...@gmail.com > > Date: Sun, 3 Jul 2011 05:44:37 +0530 > > Subject: Re: [Gentoo-Maven-Intg] plexus-velocity missing - > maven-remote-resources-plugin fails with a ClassNotFoundException > > To: dev@maven.apache.org > > > > On Sun, Jul 3, 2011 at 12:30 AM, Hervé BOUTEMY <herve.bout...@free.fr > >wrote: > > > > > Le samedi 2 juillet 2011, Kasun Gajasinghe a écrit : > > > > No, you are not discouraging me in anyway. This stage is just the > first > > > > step of a much wider task. The ultimate goal of this work is to > provide > > > > the ability to package maven-based builds to Gentoo system. Gentoo > > > > encourages and the package-management installs packages by first > > > compiling > > > > them from source. So, as you can understand, if the package source > uses > > > > maven as the build management tool, it needs maven to do the building > and > > > > generate the jar. > > > > > > > > Further, there are other constraints involved. Mainly the packages > should > > > > be able to use the existing jars available in the system (under > > > > /usr/share), and we've are not strict about having a specific version > as > > > a > > > > dep as long the existing system jar is api-compatible. > > > honestly, this is the part I really doubt about: it will be hard to do > > > (will > > > need to change the way Maven resolves dependencies), and I expect there > > > will > > > be a lot of failures since dependencies version modification in general > > > causes > > > failures. > > > > > > As a proof of concept, I find the task fun. > > > As a user, I expect a lot of problems and wouldn't really be confident > > > about > > > this. > > > > > > > > To re-iterate, as a 'user' this will have a 'normal' behavior of Maven. > It's > > the system part that will be different, and have the said constraints. > > > > And, maven is packaged with almost the same dependency versions of Maven. > > There were few exceptions in some Plexus packages, but the versions are > > close enough and api-compatible. Do you really think this leads to the > said > > error? > > > > But if you want to try, why not :) > > > > > > > Well, we have packaged ant and is in a good working condition. Now, > > unfortunately, maven-based projects don't have a simpler way to package > > their projects, to be installed via portage (the package mgt system). We > are > > going to provide a direct way for this. > > > > > > --Kasun > > > > -- > > ~~~*******'''''''''''''*******~~~ > > Kasun Gajasinghe, > > University of Moratuwa, > > Sri Lanka. > > Blog: http://blog.kasunbg.org > > Twitter: http://twitter.com/kasunbg > > -- ~~~*******'''''''''''''*******~~~ Kasun Gajasinghe, University of Moratuwa, Sri Lanka. Blog: http://blog.kasunbg.org Twitter: http://twitter.com/kasunbg
