Hi,
First of all, the good news. We were able to integrate maven successfully to
Gentoo. Now, it was able to do most of the general compiling and building
stuff. We build maven-from-source which involve considerable work to
integrate.
But, there's few glitches. There's an error in some builds whi
remember that Maven is a core engine to run plugins.
Maven core does not depend on plexus-velocity [1], but maven-remote-resources-
plugin does [2]
Maven distribution does not contain every library needed by every plugin, but
the logic to download them (hence the "Maven downloads the internet" eff
On Sat, Jul 2, 2011 at 2:03 PM, Hervé BOUTEMY wrote:
> remember that Maven is a core engine to run plugins.
> Maven core does not depend on plexus-velocity [1], but
> maven-remote-resources-
> plugin does [2]
> Maven distribution does not contain every library needed by every plugin,
> but
> the
yes, plugin depdendencies are downloaded like any other artifacts via
DefaultArtifactResolver in maven-artifact-manager for Maven 2 [1].
Plugin resolution and classloader preparation is done in DefaultPluginManager
in maven-core [2]
Velocity and plexus-velocity are nothing different than any li
Not to belittle what you are doing, but on every system I use I
1) Download the maven gziip.
2) unzip it in /opt
3) create a symlink of /opt/maven to the maven I downloaded
4) add /opt/maven/bin to the path in /etc/profile
5) add an export for M2_HOME to /opt/maven in /etc/profile.
Then I start us
On Sat, Jul 2, 2011 at 7:43 PM, Hervé BOUTEMY wrote:
> yes, plugin depdendencies are downloaded like any other artifacts via
> DefaultArtifactResolver in maven-artifact-manager for Maven 2 [1].
>
> Plugin resolution and classloader preparation is done in
> DefaultPluginManager
> in maven-core [2]
On Sat, Jul 2, 2011 at 7:45 PM, Ralph Goers wrote:
> Not to belittle what you are doing, but on every system I use I
> 1) Download the maven gziip.
> 2) unzip it in /opt
> 3) create a symlink of /opt/maven to the maven I downloaded
> 4) add /opt/maven/bin to the path in /etc/profile
> 5) add an ex
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-
I don't see anything obvious
Le samedi 2 juillet 2011, Kasun Gajasinghe a écrit :
> On Sat, Jul 2, 2011 at 7:43 PM, Hervé BOUTEMY wrote:
> > yes, plugin depdendencies are downloaded like any other artifacts via
> > DefaultArtifactResolver in maven-artifact-manager for Maven 2 [1].
> >
> > Plugin
On Jul 2, 2011, at 8:38 AM, Kasun Gajasinghe wrote:
>>
>
> Ralph,
> 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
>
This strikes me as forking maven, making a fundamental changing in the
behavior, and then passing off the results as still 'maven'. I'm not
sure if 'trademark' is the right stepping-off point here, but
something about it seems very wrong.
On Sat, Jul 2, 2011 at 3:22 PM, Ralph Goers wrote:
>
> On
lø., 02.07.2011 kl. 12.22 -0700, skrev Ralph Goers:
> On Jul 2, 2011, at 8:38 AM, Kasun Gajasinghe wrote:
> >>
> >
> > Ralph,
> > 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
On Sun, Jul 3, 2011 at 12:30 AM, Hervé BOUTEMY 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-base
On Sun, Jul 3, 2011 at 1:05 AM, Benson Margulies wrote:
> This strikes me as forking maven, making a fundamental changing in the
> behavior, and then passing off the results as still 'maven'. I'm not
> sure if 'trademark' is the right stepping-off point here, but
> something about it seems very wr
u...@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 wrote:
>
> &
On Sun, Jul 3, 2011 at 3:46 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:
> lø., 02.07.2011 kl. 12.22 -0700, skrev Ralph Goers:
> > On Jul 2, 2011, at 8:38 AM, Kasun Gajasinghe wrote:
> > >>
> > >
> > > Ralph,
> > > No, you are not discouraging me in anyway. This stage is just the
mail
> 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 -
>
I think I died a little reading this. Maven itself already has subtle
strange issues and problems working with dependency ranges, having a gentoo
specific version of maven that does even more different things with artifact
resolution would be a nightmare to deal with. Esp. if you have developers
After this brainstorming with all of you, finally figured out the error. The
issue was with doxia, that is in the site-tools. The build failed in a
compile section, so I didn't thought that caused the issue. I have
incorporated an older incompatible doxia version, thinking I can fix the
site-relate
> Yes, 3.0.3 looks cleaner. Well, I answered the points for choosing 2.2.1.
> We surely need to support 3.0.3 too, the future of maven.
> Is it possible Doxia plays a part here too? We haven't really bothered
> about these site stuff, and therefore, doxia version we have is a little
> older.
no, Do
I just read this mail after reploying to previous, saying that I didn't see
how Doxia could be involved
a nightmare, that's it: I don't understand how something about Doxia could fix
something in Maven core
But it's working: let's celebrate
(I still think I wouldn't be confident when using this
On Sun, Jul 3, 2011 at 1:28 PM, Hervé BOUTEMY wrote:
> > Yes, 3.0.3 looks cleaner. Well, I answered the points for choosing 2.2.1.
> > We surely need to support 3.0.3 too, the future of maven.
> > Is it possible Doxia plays a part here too? We haven't really bothered
> > about these site stuff, a
uh, you've got doxia-module-*.jar in your /usr/share/maven-2/lib/ directory?
but these are not in Maven core: only doxia-api and doxia-logging-api are part
of Maven core [2]
Other Doxia artifacts are used in site plugin only, and should not be shared
in core.
Your problem seems to be related: thi
On Sun, Jul 3, 2011 at 2:28 PM, Hervé BOUTEMY wrote:
> uh, you've got doxia-module-*.jar in your /usr/share/maven-2/lib/
> directory?
> but these are not in Maven core: only doxia-api and doxia-logging-api are
> part
> of Maven core [2]
> Other Doxia artifacts are used in site plugin only, and sh
24 matches
Mail list logo
