rsync went ok, everything should be good, look it over and make sure its
what you want.
-Mark
Mark R. Diggory wrote:
Stephen,
on minotaur we have:
lrwxrwxr-x 1 jvanzyl apcvs 39 Jan 17 15:59
commons-collections-SNAPSHOT.jar -> commons-collections-20040102.233541.jar
lrwxrwxr-x 1 jvan
Stephen,
on minotaur we have:
lrwxrwxr-x 1 jvanzyl apcvs 39 Jan 17 15:59
commons-collections-SNAPSHOT.jar -> commons-collections-20040102.233541.jar
lrwxrwxr-x 1 jvanzyl apcvs 43 Jan 17 15:59
commons-collections-SNAPSHOT.jar.md5 ->
commons-collections-20040102.233541.jar.md5
a
I've recently discovered that there is a bit of a rogue version of
commons-collections on ibiblio.
The jar named commons-collections-SNAPSHOT, is NOT the latest snapshot, and
in fact represents a time before the last release (3.0). This is causing
lots of misleading comments to float around the we
El vie, 07-05-2004 a las 04:40, Vincent Massol escribió:
> > -Original Message-
> > From: Pablo Lalloni [mailto:[EMAIL PROTECTED]
> > Sent: 07 May 2004 16:47
> > To: Maven Users List
> > Subject: RE: jboss plugin
> >
> > Well, don't think so...
> >
> > The problem was fixed changing '%3D'
Just found this myself, everything was fine under rc1, but fails for rc2.
I'm guessing you are using jboss 3.2.x rather than 3.0.x as I've found the
problem in the plugin.properties file for the maven-jboss-plugin-1.4.
The properties:
maven.jboss.jmx.url.deploy.3.2
maven.jboss.jmx.url.undepl
> -Original Message-
> From: Pablo Lalloni [mailto:[EMAIL PROTECTED]
> Sent: 07 May 2004 16:47
> To: Maven Users List
> Subject: RE: jboss plugin
>
> Well, don't think so...
>
> The problem was fixed changing '%3D' to '=' in urls of
> plugin.properties.
Is that valid? We have:
[...]?a
I am trying to use the hibernate plugin with maven RC1 & JDK 1.4.1
What is strange is that the bottom of the stack trace appear t be caused by
java.lang.NoClassDefFoundError: net/sf/cglib/reflect/FastClass
However net.sf.cglib.reflect.FastClass can clearly be seen high up in the
stack trace, so I
Does Maven provide a mechanism for documenting/specifying compatible
artifacts across groups in a repository?
For example, the struts distribution bundles a number of jars from jakarta
commons. This implies that the struts jar/runtime depends on particular
versions of the commons jars, but if
We put our repository on a webserver, as the URL is sometimes redirected
maven can't locate the new URL.
Are there any solution for redirecting URLs?
thanks,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
Well, don't think so...
The problem was fixed changing '%3D' to '=' in urls of
plugin.properties.
IMHO it should be '=' since there are other instances of it in the urls.
There also also spaces at the end of url strings which should be
removed.
El vie, 07-05-2004 a las 05:37, Stuart Eccles escr
Jean-François,
I did this with a custom goal, something like this:
And
maven.ear.src=target/ear
Hope this help
--
--
Edgar González González
VALHALL
Maybe I didn't have understood your doubt very well, but...
Each POM only create one artifact, so you will need two projects to create
one EAR e one WAR.
Maybe this link can help you :
http://www.theserverside.com/resources/article.jsp?l=MavenMagic
From: Jean-François El Fouly <[EMAIL PROT
Suppose I have a project with a web application. At the moment, I build the
war in this project and the ear in another project that basically has just
a POM, a maven.xml and build.properties.
Though it seems that the ear plugin was designed to build in the web
application project itself rather t
Looks like your JBoss configuration is wrong rather.
are you running the default, all or custom configuration?
-Original Message-
From: Pablo Lalloni [mailto:[EMAIL PROTECTED]
Sent: 06 May 2004 20:39
To: [EMAIL PROTECTED]
Subject: jboss plugin
I'm trying to get the deploy* targets of
Hi vlk,
Thanks.
Any workarounds you know off, instead off building it myself ?
Tia
-wil-
-Oorspronkelijk bericht-
Van: KRÁLIK Vladimír [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 6 mei 2004 16:42
Aan: Maven Users List
Onderwerp: RE: jelly:xml question
Maybe it's this bug in dom4j :
Hi Sean,
A little misunderstanding:
${file} is my original variable
${file.name} is the 'name' property of ${file}, which works fine in
non-expath situation.
Thanks anyway.
-wil-
-Oorspronkelijk bericht-
Van: W. Sean Hennessy [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 6 mei 2004 17:
16 matches
Mail list logo