Sure.
I still have stuff to verify too. :-)
2012/8/22 Simone Tripodi :
> Cool! :)
>
> can you wait me this WE to have a review to fluido, first? I stumbled
> in a couple of troubles and I would like to verify they are bugs or
> features :P
>
> TIA,
> -Simo
>
> http://people.apache.org/~simonetripo
Cool! :)
can you wait me this WE to have a review to fluido, first? I stumbled
in a couple of troubles and I would like to verify they are bugs or
features :P
TIA,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99s
2012/8/22 Simone Tripodi :
> Salut mon ami,
>
>> +++ maven/skins/trunk/maven-fluido-skin/pom.xml Tue Aug 21 22:49:07 2012
>> @@ -21,7 +21,7 @@
>>
>> org.apache.maven.skins
>> maven-skins
>> -6
>> +7-SNAPSHOT
>> ../maven-skins/pom.xml
>>
>>
>
> should that drive us on
Salut mon ami,
> +++ maven/skins/trunk/maven-fluido-skin/pom.xml Tue Aug 21 22:49:07 2012
> @@ -21,7 +21,7 @@
>
> org.apache.maven.skins
> maven-skins
> -6
> +7-SNAPSHOT
> ../maven-skins/pom.xml
>
>
should that drive us on releasing the maven-skins:7 parent first?
Hi,
Before the end of the year, all Apache projects must move their
distrib to svnpub (instead of using scp to people.a.o)
It's as simple as having content from
http://www.us.apache.org/dist/maven/ available in
http://dist.apache.org/repos/dist/release/maven/
This is for core distrib (maven 1,2.0,
Good Afternoon Oliver
Is there a JIRA filed (or any text for that matter) describing the MVNCENTRAL
issue you are referring to?
Thanks,
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulic
This is one of the caveat that I have when training people Maven usage and
plugin configuration. The documentation is always the newest and it is
actually hard to find old sites and the respective documentation.
The example I always use is the compiler plugin defaulting to language
level 1.3 with
Hi,
To follow up a MVNCENTRAL issue [1], I'd like to define such search
api in maven-indexer.
As it various repo manager will be able to implement the same api for
various consumer which will be certainly happy to consume only one
same api :-).
I can propose something in maven-indexer codebase (b
