It's just a few lines of code - what could go wrong? :-)
There's no IT for this. Have you tested it with your problematic use
case? (was it site:run?)
All the existing ITs pass on Java 1.6.0_31 on MacOS 10.7.
I don't see any errors in the code. The only thing I'm thinking about
is if ConnectExce
Can someone review this for me please.
Core scares the hell outa me.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
As long as the failing ITs have corresponding JIRAs I think this is good.
/Anders
On Thu, Oct 25, 2012 at 7:15 AM, Paul Gier wrote:
> You're right, the maven dependency tree API ran into the same issue.
> Since using the plugin annotation for automatic resolution didn't make
> the problem any be
You're right, the maven dependency tree API ran into the same issue.
Since using the plugin annotation for automatic resolution didn't make
the problem any better (and made it worse in some cases), I switched the
plugin back to resolving dependencies inside the plugin execution, and
merged back the
On 25/10/2012, at 3:05 PM, Barrie Treloar wrote:
> I can't find any docs on what I need to do to get edit access to
> https://cwiki.apache.org/confluence/display/MAVEN/Index.
>
> Anyone able to help out?
Added.
- Brett
-
To
I can't find any docs on what I need to do to get edit access to
https://cwiki.apache.org/confluence/display/MAVEN/Index.
Anyone able to help out?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands
> /**
> - * Class intended to be used by clients who wish to invoke a forked Maven
> process from their applications - *
> * @author jdcasey
> - * @plexus.component role="org.apache.maven.shared.invoker.Invoker"
> role-hint="default" */
> +@Component( role = Invoker.class, hint = "default", desc
yes, that would be great to improve the doc
notice I don't know of any dependency analyzer, then didn't use the feature, I
just imagined the scenario without really trying to use it effectively :)
The idea is to add a dependency to the plugin to an artifact with a custom
analyzer, which has a s
Le mercredi 24 octobre 2012 22:50:19 Arnaud Héritier a écrit :
> It is what I supposed few days ago that it was a problem with aether that
> rejected artifacts installed locally without using aether itself.
not exactly
Aether already resolved the artifact before the plugin deleted it and asked to
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11391&styleName=Html&version=18793
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11391&status=1
Staging repo:
https://repository.apache.org/con
It is what I supposed few days ago that it was a problem with aether that
rejected artifacts installed locally without using aether itself.
it is more annoying if resolver.resolveAlways() doesn't work :(
Arnaud
On Wed, Oct 24, 2012 at 7:25 PM, Hervé BOUTEMY wrote:
> I had a look at the IT outpu
All @since doclettags have been removed[1]
With javadoc:fix it should be very easy to set them again.
I still see 3 deprecated methods:
Commandline:
/**
* @deprecated Use {@link
CommandLineUtils#translateCommandline(String)} instead.
*/
public static String[] translateComman
Hervé:
Sorry to mess this up. Can you supply me with a way to use this
parameter from a POM, so that I could add documentation? The doc that
was in there fooled me into thinking that this was one of those
inject-an-implementation situations, not a real configurable
parameter.
--benson
On Wed, O
how would you configure this from a Pom
On Oct 24, 2012, at 1:20 PM, "Hervé BOUTEMY" wrote:
>> Add missing 'read only' flag to internal injection parameter
> no it's not missing at all, it's a configuration needed when user wants to use
> another dependency analyzer thatn the default one
> Notic
First off, I like the idea. As others have said, it makes us more human
:) Comments inline...
On 2012-10-24 12:36, Kristian Rosenvold wrote:
> r1401610, http://jira.codehaus.org/browse/MPIR-176
>
> Will release this plugin once I have added a spacer.
>
> Btw; some maven devs prefer not to have t
I had a look at the IT output and found this log message
[DEBUG] Skipped remote update check for org.apache.maven.its.dependency:purge-
local-repository:pom:1.0, already updated during this session.
the code causaing this message is in Aether
I doubt maven-dependency-tree will do anything about t
> Add missing 'read only' flag to internal injection parameter
no it's not missing at all, it's a configuration needed when user wants to use
another dependency analyzer thatn the default one
Notice this is a feature and Jira issue I discovered when using blame on code,
and I don't know any depen
ok, let me know if you succeed to do something with the dependency tree API.
Arnaud
On Wed, Oct 24, 2012 at 3:56 PM, Paul Gier wrote:
> Hi Arnaud,
>
> I should have some time today to try out the shared dependency tree API,
> if it doesn't work in Maven 3.0.4 with that, then I'm not sure what e
Hi Arnaud,
I should have some time today to try out the shared dependency tree API,
if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
I can do since this seems to be a regression in 3.0.4. At that point I
will just configure the failing ITs to be skipped for 3.0.4.
Jenkins
ok. thanks
I'll launch the release process tonight.
On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies wrote:
> I reran the build with a clean local repo and it's good. So I withdraw
> my complaint, go right ahead.
>
> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier
> wrote:
> > Strange your iss
yes this is what I have too
[ERROR] * purge-local-repository-reresolve/pom.xml
[ERROR] * purge-local-repository-version-range/pom.xml
which are the ITs mentioned by Paul.
Mountain Lion + Java 6 + Maven 3.0.4
Arnaud
On Wed, Oct 24, 2012 at 2:56 PM, Benson Margulies wrote:
> we are all good h
we are all good here
On Oct 24, 2012, at 8:17 AM, Anders Hammar wrote:
>>> What platform and where to you get that?
>>> I don't get that with 3.0.4 on Mac OS 10.7 and Apple Java 1.6. Two of
>>> the its fail though.
>> MacOSX Mountain Lion and Java 1.6 from apple. The same error below
>> also hap
I reran the build with a clean local repo and it's good. So I withdraw
my complaint, go right ahead.
On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier wrote:
> Strange your issue with the report.
> I don't have it on my side.
> Example :
> https://projects.exoplatform.org/forum/forum-component/for
>> What platform and where to you get that?
>> I don't get that with 3.0.4 on Mac OS 10.7 and Apple Java 1.6. Two of
>> the its fail though.
> MacOSX Mountain Lion and Java 1.6 from apple. The same error below
> also happens when I try the analyze-report report plugin with the
> 2.6-SNAPSHOT.
Stra
Strange your issue with the report.
I don't have it on my side.
Example :
https://projects.exoplatform.org/forum/forum-component/forum-component-common/dependency-analysis.html
I need to investigate more but it won't be before tonight
On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies wrote:
> On
On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies wrote:
> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier wrote:
>> Ok if we are all agree I'll process the release this evening.
>> Thanks for your help guys
>
> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> tested the 're
On Wed, Oct 24, 2012 at 2:41 AM, Anders Hammar wrote:
> What platform and where to you get that?
> I don't get that with 3.0.4 on Mac OS 10.7 and Apple Java 1.6. Two of
> the its fail though.
MacOSX Mountain Lion and Java 1.6 from apple. The same error below
also happens when I try the analyze-re
On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier wrote:
> Ok if we are all agree I'll process the release this evening.
> Thanks for your help guys
I am -1 to a release which does not work, at all, on Maven 3.0.4. I
tested the 'report' mojo last night with the current snapshot and it
died with th
r1401610, http://jira.codehaus.org/browse/MPIR-176
Will release this plugin once I have added a spacer.
Btw; some maven devs prefer not to have their email and hence no avatar,
even though they are registered on gravatar.
I feel inclined to add their direct gravatar url in properties/picUrl;
wou
Ok if we are all agree I'll process the release this evening.
Thanks for your help guys
Arnaud
On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY wrote:
> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> > I did some more testing, and the tests only seem to fail using Maven
> > 3.0.4 for me.
I like.
Very cool
On Wed, Oct 24, 2012 at 10:50 AM, Olivier Lamy wrote:
> 2012/10/24 Kristian Rosenvold :
> > I just hacked together a quick implementation using either
> > properties/picUrl or the gravatar.com avatar for the email address.
> >
> > I did a one-off deploy to http://maven.apache.o
2012/10/24 Kristian Rosenvold :
> I just hacked together a quick implementation using either
> properties/picUrl or the gravatar.com avatar for the email address.
>
> I did a one-off deploy to http://maven.apache.org/team-list.html so you can
> look at the result (register your avatar at gravatar.c
On 24/10/2012, at 6:56 PM, Kristian Rosenvold
wrote:
> I just hacked together a quick implementation using either
> properties/picUrl or the gravatar.com avatar for the email address.
Cool!
>
> I did a one-off deploy to http://maven.apache.org/team-list.html so you can
> look at the result (r
Cool!
/Anders
On Wed, Oct 24, 2012 at 10:02 AM, Stephen Connolly
wrote:
> I like. Pictures make the team feel more human and concrete.
>
> -Stephen
>
> On 24 October 2012 08:56, Kristian Rosenvold
> wrote:
>
>> I just hacked together a quick implementation using either
>> properties/picUrl or th
I like. Pictures make the team feel more human and concrete.
-Stephen
On 24 October 2012 08:56, Kristian Rosenvold
wrote:
> I just hacked together a quick implementation using either
> properties/picUrl or the gravatar.com avatar for the email address.
>
> I did a one-off deploy to http://maven.
35 matches
Mail list logo
