It was with a great pleasure I released Maven 1.1 almost 6 years ago
http://mail-archives.apache.org/mod_mbox/maven-announce/200706.mbox/%3c262c6c680706250248m46d1b285i1792a19fb7c2b...@mail.gmail.com%3E
As you noticed it was so perfect that it didn't require any maintenance ;-)
The king is dead lon
Hi,
I'd like to release PMD Plugin 3.1.
It's a bug fix release.
We fixed 1 issue:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18929&styleName=Text&projectId=11140&Create=Create
Staging repository:
https://repository.apache.org/content/repositories/maven-325/
Staged site: http://mave
I have no more time to spend on maven sadly.
I pushed here some things I would like to see in a new major version
https://gist.github.com/olamy/5081375
And for sure as an end user I have really nothing to do about SLF4J,
aether, Guice or any other component used within the product.
I understand ver
On Mar 4, 2013, at 2:52 AM, Hervé BOUTEMY wrote:
> some more personal thoughts and questions to make myself an opinion
>
> - about determining whether Aether API is biased or not: there was an
> argument
> for not developing Aether in Maven that was "Aether API will be more generic
> to cove
On Mar 3, 2013, at 2:43 PM, Stuart McCulloch wrote:
> On 3 Mar 2013, at 14:16, Jason van Zyl wrote:
>> Hi,
>>
>> No one seems to object to doing a release with the SLF4J support without the
>> isolation so I wanted to discuss what happens when we integrate Eclipse
>> Aether and suggest an alt
+1
On 2/28/2013 1:15 AM, Stéphane Nicoll wrote:
+1
Sent from my iPhone
On 27 Feb 2013, at 19:34, Benson Margulies wrote:
I think it's long overtime for us to officially disclaim support for Maven 1.
-
To unsubscribe, e-ma
This page is completely out of date. Nowadays you would use a repository
manager like Nexus and have most of the issue taken care of..
manfred
> Hi all,
>
> Many projects still don't use maven that for me is the best build
> tool, but have several problems with security, a summary in
> http://doc
+1
2013/3/1 Benson Margulies :
> Hi,
>
> We solved some issues:
>
> ** Bug
> * [MCHANGES-276] - TracDownloader does not set issue key to ticket id
> * [MCHANGES-293] - XML Parser error backtraces from, presumably,
> malformed JIRA responses
> * [MCHANGES-299] - ClassNotFoundException w
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=18988
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MINDEXER%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Staging repo:https:
Let's try to follow the version-convention: if it's only a bugfix, it
should be 3.0.1
Robert
Op Mon, 04 Mar 2013 11:59:42 +0100 schreef Olivier Lamy :
Hi,
I'd like to release PMD Plugin 3.1.
It's a bug fix release.
We fixed 1 issue:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=1
+1
Regards,
Hervé
Le vendredi 1 mars 2013 14:56:15 Benson Margulies a écrit :
> Hi,
>
> We solved some issues:
>
> ** Bug
> * [MCHANGES-276] - TracDownloader does not set issue key to ticket id
> * [MCHANGES-293] - XML Parser error backtraces from, presumably,
> malformed JIRA response
+1
--
Regards,
Igor
On 2013-03-04 12:21 PM, Tamás Cservenák wrote:
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=18988
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MINDEXER%20AND%20
+1 from me
On 2013-03-02 16:18, Benson Margulies wrote:
> Based on the sentiment on the discussion thread, I call a formal vote
> to end support for Maven 1.x. This is a vote to:
>
> 1: Remove maven 1 release materials from the primary distribution
> area, leaving them only on the archive.
>
> 2
My +1.
On Sat, Mar 2, 2013 at 9:18 AM, Benson Margulies wrote:
> Based on the sentiment on the discussion thread, I call a formal vote
> to end support for Maven 1.x. This is a vote to:
>
> 1: Remove maven 1 release materials from the primary distribution
> area, leaving them only on the archive
Hi Olivier,
Previously I aligned the model versions with the product versions. This
commit doesn't follow that path. Unless you plan for the next version of
doxia-sitetools to be 1.3.1, then I suggest changing the model version
to 1.4.0.
On 2013-03-03 16:06, ol...@apache.org wrote:
> Author: olam
Have a look at here
http://svn.apache.org/repos/asf/archiva/site/src/site/site.xml
2013/3/4 Kristian Rosenvold :
> It turns out the missing trade marks from the surefire site
> (http://maven.apache.org/surefire/maven-surefire-plugin/) are because
> the attributions seem to be hard coded into the
agree.
So vote cancel.
2013/3/4 Robert Scholte :
> Let's try to follow the version-convention: if it's only a bugfix, it should
> be 3.0.1
>
> Robert
>
> Op Mon, 04 Mar 2013 11:59:42 +0100 schreef Olivier Lamy :
>
>> Hi,
>> I'd like to release PMD Plugin 3.1.
>> It's a bug fix release.
>> We fixed
Hi,
I'd like to release PMD Plugin 3.0.1.
It's a bug fix release.
We fixed 1 issue:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18929&styleName=Text&projectId=11140&Create=Create
Staging repository:
https://repository.apache.org/content/repositories/maven-328/
Staged site: http://ma
2013/3/4 Dennis Lundberg :
> Hi Olivier,
>
> Previously I aligned the model versions with the product versions. This
> commit doesn't follow that path. Unless you plan for the next version of
> doxia-sitetools to be 1.3.1, then I suggest changing the model version
> to 1.4.0.
agree I just fixed tha
I am trying to replace a attribute in my web.xml by using the maven replacer
plugin but it seems to not be doing anything bec. when I look at my
generated war file the web.xml contains the orginal attribute that I had
wanted to replace - I only want to replace it during a specific build
profile -
20 matches
Mail list logo
