Hi everyone,
I think it would be very beneficial for the community that the maven
dev team communicates on the current events of the sunset of OSSRH.
Otherwise, I think there is a big risk of uncertainty and division in
the community.
Quoting Romain (
https://lists.apache.org/thread/bf3762lvd8l64h
Hi list,
using maven-enforcer-plugin dependency converge rule, the logs of the
trees of the conflicting dependencies represent 7000 lines out of the
12000 lines of logs of my build.
Would it be possible to allow configuring the verbosity of the plugin
? Either with an explicit configuration flag,
Hi,
https://issues.apache.org/jira/browse/MNG-6184 (a.k.a.
https://issues.apache.org/jira/browse/MNG-5592 ) still affects maven today.
It's an old bug so the fix could be delayed, but it is relevant now because
the bug is in the aether code that was migrated to the maven codebase in
3.5.
Jon
On M
Hi,
I opened https://issues.apache.org/jira/browse/MNGSITE-300 to improve the
documentation of the version order.
Cheers,
Jon
Jon
On Mon, Mar 23, 2015 at 6:39 PM, Jon Harper wrote:
> Hi Hervé,
> thanks. I agree that the intro is now better, but I think we need to
> describe the o
For info I've deployed this patch on the site of my project :
https://dev.lutece.paris.fr/plugins/lutece-core/
Le 20 juil. 2016 16:12, "Jon Harper" a écrit :
Hi Karl,
I made a JIRA: https://issues.apache.org/jira/browse/MSKINS-131
Cheers,
Jon
Jon
On Thu, Jul 7, 2016 at 10:14
n
> take a look within the next days...
>
> Kind regards
> Karl Heinz
>
>
> On 7/7/16 5:23 PM, Jon Harper wrote:
>
>> Hello,
>> is anyone interested in this very small change for fluido and doing an 1.6
>> release ?
>> Jon
>>
>> Jon
Hello,
is anyone interested in this very small change for fluido and doing an 1.6
release ?
Jon
Jon
On Wed, Apr 27, 2016 at 7:05 PM, Jon Harper wrote:
> Hi Karl,
> congratulations on improving fluido and releasing fluido 1.5 in february.
>
> I tried enabling Bootstrap's 2 r
Hi Karl,
congratulations on improving fluido and releasing fluido 1.5 in february.
I tried enabling Bootstrap's 2 responsive mode on
https://maven.apache.org and I thought that it was better than the
current version. Please see a demo here: http://jonenst.github.io/maven-site/ .
I also added previ
0, not by the
null value ""!)
+* Complex example
+ * "1.0" < "1.sp" (trailing null value removed, padded to identifier
null, which is less than sp)
+ * "1.sp.1" < "1.0.1" ( .sp < .0 because
ODO: describe the pseudo-lexicographical order used above, using major
version, minor version, incremental version, and qualifier.
+ examples: 1.0.0-SNAPSHOT < 1.0.0 ...
+
*** {Exclusions}
Exclusions explicitly tell Maven that you don't want to include the
Jon
On Sun, Feb 15, 2015 at
s are self-explanatory"
The version element is *not* self-explanatory, especially regarding
interactions between version ranges and *-SNAPSHOTs artifacts.
Any thoughts on this matter would be appreciated.
Regards,
Jon
On Thu, Feb 5, 2015 at 5:52 PM, Jon Harper wrote:
> Hi,
> I
Hi,
I'm resurrecting this old thread to ask if it's possible to change
http://maven.apache.org/pom.html to document the current implementation
behavior (7+ years old).
Please see my comment on MNG-3092:
http://jira.codehaus.org/browse/MNG-3092?focusedCommentId=362616&page=com.atlassian.jira.plugin
12 matches
Mail list logo