Hi,
This should be on the users mailing list. anyway, to answer your question,
When using deploy-deploy-file goal and encountered this error
"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find
wagon which supports the requested protocol: ftp"
You only have to place the approp
I've posted some attachments to the JIRA issue WAGON-55 [1] to implement
support for accepting GZip-based compression with HTTP GETs for HTTP and
WebDAV. I'm hoping these simple changes can help to reduce some bandwidth
needs. I've seen some significant gains from my personal testing.
In any case,
Committed the proposed changes in
http://svn.apache.org/viewvc?view=rev&revision=420352
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
It seems to me that the consensus is to stay with 1.4 (or not, in any
case...) on a related note: Does it make sense to have plugins require a
specific version of jdk to run? This would allow the plugin toolkit to make
use of current language constructs (annotations), but reducing of
portability.
Brett Porter <[EMAIL PROTECTED]> writes:
If you use maven to develop for a J2EE 1.2/1.3 target enviroment, your
code is required to run on JDK 1.4
A continuum run that builds that code targeted for 1.4 using a JDK 5
is pretty much useless because it doesn't build what must get
deployed.
If you a
http://people.apache.org/maven-snapshot-repository/
On 7/9/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
David Blevins wrote:
> On Jul 3, 2006, at 12:53 PM, Mohammed Nour wrote:
>
>> Hi All...
>> While building OEJB3.0 a missing dependency has been found, it is
>> xbean-finder jar artifact vers
David Blevins wrote:
On Jul 3, 2006, at 12:53 PM, Mohammed Nour wrote:
Hi All...
While building OEJB3.0 a missing dependency has been found, it is
xbean-finder jar artifact version 2.4-SNAPSHOT, I could not found
this jar artifact on any site listed in the main pom.xml file, I
could only fin
On 7/9/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Carlos Sanchez wrote:
> Some comments
Thanks!
> - add SHA1 checksums where you mention MD5. Maven2 uses first SHA1 if
> present
Will do that.
> - Maven2 to Maven 2 / Releasing the next version
>
> When the next release of <<>> is made, you
Dennis Lundberg wrote:
Trygve Laugstøl wrote:
Brett Porter wrote:
I believe qdox has been fixed and we just need an upgrade, but I'm
not sure. AFAIK it doesn't work with the current version.
It does not work in current version of the java plugin tool since qdox
1.5 doesn't support generics.
Carlos Sanchez wrote:
Some comments
Thanks!
- add SHA1 checksums where you mention MD5. Maven2 uses first SHA1 if
present
Will do that.
- Maven2 to Maven 2 / Releasing the next version
When the next release of <<>> is made, you only need to publish a
Maven 2
pom with a groupId of <<>>,
+1 for Continuum/MRM
-1 for maven, I know lots of users still using 1.4 and this is part of
the company policy to run stuff with 1.4.
Stéphane
> Hi,
>
> I wanted to get thoughts on starting to require a Java 5 JVM to run
> stuff we build. We currently restrict to 1.4 across the board.
>
> Here
Trygve Laugstøl wrote:
Brett Porter wrote:
I believe qdox has been fixed and we just need an upgrade, but I'm not
sure. AFAIK it doesn't work with the current version.
It does not work in current version of the java plugin tool since qdox
1.5 doesn't support generics.
I tried to upgrade to
12 matches
Mail list logo
