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
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
AFAIK, nothing was done on the job configuration recently [1]
Olivier, the #217 run you launched went well: did you do something?
Regards,
Hervé
[1] https://builds.apache.org/job/maven-plugins-ITs-2.x/jobConfigHistory/
Le vendredi 1 juillet 2011, Barrie Treloar a écrit :
On Sat, Jul 2, 2011 at 2:03 PM, Hervé BOUTEMY herve.bout...@free.fr 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
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
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
On Sat, Jul 2, 2011 at 7:43 PM, Hervé BOUTEMY herve.bout...@free.fr 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
On Sat, Jul 2, 2011 at 7:45 PM, Ralph Goers ralph.go...@dslextreme.comwrote:
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
/Users/benson/asf/mvn/plugins svn cleanup
svn: In directory 'maven-shade-plugin/src/it/mini-jar-package-info'
svn: Error processing command 'committed' in
'maven-shade-plugin/src/it/mini-jar-package-info'
svn: Working copy 'maven-shade-plugin/src/it' locked
svn: run 'svn cleanup' to remove locks
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
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 herve.bout...@free.fr wrote:
yes, plugin depdendencies are downloaded like any other artifacts via
DefaultArtifactResolver in maven-artifact-manager for Maven 2
The problem I reported with svn was local to my checkout; my checkin
had succeeded.
I've applied all the patches with tests, and even written tests for
two without tests. I've invited two others to provide tests, and
there's one interesting patch that poses a legal issue: the submitted
just
Hello
2011/7/2 Hervé BOUTEMY herve.bout...@free.fr:
AFAIK, nothing was done on the job configuration recently [1]
Olivier, the #217 run you launched went well: did you do something?
Nope.
So probably a temporary overload on the machine.
I remember a build took all resources on b.a.o so due to
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
and the
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
Hi
What's the status on this? I know Hervé worked on extracting a shared
component (maven-reporting-exec) for the Maven 3 specific parts of the
plugin. Did you finish with that?
I would like to push for a release of Site Plugin 3 shortly. The only
issue left according to JIRA is this one:
AFAIK, code is ok: I'm closing MSITE-560
the only thing to confirm is the documentation: there is a TODO in
maven-3.apt.vm that we should check carefully: I'm personnally lost on this
one.
Regards,
Hervé
Le samedi 2 juillet 2011, Dennis Lundberg a écrit :
Hi
What's the status on this? I
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 package
On 2 July 2011 20:23, hbout...@apache.org wrote:
Author: hboutemy
Date: Sat Jul 2 19:23:41 2011
New Revision: 1142276
URL: http://svn.apache.org/viewvc?rev=1142276view=rev
Log:
added phase to sample run-its command
Modified:
OK, well, I'm stumped.
In maven-shade-plugin, I modified my local copy to point to
maven-plugins version 20 as parent. This in turn points to maven
parent 20. Which configures the compiler plugin for source level 1.5.
Yet, help:effective-pom shows me source level 1.4, and adding in a
generic
correction: I made shade point to maven-plugins:21, which in turn
points to maven-parent 20, which is the one with the 1.5's in it.
On Sat, Jul 2, 2011 at 8:04 PM, Benson Margulies bimargul...@gmail.com wrote:
OK, well, I'm stumped.
In maven-shade-plugin, I modified my local copy to point to
Oh, Duh, I see. It's only in a profile in the plugin parent. oops.
On Sat, Jul 2, 2011 at 8:04 PM, Benson Margulies bimargul...@gmail.com wrote:
OK, well, I'm stumped.
In maven-shade-plugin, I modified my local copy to point to
maven-plugins version 20 as parent. This in turn points to maven
On Sun, Jul 3, 2011 at 12:30 AM, Hervé BOUTEMY herve.bout...@free.frwrote:
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
On Sun, Jul 3, 2011 at 1:05 AM, Benson Margulies bimargul...@gmail.comwrote:
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
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
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 first
step
of
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
I just realized rather inefficiently that the change to default to 1.5
is still pending for the maven-parent pom, along with a raft of
others. Any objection to staging a release?
-
To unsubscribe, e-mail:
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
29 matches
Mail list logo
