Ping.
--
Olivier
Le 7 mai 2012 22:23, "Olivier Lamy" a écrit :
> Hi,
> I'd like to release Maven Remote Resource Plugin 1.3.
> We fixed 4 issues: http://s.apache.org/MRRESOURCES-1.3
>
> The staging repo:
> https://repository.apache.org/content/repositories/maven-052/
> The site staging:
> http:
Issue Subscription
Filter: Design & Best Practices (25 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
https://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
I did notice that! Thanks!
And thanks to everyone for helping me get my first (hopefully of many)
contributions through to the process!
-Chris
Sent from my iPhone
On 11/05/2012, at 8:26 AM, "Robert Scholte" wrote:
> Hi,
>
> Some final notes:
>
> @Laird, thanks, this is indeed one of the mo
Hi,
Some final notes:
@Laird, thanks, this is indeed one of the most important fixes.
@Chris, as you might have noticed you have a non-binding vote. Every
feedback is appreciated.
@Hervé, thanks for fixing the site as mentioned by Mirko.
@Mark, I've adjusted the VOTE-template for the next tim
Hi,
The vote has passed with the following result :
+1 (binding): Olivier Lamy, Hervé Boutemy, Mark Struberg, Robert Scholte
+1 (non binding): Laird Nelson, Chris Graham, Mirko Friedenhagen
I will promote the artifacts to the central repo.
Thanks for the votes!
Robert Scholte
---
Hi,
We solved 1 issues: MCHANGES-281
There are still plenty of issues left in JIRA.
Staging repo:
https://repository.apache.org/content/repositories/maven-077/
Staging site:
http://maven.apache.org/plugins/maven-changes-plugin-2.7.1/
Guide to testing staged releases:
http://maven.apache.org/gu
@java.lang.Deprecated misses not only the description text but also a 'since'
field.
It would be really important to know since when a method is deprecated...
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Thursday, May 10, 2012 9
+1
Op Thu, 10 May 2012 08:54:27 +0200 schreef Mark Struberg
:
+1 (binding)
Just a small note:
Please always also link to the source-release as this is what the ASF
primarily ships. All other artifacts are only nice to have goodies (in
the legal aspect).
https://repository.apache.org
2012/5/10 Jesse Glick :
> On 05/09/2012 12:56 PM, Olivier Lamy wrote:
>>
>> we still need to do some javadoc parsing for @deprecated
>
>
> Just look for @Deprecated - the real annotation - instead. (Note that javac
> will warn you if you have the Javadoc tag without the annotation.)
>
>
>> @since a
+1
Hervé
Le mardi 8 mai 2012 22:46:26 Paul Gier a écrit :
> Hi,
>
> We solved 5 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=17
> 443
>
> There are still a couple of issues left in JIRA:
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jql
+1
Hervé
Le lundi 7 mai 2012 22:23:20 Olivier Lamy a écrit :
> Hi,
> I'd like to release Maven Remote Resource Plugin 1.3.
> We fixed 4 issues: http://s.apache.org/MRRESOURCES-1.3
>
> The staging repo:
> https://repository.apache.org/content/repositories/maven-052/ The site
> staging:
> http://
On 05/09/2012 12:56 PM, Olivier Lamy wrote:
we still need to do some javadoc parsing for @deprecated
Just look for @Deprecated - the real annotation - instead. (Note that javac
will warn you if you have the Javadoc tag without the annotation.)
@since and comments for class/field description.
On Thu, May 10, 2012 at 10:41 AM, Mark Struberg wrote:
> I only have those profiles in my projects. The only profile I have in my
> settings.xml is for enabling staging repos.
>
> Do you have a sample so we get an idea what you try to solve?
Mark, you're getting me wrong. I am not trying to disc
I only have those profiles in my projects. The only profile I have in my
settings.xml is for enabling staging repos.
Do you have a sample so we get an idea what you try to solve?
LieGrue,
strub
- Original Message -
> From: Jochen Wiedmann
> To: Maven Developers List ; Mark Struberg
>
Sorry to hear that you have no fun hacking here anymore.
But just to share some thoughts about the groovy-maven stuff. I can certainly
see that there was lots of bad timing around on both sides in those days. But
the argument for _not_ checking this in to maven 1:1 was mainly because this
featu
On Thu, May 10, 2012 at 10:00 AM, Mark Struberg wrote:
> The reason why it got removed is obvious: you needed to know exactly what
> goes into it. Without that info you sometimes could not even compile your
> project.
>
> What you can try nowadays is to create profiles (maybe in your parent pom
Here my +1.
2012/5/7 Olivier Lamy :
> Hi,
> I'd like to release Maven Remote Resource Plugin 1.3.
> We fixed 4 issues: http://s.apache.org/MRRESOURCES-1.3
>
> The staging repo:
> https://repository.apache.org/content/repositories/maven-052/
> The site staging:
> http://maven.apache.org/plugins/m
activation is king ;)
The reason why it got removed is obvious: you needed to know exactly what goes
into it. Without that info you sometimes could not even compile your project.
What you can try nowadays is to create profiles (maybe in your parent pom) and
have them activated via a system pro
Hi,
just opening a several years old project, which was written for Maven
2 before 3.0 and is making heavy use of profiles.xml.
Reminds me how much I am missing this feature: Local profiles used to
be the most obvious, easiest to use place for
local customizations like configuring a database URL o
19 matches
Mail list logo
