Hi there,
I am toying with some thoughts to make a bigger leap with MI. I plan to
start 6.0 of it, with following changes:
Changes would be along these lines:
- Collapse indexer-artifact into indexer-core (this modularization had a
historical reason, coming from Sonatype Nexus)
- Remove Maven1
I saw the requirement for Ant 1.8 or later. The encoding option in
the echo task is new since Ant 1.7.
To install ant 1.7, 1.8 or 1.8.4 requires JUnit to already be present.
Unfortunately, to build JUnit you need maven in place.
Hence my attempt to install/build maven.
I found that I was able
Hi,
I'm under the impression this question should have actually been asked on
the user ML.
You seem to be trying to build Maven although you shouldn't have to do.
So, what are you actually trying to achieve currently?
Maven is a pure Java tool, so unless you're actually trying to hack on
Maven
The Apache Software Foundation releases open _source_ products. If one
of our users wants to build the product from source, instead of using
our convenience binaries, we should be helping, not pushing them to
the binaries.
On Thu, Nov 7, 2013 at 8:37 AM, Baptiste Mathus m...@batmat.net wrote:
Try adding:
mkdir
dir=bootstrap/target/classes/META-INF/maven/org.apache.maven/maven-core /
before the echo task on line 236
On 7 Nov 2013, at 13:27, Ed Mansky wrote:
I saw the requirement for Ant 1.8 or later. The encoding option in the echo
task is new since Ant 1.7.
To
Well, I agree. I was just pointing that out because that might not actually
be what Ed actually wants.
I had this fuzzy feeling when reading his mails (and not seing a sentence
assertively stating that he didn't want to use the already provided
binaries, which is fine in the ASF you're totally
PS. note that JUnit is only required by the Ant tests, you can build a minimal
distribution of Ant by removing the test-jar dependency from dist-lite and
running:
ant dist-lite
Alternatively if you want to run the Ant unit tests for sanity checking, you
can always build a basic JUnit4
Hi,
Yes, I tried to use the binaries first, but on the ppc architecture
when I type mvn -version
I see:
Exception in thread main java.lang.NoClassDefFoundError:
org/codehaus/plexus/classworlds/launcher/Launcher.
I get this for Maven version 3.1.1
What I am trying to do is install the
I'd step back and try Maven 3.0.5's binaries... I am beginning to wonder if
a Java 6 dependency crept into 3.1.x
On 7 November 2013 15:05, Ed Mansky man...@mindspring.com wrote:
Hi,
Yes, I tried to use the binaries first, but on the ppc architecture when I
type mvn -version
I see:
I'd try to unset M2_HOME and/or MAVEN_HOME. Seems like the typical error
you get when you set that variable pointing to another maven version than
the one you're currently trying to run.
Most often I just advise to get simply get rid of its use anywhere. Maven
actually doesn't need it and finds
Sounds good plan.
Perso I would prefer use @Inject and not using container specific.
(if possible)
On 7 November 2013 21:03, Tamás Cservenák ta...@cservenak.net wrote:
Hi there,
I am toying with some thoughts to make a bigger leap with MI. I plan to
start 6.0 of it, with following changes:
11 matches
Mail list logo
