This is a user question so you should ask it on the user list. If you have a
proxy, it's not used by Maven it seems. Check your local settings.
S.
On Wed, Nov 10, 2010 at 7:46 PM, Hahn, Christopher (SAN DIEGO) <
christopher.h...@hp.com> wrote:
> Hello,
>
>
>
> Yesterday I was asked to upgrade t
I replied off-list suggesting users@ instead of iss...@. -Wendy
On Wed, Nov 10, 2010 at 7:39 PM, shragi wrote:
>
> I downloaded a project that is build using maven. I also downloaded maven
> 2.2.1 version. This is the first time I am using maven.
...
-
Ah, yes, the env is so often the issue (i.e. cron)
I will think about this.
Thank you for taking the time.
Chris
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, November 10, 2010 3:06 PM
To: Maven Developers List
Subject: Re: RE: runn
Well I've seen differences in the environment that gets passed from maven to
ant versus running ant directly.
.. And to further complicate this, the environment that ant gets is
different again when in a forked maven eg during release: prepare
- Stephen
---
Sent from my Android phone, so random
+1
Vincent
2010/11/9 Dennis Lundberg :
> Hi,
>
> We solved 6 + 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16748
> http://jira.codehaus.org/browse/DOXIA-410
> http://jira.codehaus.org/browse/DOXIA-412
> http://jira.codehaus.org/browse/DOXIA-
+1
Thanks !
2010/11/9 Dennis Lundberg :
> Hi,
>
> We solved 6 + 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16748
> http://jira.codehaus.org/browse/DOXIA-410
> http://jira.codehaus.org/browse/DOXIA-412
> http://jira.codehaus.org/browse/DOXIA
+1
Thanks Dennis!
-Lukas
Dennis Lundberg wrote:
Hi,
We solved 6 + 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16748
http://jira.codehaus.org/browse/DOXIA-410
http://jira.codehaus.org/browse/DOXIA-412
http://jira.codehaus.org/browse/DOXIA
Thanks for the clarification John.
On 2010-11-10 15:27, John Casey wrote:
> The documentation should reference configuration, not
> . I've been watching the JIRAs, but haven' had time to
> mount a new offensive to get another release out.
>
> The short story is there was a lot of potential for b
Hello,
Yesterday I was asked to upgrade the version of maven-assembly-plugin
in our local repository.
I settled on the 2.2 release, change the version in my toplevel pom to this
value,
and ran the command I expected to handle this for me.
Output:
I appreciate the tenacity!
Look earlier in the threadI have a build.xml that
defined the restartora target.
It runs fine when called from ant on the command line,
but fails when called out in the pom (also pasted in below)
Any clues appreciated.
Chris
-Original Message-
From: Den
On 10 November 2010 14:02, Jesse Glick wrote:
> The trouble with Javadoc pseudo-annotations is that they are unavailable in
> bytecode and thus invisible to a tool like sigtest. I don't know about
> Clirr. I suspect this particular set of Javadoc tags was designed with
> Eclipse editor hints in mi
The documentation should reference configuration, not
. I've been watching the JIRAs, but haven' had time to
mount a new offensive to get another release out.
The short story is there was a lot of potential for bad things to happen
in the complex code used to load descriptors. Paired with the
On 11/09/2010 07:07 PM, Rex Hoffman wrote:
I'm leaning to using the (javadoc) annotations
The trouble with Javadoc pseudo-annotations is that they are unavailable in bytecode and thus invisible to a tool like sigtest. I don't know about Clirr. I suspect this
particular set of Javadoc tags was
13 matches
Mail list logo
