And why didn't anyone tell me that? We can't all be maven experts ;)
Frank
On 3/14/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
umm, we already found a solution for that
mvn eclipse:eclipse -U
which tells maven to update its dependencies
woops :)
-igor
On 3/14/07, Frank Bille <[EMAIL PRO
umm, we already found a solution for that
mvn eclipse:eclipse -U
which tells maven to update its dependencies
woops :)
-igor
On 3/14/07, Frank Bille <[EMAIL PROTECTED]> wrote:
I finally got it!! Ok, two things:
First the pom file error. I'll commit a fix for the root pom without the
jdk15
I finally got it!! Ok, two things:
First the pom file error. I'll commit a fix for the root pom without the
jdk15 profile. This was the one which caused problems with the second error.
The first error was because of some old versions of maven plugins. I didn't
find out what it exactly was (thoug
Double-check the top-level pom.xml? It should have
jdk-1.4
jdk-1.5
but your log doesn't seem to show it doing the jdk-1.4 module tree for
soem reason...
/Gwyn
On 14/03/07, Frank Bille <[EMAIL PROTECTED]> wrote:
> I have upgraded to 2.0.5 and also updated to latest svn version of 1.3, and
> I no
I have upgraded to 2.0.5 and also updated to latest svn version of 1.3, and
I now get a different error:
http://www.nabble.com/Al%27s-repository-restructure-tf3386729.html#a9469179
Frank
On 3/13/07, John Patterson <[EMAIL PROTECTED]> wrote:
Strange, I just deleted the entire .m2/repository/o
Strange, I just deleted the entire .m2/repository/org/apache/wicket/
directory and checked out a fresh copy of http://svn.apache.org/repos/
asf/incubator/wicket/branches/wicket-1.x into a new directory,
updated mvn to 2.0.5 (using darwin ports) and ran:
mvn -Dmaven.test.skip=true install
Bu
2.0.5, you say... hmm, I'll try later
Frank
On 3/13/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I just did a clean checkout of our 1.x branch, removed my local
repository, and it 'just worked'.
I do use maven 2.0.5, perhaps that is the deciding factor?
Martijn
On 3/13/07, John Patterso
I just did a clean checkout of our 1.x branch, removed my local
repository, and it 'just worked'.
I do use maven 2.0.5, perhaps that is the deciding factor?
Martijn
On 3/13/07, John Patterson <[EMAIL PROTECTED]> wrote:
> On 13 Mar 2007, at 12:31, Frank Bille wrote:
>
> > I get the same error and
On 13 Mar 2007, at 12:31, Frank Bille wrote:
> I get the same error and have tried to remove local jar files. I'll
> look into it tonight (can't get workspace setup using new "al"
> structure)
>
Great, cheers. Until then I have checked out the last revision
before the restructuring.
-
I removed all wicket jars from my maven repo and also from the target
folders of the source folders. The file wicket-1.3.0-incubating-
SNAPSHOT.jar was recreated but a similar error was shown:
Loading source file /Users/John/Development/wicket-1.x/jdk-1.4/wicket-
extensions/src/main/java/wick
I get the same error and have tried to remove local jar files. I'll look
into it tonight (can't get workspace setup using new "al" structure)
Frank
P.s. Ubuntu linux
On 3/13/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Probably you have remove the jars from your local repository and build
Probably you have remove the jars from your local repository and build again.
Martijn
On 3/13/07, John Patterson <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I get this error message when trying to build wicket:
>
> ERROR] BUILD FAILURE
> [INFO]
> -
Hi,
I get this error message when trying to build wicket:
ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
error: error reading /Users/john/.m2/repository/org/apache/wicket/
wicket/1.3.0-incubating-SNAPSHOT/wicket-
13 matches
Mail list logo
