maven-archetype-2.0-alpha-5 tag

[Stevo Slavić]

Hello Maven developers,

I'd like just to inform you that while checking out maven archetype I've
noticed that there is a maven-archetype-2.0-alpha-5 tag created in April
2009; most recent release is 2.0-alpha-4 from September 2008, and current
trunk is 2.0-alpha-5-SNAPSHOT, so this existing maven-archetype-2.0-alpha-5
tag might cause problems when 2.0-alpha-5 gets actually released.

Regards,
Stevo.

Re: [VOTE] Release Maven reporting impl version 2.0.4.3

[Mark Hobson]

2009/11/10 Vincent Siveton :
> The vote has passed with the following result :
> +1 Benjamin, Lukas, Dennis, Hervé, Vincent
>
> I will promote the artifacts to the central repo.

Have the artifacts been promoted to central?  I can't see them:

http://repo1.maven.org/maven2/org/apache/maven/shared/maven-reporting-impl/

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven-archetype-2.0-alpha-5 tag

[Brett Porter]

Nice catch, I've removed it.

On 12/11/2009, at 7:22 PM, Stevo Slavić wrote:

> Hello Maven developers,
> 
> I'd like just to inform you that while checking out maven archetype I've
> noticed that there is a maven-archetype-2.0-alpha-5 tag created in April
> 2009; most recent release is 2.0-alpha-4 from September 2008, and current
> trunk is 2.0-alpha-5-SNAPSHOT, so this existing maven-archetype-2.0-alpha-5
> tag might cause problems when 2.0-alpha-5 gets actually released.
> 
> Regards,
> Stevo.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven-archetype-2.0-alpha-5 tag

[Stevo Slavić]

Great!

Debugged 2.0-alpha-4, and I think I've solved
ARCHETYPE-220issue. Can
someone with enough privileges please flag the issue that it
contains a patch (no additional tests, yet), and if agreed to increase issue
priority from Minor to Major as IMO this issue prevents archetype-plugin
from being fully adopted, especially in (closed source) corporate
environments.

Regards,
Stevo.

On Thu, Nov 12, 2009 at 12:26 PM, Brett Porter  wrote:

> Nice catch, I've removed it.
>
> On 12/11/2009, at 7:22 PM, Stevo Slavić wrote:
>
> > Hello Maven developers,
> >
> > I'd like just to inform you that while checking out maven archetype I've
> > noticed that there is a maven-archetype-2.0-alpha-5 tag created in April
> > 2009; most recent release is 2.0-alpha-4 from September 2008, and current
> > trunk is 2.0-alpha-5-SNAPSHOT, so this existing
> maven-archetype-2.0-alpha-5
> > tag might cause problems when 2.0-alpha-5 gets actually released.
> >
> > Regards,
> > Stevo.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven reporting impl version 2.0.4.3

[Vincent Siveton]

Hi Mark,

It seems that we changed the groupid/artifactid in the past. Here the
right link:
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/

Cheers,

Vincent

2009/11/12 Mark Hobson :
> 2009/11/10 Vincent Siveton :
>> The vote has passed with the following result :
>> +1 Benjamin, Lukas, Dennis, Hervé, Vincent
>>
>> I will promote the artifacts to the central repo.
>
> Have the artifacts been promoted to central?  I can't see them:
>
> http://repo1.maven.org/maven2/org/apache/maven/shared/maven-reporting-impl/
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.0-alpha-3

[Brett Porter]

+1

I downloaded the source tarball and verified the signature matches KEYS. I 
built from source, then rebuilt the source with itself without error on a clean 
repository. I'll do some more testing, but that's sufficient for an alpha 
release. Nice work!

Cheers,
Brett

On 10/11/2009, at 3:39 AM, Benjamin Bentmann wrote:

> Hi,
> 
> OK, here we go, another alpha release of Maven, for all those brave guys that 
> want to take it for a test drive ;-)
> 
> We solved many issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamim
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.0-alpha-3

[Vincent Siveton]

+1

Vincent

2009/11/9 Benjamin Bentmann :
> Hi,
>
> OK, here we go, another alpha release of Maven, for all those brave guys
> that want to take it for a test drive ;-)
>
> We solved many issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
>
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> +1 from me
>
>
> Benjamim
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: IT failure (was: [VOTE] Release Apache Maven 3.0-alpha-3)

[Brett Porter]

Doesn't affect my vote, but I noted that this IT fails on 3.0-alpha-3, even 
though it is marked as fixed in JIRA:
- mng4361ForceDependencySnapshotUpdate

Anyone else see the same result or should I post logs?

Cheers,
Brett

On 12/11/2009, at 11:00 PM, Brett Porter wrote:

> +1
> 
> I downloaded the source tarball and verified the signature matches KEYS. I 
> built from source, then rebuilt the source with itself without error on a 
> clean repository. I'll do some more testing, but that's sufficient for an 
> alpha release. Nice work!
> 
> Cheers,
> Brett
> 
> On 10/11/2009, at 3:39 AM, Benjamin Bentmann wrote:
> 
>> Hi,
>> 
>> OK, here we go, another alpha release of Maven, for all those brave guys 
>> that want to take it for a test drive ;-)
>> 
>> We solved many issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
>> 
>> There are still a couple of issues left in JIRA:
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>> 
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-004/
>> 
>> Staged source and binary distros:
>> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
>> 
>> Guide to testing staged releases:
>> http://maven.apache.org/guides/development/guide-testing-releases.html
>> 
>> Vote open for 72 hours.
>> 
>> [ ] +1
>> [ ] +0
>> [ ] -1
>> 
>> +1 from me
>> 
>> 
>> Benjamim
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

integration test versioning policy?

[Brett Porter]

Hi,

I ran the ITs against 3.0-alpha-3 and got a number of failures.

Several of those are because they are fixed in 3.0-alpha-4 but marked to run 
for all versions:
- mng4412OfflineModeInPlugin
- mng4433ForceParentSnapshotUpdate

Before correcting anything I would like to check I understand the policy 
correctly: should the versions be set to the versions for which the tests 
should run 100%? Or is there a deliberate move to show failures where something 
didn't work because of a regression (such as the ones above)?

Thanks,
Brett
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: IT failure (was: [VOTE] Release Apache Maven 3.0-alpha-3)

[Brian Fox]

That sounds like the one that is supposed to be fixed in alpha-4

On Thu, Nov 12, 2009 at 8:20 AM, Brett Porter  wrote:
> Doesn't affect my vote, but I noted that this IT fails on 3.0-alpha-3, even 
> though it is marked as fixed in JIRA:
> - mng4361ForceDependencySnapshotUpdate
>
> Anyone else see the same result or should I post logs?
>
> Cheers,
> Brett
>
> On 12/11/2009, at 11:00 PM, Brett Porter wrote:
>
>> +1
>>
>> I downloaded the source tarball and verified the signature matches KEYS. I 
>> built from source, then rebuilt the source with itself without error on a 
>> clean repository. I'll do some more testing, but that's sufficient for an 
>> alpha release. Nice work!
>>
>> Cheers,
>> Brett
>>
>> On 10/11/2009, at 3:39 AM, Benjamin Bentmann wrote:
>>
>>> Hi,
>>>
>>> OK, here we go, another alpha release of Maven, for all those brave guys 
>>> that want to take it for a test drive ;-)
>>>
>>> We solved many issues:
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
>>>
>>> There are still a couple of issues left in JIRA:
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/maven-004/
>>>
>>> Staged source and binary distros:
>>> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
>>>
>>> Guide to testing staged releases:
>>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>>
>>> Vote open for 72 hours.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>>
>>> +1 from me
>>>
>>>
>>> Benjamim
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: integration test versioning policy?

[Brian Fox]

There should be a start and end range for the tests. These new ones
start in alpha-4-snapshot and end ]

On Thu, Nov 12, 2009 at 8:20 AM, Brett Porter  wrote:
> Hi,
>
> I ran the ITs against 3.0-alpha-3 and got a number of failures.
>
> Several of those are because they are fixed in 3.0-alpha-4 but marked to run 
> for all versions:
> - mng4412OfflineModeInPlugin
> - mng4433ForceParentSnapshotUpdate
>
> Before correcting anything I would like to check I understand the policy 
> correctly: should the versions be set to the versions for which the tests 
> should run 100%? Or is there a deliberate move to show failures where 
> something didn't work because of a regression (such as the ones above)?
>
> Thanks,
> Brett
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Use-case for multiple entries in the same section

[Brian Fox]

You should use the inherited element of the execution for that.

On Wed, Nov 11, 2009 at 4:43 AM, Stephen Connolly
 wrote:
> Just thought of a use-case for listing the same plugin twice in the
> one  section namely true and
> false
>
> OK, so it's somewhat specialised, and I have not had to use it myself,
> and you could probably work-around using a profile, but there is a use
> case.
>
> So what I would say is than in any one  section, the
> groupId:artifactId:inherited should be unique for each  in the
>  section
>
> -Stephen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: integration test versioning policy?

[Brett Porter]

On 13/11/2009, at 1:08 AM, Brian Fox wrote:

> There should be a start and end range for the tests. These new ones
> start in alpha-4-snapshot and end ]

ok, I've fixed these 2 and 4361 based on your other comment (though I haven't 
changed the JIRA version of that issue).

I also included all versions of 2.0 in the valid ranges since I believe these 
were working cases in earlier versions.

- Brett


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Use-case for multiple entries in the same section

[Stephen Connolly]

but what if you want to configure the defaults for all executions, and for
the child module executions, and you want the defaults for the child modules
to be different from the defaults for this module.

e.g.

turn skip on for this module, but off for child modules

2009/11/12 Brian Fox 

> You should use the inherited element of the execution for that.
>
> On Wed, Nov 11, 2009 at 4:43 AM, Stephen Connolly
>  wrote:
> > Just thought of a use-case for listing the same plugin twice in the
> > one  section namely true and
> > false
> >
> > OK, so it's somewhat specialised, and I have not had to use it myself,
> > and you could probably work-around using a profile, but there is a use
> > case.
> >
> > So what I would say is than in any one  section, the
> > groupId:artifactId:inherited should be unique for each  in the
> >  section
> >
> > -Stephen
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven 3.0-alpha-3

[John Casey]

+1, seems to run well here.

Benjamin Bentmann wrote:

Hi,

OK, here we go, another alpha release of Maven, for all those brave guys 
that want to take it for a test drive ;-)


We solved many issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719 



There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 



Staging repo:
https://repository.apache.org/content/repositories/maven-004/

Staged source and binary distros:
https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/ 



Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

+1 from me


Benjamim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven reporting impl version 2.0.4.3

[Mark Hobson]

Ah great, thanks :)

Mark

2009/11/12 Vincent Siveton :
> Hi Mark,
>
> It seems that we changed the groupid/artifactid in the past. Here the
> right link:
> http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/
>
> Cheers,
>
> Vincent
>
> 2009/11/12 Mark Hobson :
>> 2009/11/10 Vincent Siveton :
>>> The vote has passed with the following result :
>>> +1 Benjamin, Lukas, Dennis, Hervé, Vincent
>>>
>>> I will promote the artifacts to the central repo.
>>
>> Have the artifacts been promoted to central?  I can't see them:
>>
>> http://repo1.maven.org/maven2/org/apache/maven/shared/maven-reporting-impl/
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3

[Julien HENRY]

Another issue I have with Maven 3: trying to deploy an artifact with 
release:perform, I get the following error:

[INFO] [ERROR] Error deploying artifact: Unsupported Protocol: 'dav': Cannot 
find wagon which supports the requested protocol: dav -> [Help 1]
[INFO] [ERROR]

Is it a known issue?



- Message d'origine 
> De : Julien HENRY 
> À : Maven Developers List 
> Envoyé le : Mar 10 Novembre 2009, 15 h 56 min 15 s
> Objet : Re : [VOTE] Release Apache Maven 3.0-alpha-3
> 
> Hi,
> 
> I don't know if it is related to Maven 3, but I'm not able to update to a 
> newer 
> SNAPSHOT that is available in my corporate repository, even by using the -U 
> command line option. It seems Maven is not even asking the repository manager 
> for a new version.
> 
> What's wrong?
> 
> > mvn compile -U -X
> Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 17:04:41+0100)
> 
> [INFO] Scanning for projects...
> [DEBUG] Determining update check for snapshot 
> com.mycompany:project-parent:1-SNAPSHOT 
> (D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\maven-metadata-nexus.xml)
>  
> from nexus (http://nexus.mycompany.fr/content/groups/all)
> [DEBUG] Searching for: nexus.maven-metadata-nexus.xml.lastUpdated in 
> touchfile.
> [DEBUG] Reading resolution-state from: 
> D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties
> [DEBUG] project-parent: resolved to version 1-20091110.084931-1 from 
> repository 
> nexus
> 
> 
> In the Nexus repository I have:
> 
> project-parent-1-20091110.084931-1.pom
> project-parent-1-20091110.085551-2.pom
> 
> Removing 
> D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties
>  
> is a workaround, but I was expecting -U option to force SNAPSHOT update 
> whatever 
> is in the local repository...
> 
> Regards,
> 
> Julien
> 
> 
> 
> 
> - Message d'origine 
> > De : Benjamin Bentmann 
> > À : Maven Developers List 
> > Envoyé le : Lun 9 Novembre 2009, 17 h 39 min 09 s
> > Objet : [VOTE] Release Apache Maven 3.0-alpha-3
> > 
> > Hi,
> > 
> > OK, here we go, another alpha release of Maven, for all those brave guys 
> > that 
> > want to take it for a test drive ;-)
> > 
> > We solved many issues:
> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
> > 
> > There are still a couple of issues left in JIRA:
> > 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> > 
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-004/
> > 
> > Staged source and binary distros:
> > 
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
> > 
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> > 
> > Vote open for 72 hours.
> > 
> > [ ] +1
> > [ ] +0
> > [ ] -1
> > 
> > +1 from me
> > 
> > 
> > Benjamim
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org



 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Checkstyle ready for a 2.4 release?

[Mark Hobson]

I've upgraded maven-reporting-impl now that it has been released.

The only unresolved issue destined for 2.4 is now MCHECKSTYLE-123 [1].
 Can this be resolved quickly or shall we defer it until 2.5?

Cheers,

Mark

[1] http://jira.codehaus.org/browse/MCHECKSTYLE-123

2009/11/4 Mark Hobson :
> Okay, I'll wait for that release first, thanks.
>
> Unless anyone else objects in the meantime, I'll start a vote to
> release maven-checkstyle-plugin 2.4 after that.
>
> Cheers,
>
> Mark
>
> 2009/11/3 Vincent Siveton :
>> Hi,
>>
>> maven-reporting-impl:2.0.4.3 should be release to be able to write
>> single report, ie mvn checkstyle:checkstyle See MSHARED-120
>>
>> Cheers,
>>
>> Vincent
>>
>> 2009/11/3 Mark Hobson :
>>> Hi there,
>>>
>>> Has anyone got any objections to rolling a Checkstyle 2.4 release?
>>> The big addition in this version is MCHECKSTYLE-105 [1] which upgrades
>>> Checkstyle to 5.0, and thus is compatible with Java 5.  Several users
>>> have been using 2.4-SNAPSHOT successfully for a while now without
>>> problems, myself included.
>>>
>>> The remaining outstanding issue [2] is MCHECKSTYLE-123 [3].  Is there
>>> any rush to get this in 2.4 or can we defer this until 2.5?
>>>
>>> Cheers,
>>>
>>> Mark
>>>
>>> [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105
>>> [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336
>>> [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3

[Olivier Lamy]

wagon weddav is not any more included in the distrib.
You have to add it in your pom.

--
Olivier

2009/11/12 Julien HENRY :
> Another issue I have with Maven 3: trying to deploy an artifact with 
> release:perform, I get the following error:
>
> [INFO] [ERROR] Error deploying artifact: Unsupported Protocol: 'dav': Cannot 
> find wagon which supports the requested protocol: dav -> [Help 1]
> [INFO] [ERROR]
>
> Is it a known issue?
>
>
>
> - Message d'origine 
>> De : Julien HENRY 
>> À : Maven Developers List 
>> Envoyé le : Mar 10 Novembre 2009, 15 h 56 min 15 s
>> Objet : Re : [VOTE] Release Apache Maven 3.0-alpha-3
>>
>> Hi,
>>
>> I don't know if it is related to Maven 3, but I'm not able to update to a 
>> newer
>> SNAPSHOT that is available in my corporate repository, even by using the -U
>> command line option. It seems Maven is not even asking the repository manager
>> for a new version.
>>
>> What's wrong?
>>
>> > mvn compile -U -X
>> Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 17:04:41+0100)
>>
>> [INFO] Scanning for projects...
>> [DEBUG] Determining update check for snapshot
>> com.mycompany:project-parent:1-SNAPSHOT
>> (D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\maven-metadata-nexus.xml)
>> from nexus (http://nexus.mycompany.fr/content/groups/all)
>> [DEBUG] Searching for: nexus.maven-metadata-nexus.xml.lastUpdated in 
>> touchfile.
>> [DEBUG] Reading resolution-state from:
>> D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties
>> [DEBUG] project-parent: resolved to version 1-20091110.084931-1 from 
>> repository
>> nexus
>>
>>
>> In the Nexus repository I have:
>>
>> project-parent-1-20091110.084931-1.pom
>> project-parent-1-20091110.085551-2.pom
>>
>> Removing
>> D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties
>> is a workaround, but I was expecting -U option to force SNAPSHOT update 
>> whatever
>> is in the local repository...
>>
>> Regards,
>>
>> Julien
>>
>>
>>
>>
>> - Message d'origine 
>> > De : Benjamin Bentmann
>> > À : Maven Developers List
>> > Envoyé le : Lun 9 Novembre 2009, 17 h 39 min 09 s
>> > Objet : [VOTE] Release Apache Maven 3.0-alpha-3
>> >
>> > Hi,
>> >
>> > OK, here we go, another alpha release of Maven, for all those brave guys 
>> > that
>> > want to take it for a test drive ;-)
>> >
>> > We solved many issues:
>> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
>> >
>> > There are still a couple of issues left in JIRA:
>> >
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/maven-004/
>> >
>> > Staged source and binary distros:
>> >
>> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
>> >
>> > Guide to testing staged releases:
>> > http://maven.apache.org/guides/development/guide-testing-releases.html
>> >
>> > Vote open for 72 hours.
>> >
>> > [ ] +1
>> > [ ] +0
>> > [ ] -1
>> >
>> > +1 from me
>> >
>> >
>> > Benjamim
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>



-- 
Olivier

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Checkstyle ready for a 2.4 release?

[Olivier Lamy]

Hi,
Move it to 2.5.
I wanted to work on some refactoring on the plugin.
But the best is to do it after the release :-)

--
Olivier

2009/11/12 Mark Hobson :
> I've upgraded maven-reporting-impl now that it has been released.
>
> The only unresolved issue destined for 2.4 is now MCHECKSTYLE-123 [1].
>  Can this be resolved quickly or shall we defer it until 2.5?
>
> Cheers,
>
> Mark
>
> [1] http://jira.codehaus.org/browse/MCHECKSTYLE-123
>
> 2009/11/4 Mark Hobson :
>> Okay, I'll wait for that release first, thanks.
>>
>> Unless anyone else objects in the meantime, I'll start a vote to
>> release maven-checkstyle-plugin 2.4 after that.
>>
>> Cheers,
>>
>> Mark
>>
>> 2009/11/3 Vincent Siveton :
>>> Hi,
>>>
>>> maven-reporting-impl:2.0.4.3 should be release to be able to write
>>> single report, ie mvn checkstyle:checkstyle See MSHARED-120
>>>
>>> Cheers,
>>>
>>> Vincent
>>>
>>> 2009/11/3 Mark Hobson :
 Hi there,

 Has anyone got any objections to rolling a Checkstyle 2.4 release?
 The big addition in this version is MCHECKSTYLE-105 [1] which upgrades
 Checkstyle to 5.0, and thus is compatible with Java 5.  Several users
 have been using 2.4-SNAPSHOT successfully for a while now without
 problems, myself included.

 The remaining outstanding issue [2] is MCHECKSTYLE-123 [3].  Is there
 any rush to get this in 2.4 or can we defer this until 2.5?

 Cheers,

 Mark

 [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105
 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336
 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org


>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>



-- 
Olivier

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re : Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3

[Julien HENRY]

OK, thanks



- Message d'origine 
> De : Olivier Lamy 
> À : Maven Developers List 
> Envoyé le : Jeu 12 Novembre 2009, 16 h 58 min 00 s
> Objet : Re: Re : Re : [VOTE] Release Apache Maven 3.0-alpha-3
> 
> wagon weddav is not any more included in the distrib.
> You have to add it in your pom.
> 
> --
> Olivier
> 
> 2009/11/12 Julien HENRY :
> > Another issue I have with Maven 3: trying to deploy an artifact with 
> release:perform, I get the following error:
> >
> > [INFO] [ERROR] Error deploying artifact: Unsupported Protocol: 'dav': 
> > Cannot 
> find wagon which supports the requested protocol: dav -> [Help 1]
> > [INFO] [ERROR]
> >
> > Is it a known issue?
> >
> >
> >
> > - Message d'origine 
> >> De : Julien HENRY 
> >> À : Maven Developers List 
> >> Envoyé le : Mar 10 Novembre 2009, 15 h 56 min 15 s
> >> Objet : Re : [VOTE] Release Apache Maven 3.0-alpha-3
> >>
> >> Hi,
> >>
> >> I don't know if it is related to Maven 3, but I'm not able to update to a 
> newer
> >> SNAPSHOT that is available in my corporate repository, even by using the -U
> >> command line option. It seems Maven is not even asking the repository 
> >> manager
> >> for a new version.
> >>
> >> What's wrong?
> >>
> >> > mvn compile -U -X
> >> Apache Maven 3.0-alpha-3 (r834122; 2009-11-09 17:04:41+0100)
> >>
> >> [INFO] Scanning for projects...
> >> [DEBUG] Determining update check for snapshot
> >> com.mycompany:project-parent:1-SNAPSHOT
> >> 
> (D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\maven-metadata-nexus.xml)
> >> from nexus (http://nexus.mycompany.fr/content/groups/all)
> >> [DEBUG] Searching for: nexus.maven-metadata-nexus.xml.lastUpdated in 
> touchfile.
> >> [DEBUG] Reading resolution-state from:
> >> 
> D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties
> >> [DEBUG] project-parent: resolved to version 1-20091110.084931-1 from 
> repository
> >> nexus
> >>
> >>
> >> In the Nexus repository I have:
> >>
> >> project-parent-1-20091110.084931-1.pom
> >> project-parent-1-20091110.085551-2.pom
> >>
> >> Removing
> >> 
> D:\.m2\repository\com\mycompany\project-parent\1-SNAPSHOT\resolver-status.properties
> >> is a workaround, but I was expecting -U option to force SNAPSHOT update 
> whatever
> >> is in the local repository...
> >>
> >> Regards,
> >>
> >> Julien
> >>
> >>
> >>
> >>
> >> - Message d'origine 
> >> > De : Benjamin Bentmann
> >> > À : Maven Developers List
> >> > Envoyé le : Lun 9 Novembre 2009, 17 h 39 min 09 s
> >> > Objet : [VOTE] Release Apache Maven 3.0-alpha-3
> >> >
> >> > Hi,
> >> >
> >> > OK, here we go, another alpha release of Maven, for all those brave guys 
> that
> >> > want to take it for a test drive ;-)
> >> >
> >> > We solved many issues:
> >> > 
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
> >> >
> >> > There are still a couple of issues left in JIRA:
> >> >
> >> 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
> >> >
> >> > Staging repo:
> >> > https://repository.apache.org/content/repositories/maven-004/
> >> >
> >> > Staged source and binary distros:
> >> >
> >> 
> https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0-alpha-3/
> >> >
> >> > Guide to testing staged releases:
> >> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >> >
> >> > Vote open for 72 hours.
> >> >
> >> > [ ] +1
> >> > [ ] +0
> >> > [ ] -1
> >> >
> >> > +1 from me
> >> >
> >> >
> >> > Benjamim
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: dev-h...@maven.apache.org
> >>
> >>
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> 
> 
> 
> -- 
> Olivier
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.0-alpha-3

[Hervé BOUTEMY]

+1

Hervé

Le lundi 09 novembre 2009, Benjamin Bentmann a écrit :
> Hi,
> 
> OK, here we go, another alpha release of Maven, for all those brave guys
> that want to take it for a test drive ;-)
> 
> We solved many issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14
> 719
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&st
> atus=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-004/
> 
> Staged source and binary distros:
> https://repository.apache.org/content/repositories/maven-004/org/apache/mav
> en/apache-maven/3.0-alpha-3/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> +1 from me
> 
> 
> Benjamim
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Checkstyle ready for a 2.4 release?

[Mark Hobson]

Great, thanks Olivier.

I'll start the vote for 2.4.

Cheers,

Mark

2009/11/12 Olivier Lamy :
> Hi,
> Move it to 2.5.
> I wanted to work on some refactoring on the plugin.
> But the best is to do it after the release :-)
>
> --
> Olivier
>
> 2009/11/12 Mark Hobson :
>> I've upgraded maven-reporting-impl now that it has been released.
>>
>> The only unresolved issue destined for 2.4 is now MCHECKSTYLE-123 [1].
>>  Can this be resolved quickly or shall we defer it until 2.5?
>>
>> Cheers,
>>
>> Mark
>>
>> [1] http://jira.codehaus.org/browse/MCHECKSTYLE-123
>>
>> 2009/11/4 Mark Hobson :
>>> Okay, I'll wait for that release first, thanks.
>>>
>>> Unless anyone else objects in the meantime, I'll start a vote to
>>> release maven-checkstyle-plugin 2.4 after that.
>>>
>>> Cheers,
>>>
>>> Mark
>>>
>>> 2009/11/3 Vincent Siveton :
 Hi,

 maven-reporting-impl:2.0.4.3 should be release to be able to write
 single report, ie mvn checkstyle:checkstyle See MSHARED-120

 Cheers,

 Vincent

 2009/11/3 Mark Hobson :
> Hi there,
>
> Has anyone got any objections to rolling a Checkstyle 2.4 release?
> The big addition in this version is MCHECKSTYLE-105 [1] which upgrades
> Checkstyle to 5.0, and thus is compatible with Java 5.  Several users
> have been using 2.4-SNAPSHOT successfully for a while now without
> problems, myself included.
>
> The remaining outstanding issue [2] is MCHECKSTYLE-123 [3].  Is there
> any rush to get this in 2.4 or can we defer this until 2.5?
>
> Cheers,
>
> Mark
>
> [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105
> [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336
> [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org


>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
>
> --
> Olivier
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[VOTE] Release Maven Checkstyle plugin version 2.4

[Mark Hobson]

Hi,

The big new feature in this release is an upgrade to Checkstyle 5.0,
which brings Java 5 compatibility.

We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&version=15336

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-001/

Staging site:
http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/
(Wait for sync, or use proxy)

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Cheers,

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: endorsing: ToolChain thing or compiler/surefire plugin thing or ....

[Daniel Kulp]

Just to follow up on this, it looks like the two main options are:

1) Add an "endorsed" scope.   What would be involved with that?   What would 
happen when a 2.0.10/2.2.1 maven version hits such a scope?This seems to 
be a "maven core" thing with updates needed to a bunch of core things.   Not a 
BAD thing, especially for 3.0 or something, but increases the complexity.

2) maven-endorsed-plugin - similar to the toolchains thing, but provides 
special endorsing capabilities.  Would be done in parts.   The plugin plus 
updates to surefire and compiler (and others that may need it).


(2) can definitely be made to work with existing versions of maven, but (1) 
definitely seems "cleaner".   (1) would also allow endorsements to be handled 
from transitive deps, although I'm not sure if that's a good thing or not.  
:-)  

Anyway, what are peoples thoughts?   I think after thanksgiving, I may need to 
start working on bits of this so I'd like to get peoples thoughts and ideas 
before then.

Dan




On Mon November 9 2009 4:55:17 pm Daniel Kulp wrote:
> While at ApacheCon last week, I talked to Jarek Gawor a bit and then
>  followed up with a quick conversation with Brett about a problem that is
>  soon going to hit CXF/Axis2/Geronimo.
> 
> Basically, we're going to need a mechanism to easily "endorse" a few api
>  jars when we call javac and when surefire runs. I'm ok with limiting
>  the endorsing to when those plugins are in their "fork" mode.  There are a
>  few options that could be pursued:
> 
> 1) Require all developers to drop some jars in jre/lib/endorsed.   That
>  really sucks.  Not exactly viable, IMO.
> 
> 2) Require all devs to copy the jars someplace and add
>  -Djava.endorsed.dirs=.. to their MAVEN_OPTS.Also sucks.
> 
> 3) In all modules, configure dependency:copy to copy the artifacts into a
>  dir in target, then add the -D thing as system flags for compiler plugin
>  and surefire.  This is better than (2) as it can be all automatic in the
>  poms, but it's a ton of configuration if dealing with a lot of poms and
>  projects and such.
> 
> 4) Add some mechanism to compiler and surefire (and maybe others) to do
>  some of (3) automatically.   I'm thinking something like:
> 
> 
>org.apache.maven.plugins
>maven-compiler-plugin
>
> 
> 
>   ...
>   ...
>   
> 
> 
>
> 
> 
> and similar configuration for surefire.   Maybe make  optional and
>  it would pick up a version from a dependency.
> 
> 5) Maybe some extension to the ToolChains stuff (which I don't know enough
> about, need to dig further if this is viable) to handle this.
> 
> Anyway, does anyone have any other thoughts?
> 

-- 
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: endorsing: ToolChain thing or compiler/surefire plugin thing or ....

[Paul Benedict]

Is it possible to add endorsed libraries programatically? I thought
the JDK grabbed all its endorsements from jdk_home\lib\ext

Paul

On Thu, Nov 12, 2009 at 12:48 PM, Daniel Kulp  wrote:
>
> Just to follow up on this, it looks like the two main options are:
>
> 1) Add an "endorsed" scope.   What would be involved with that?   What would
> happen when a 2.0.10/2.2.1 maven version hits such a scope?    This seems to
> be a "maven core" thing with updates needed to a bunch of core things.   Not a
> BAD thing, especially for 3.0 or something, but increases the complexity.
>
> 2) maven-endorsed-plugin - similar to the toolchains thing, but provides
> special endorsing capabilities.  Would be done in parts.   The plugin plus
> updates to surefire and compiler (and others that may need it).
>
>
> (2) can definitely be made to work with existing versions of maven, but (1)
> definitely seems "cleaner".   (1) would also allow endorsements to be handled
> from transitive deps, although I'm not sure if that's a good thing or not.
> :-)
>
> Anyway, what are peoples thoughts?   I think after thanksgiving, I may need to
> start working on bits of this so I'd like to get peoples thoughts and ideas
> before then.
>
> Dan
>
>
>
>
> On Mon November 9 2009 4:55:17 pm Daniel Kulp wrote:
>> While at ApacheCon last week, I talked to Jarek Gawor a bit and then
>>  followed up with a quick conversation with Brett about a problem that is
>>  soon going to hit CXF/Axis2/Geronimo.
>>
>> Basically, we're going to need a mechanism to easily "endorse" a few api
>>  jars when we call javac and when surefire runs.     I'm ok with limiting
>>  the endorsing to when those plugins are in their "fork" mode.  There are a
>>  few options that could be pursued:
>>
>> 1) Require all developers to drop some jars in jre/lib/endorsed.   That
>>  really sucks.  Not exactly viable, IMO.
>>
>> 2) Require all devs to copy the jars someplace and add
>>  -Djava.endorsed.dirs=.. to their MAVEN_OPTS.    Also sucks.
>>
>> 3) In all modules, configure dependency:copy to copy the artifacts into a
>>  dir in target, then add the -D thing as system flags for compiler plugin
>>  and surefire.  This is better than (2) as it can be all automatic in the
>>  poms, but it's a ton of configuration if dealing with a lot of poms and
>>  projects and such.
>>
>> 4) Add some mechanism to compiler and surefire (and maybe others) to do
>>  some of (3) automatically.   I'm thinking something like:
>>
>> 
>>        org.apache.maven.plugins
>>        maven-compiler-plugin
>>        
>>             
>>                 
>>                       ...
>>                       ...
>>                       
>>                 
>>             
>>        
>> 
>>
>> and similar configuration for surefire.   Maybe make  optional and
>>  it would pick up a version from a dependency.
>>
>> 5) Maybe some extension to the ToolChains stuff (which I don't know enough
>> about, need to dig further if this is viable) to handle this.
>>
>> Anyway, does anyone have any other thoughts?
>>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.dankulp.com/blog
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: endorsing: ToolChain thing or compiler/surefire plugin thing or ....

[Daniel Kulp]

On Thu November 12 2009 2:22:51 pm Paul Benedict wrote:
> Is it possible to add endorsed libraries programatically? I thought
> the JDK grabbed all its endorsements from jdk_home\lib\ext

When you fork a jvm (javac fork or surefire set to fork), you can specify a 
system property of other places to look.   Thus, then endorsed stuff would 
only apply when those are set to fork.

Dan


> 
> Paul
> 
> On Thu, Nov 12, 2009 at 12:48 PM, Daniel Kulp  wrote:
> > Just to follow up on this, it looks like the two main options are:
> >
> > 1) Add an "endorsed" scope.   What would be involved with that?   What
> > would happen when a 2.0.10/2.2.1 maven version hits such a scope?This
> > seems to be a "maven core" thing with updates needed to a bunch of core
> > things.   Not a BAD thing, especially for 3.0 or something, but increases
> > the complexity.
> >
> > 2) maven-endorsed-plugin - similar to the toolchains thing, but provides
> > special endorsing capabilities.  Would be done in parts.   The plugin
> > plus updates to surefire and compiler (and others that may need it).
> >
> >
> > (2) can definitely be made to work with existing versions of maven, but
> > (1) definitely seems "cleaner".   (1) would also allow endorsements to be
> > handled from transitive deps, although I'm not sure if that's a good
> > thing or not.
> >
> > :-)
> >
> > Anyway, what are peoples thoughts?   I think after thanksgiving, I may
> > need to start working on bits of this so I'd like to get peoples thoughts
> > and ideas before then.
> >
> > Dan
> >
> > On Mon November 9 2009 4:55:17 pm Daniel Kulp wrote:
> >> While at ApacheCon last week, I talked to Jarek Gawor a bit and then
> >>  followed up with a quick conversation with Brett about a problem that
> >> is soon going to hit CXF/Axis2/Geronimo.
> >>
> >> Basically, we're going to need a mechanism to easily "endorse" a few api
> >>  jars when we call javac and when surefire runs. I'm ok with
> >> limiting the endorsing to when those plugins are in their "fork" mode.
> >>  There are a few options that could be pursued:
> >>
> >> 1) Require all developers to drop some jars in jre/lib/endorsed.   That
> >>  really sucks.  Not exactly viable, IMO.
> >>
> >> 2) Require all devs to copy the jars someplace and add
> >>  -Djava.endorsed.dirs=.. to their MAVEN_OPTS.Also sucks.
> >>
> >> 3) In all modules, configure dependency:copy to copy the artifacts into
> >> a dir in target, then add the -D thing as system flags for compiler
> >> plugin and surefire.  This is better than (2) as it can be all automatic
> >> in the poms, but it's a ton of configuration if dealing with a lot of
> >> poms and projects and such.
> >>
> >> 4) Add some mechanism to compiler and surefire (and maybe others) to do
> >>  some of (3) automatically.   I'm thinking something like:
> >>
> >> 
> >>org.apache.maven.plugins
> >>maven-compiler-plugin
> >>
> >> 
> >> 
> >>   ...
> >>   ...
> >>   
> >> 
> >> 
> >>
> >> 
> >>
> >> and similar configuration for surefire.   Maybe make  optional
> >> and it would pick up a version from a dependency.
> >>
> >> 5) Maybe some extension to the ToolChains stuff (which I don't know
> >> enough about, need to dig further if this is viable) to handle this.
> >>
> >> Anyway, does anyone have any other thoughts?
> >
> > --
> > Daniel Kulp
> > dk...@apache.org
> > http://www.dankulp.com/blog
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

-- 
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: endorsing: ToolChain thing or compiler/surefire plugin thing or ....

[Paul Benedict]

Yes, then it is probably appropriate for the Maven Compiler plugin to
support endorsed libraries. I can't remember if it always forks, but
if forking isn't specified, an error should be thrown when endorsed
libraries are used.

Paul

On Thu, Nov 12, 2009 at 3:19 PM, Daniel Kulp  wrote:
> On Thu November 12 2009 2:22:51 pm Paul Benedict wrote:
>> Is it possible to add endorsed libraries programatically? I thought
>> the JDK grabbed all its endorsements from jdk_home\lib\ext
>
> When you fork a jvm (javac fork or surefire set to fork), you can specify a
> system property of other places to look.   Thus, then endorsed stuff would
> only apply when those are set to fork.
>
> Dan
>
>
>>
>> Paul
>>
>> On Thu, Nov 12, 2009 at 12:48 PM, Daniel Kulp  wrote:
>> > Just to follow up on this, it looks like the two main options are:
>> >
>> > 1) Add an "endorsed" scope.   What would be involved with that?   What
>> > would happen when a 2.0.10/2.2.1 maven version hits such a scope?    This
>> > seems to be a "maven core" thing with updates needed to a bunch of core
>> > things.   Not a BAD thing, especially for 3.0 or something, but increases
>> > the complexity.
>> >
>> > 2) maven-endorsed-plugin - similar to the toolchains thing, but provides
>> > special endorsing capabilities.  Would be done in parts.   The plugin
>> > plus updates to surefire and compiler (and others that may need it).
>> >
>> >
>> > (2) can definitely be made to work with existing versions of maven, but
>> > (1) definitely seems "cleaner".   (1) would also allow endorsements to be
>> > handled from transitive deps, although I'm not sure if that's a good
>> > thing or not.
>> >
>> > :-)
>> >
>> > Anyway, what are peoples thoughts?   I think after thanksgiving, I may
>> > need to start working on bits of this so I'd like to get peoples thoughts
>> > and ideas before then.
>> >
>> > Dan
>> >
>> > On Mon November 9 2009 4:55:17 pm Daniel Kulp wrote:
>> >> While at ApacheCon last week, I talked to Jarek Gawor a bit and then
>> >>  followed up with a quick conversation with Brett about a problem that
>> >> is soon going to hit CXF/Axis2/Geronimo.
>> >>
>> >> Basically, we're going to need a mechanism to easily "endorse" a few api
>> >>  jars when we call javac and when surefire runs.     I'm ok with
>> >> limiting the endorsing to when those plugins are in their "fork" mode.
>> >>  There are a few options that could be pursued:
>> >>
>> >> 1) Require all developers to drop some jars in jre/lib/endorsed.   That
>> >>  really sucks.  Not exactly viable, IMO.
>> >>
>> >> 2) Require all devs to copy the jars someplace and add
>> >>  -Djava.endorsed.dirs=.. to their MAVEN_OPTS.    Also sucks.
>> >>
>> >> 3) In all modules, configure dependency:copy to copy the artifacts into
>> >> a dir in target, then add the -D thing as system flags for compiler
>> >> plugin and surefire.  This is better than (2) as it can be all automatic
>> >> in the poms, but it's a ton of configuration if dealing with a lot of
>> >> poms and projects and such.
>> >>
>> >> 4) Add some mechanism to compiler and surefire (and maybe others) to do
>> >>  some of (3) automatically.   I'm thinking something like:
>> >>
>> >> 
>> >>        org.apache.maven.plugins
>> >>        maven-compiler-plugin
>> >>        
>> >>             
>> >>                 
>> >>                       ...
>> >>                       ...
>> >>                       
>> >>                 
>> >>             
>> >>        
>> >> 
>> >>
>> >> and similar configuration for surefire.   Maybe make  optional
>> >> and it would pick up a version from a dependency.
>> >>
>> >> 5) Maybe some extension to the ToolChains stuff (which I don't know
>> >> enough about, need to dig further if this is viable) to handle this.
>> >>
>> >> Anyway, does anyone have any other thoughts?
>> >
>> > --
>> > Daniel Kulp
>> > dk...@apache.org
>> > http://www.dankulp.com/blog
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.dankulp.com/blog
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[ANN] Apache Source-Release Assembly Descriptor 1.0.2 Released

[Benjamin Bentmann]

The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.2.

This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build output) that
are the subject of an ASF release vote.

The new version of the descriptor fixes the erroneous exclusion of some
file types like IDE files from the source archive even if those files 
are located in the src/ directory tree of a project, i.e. denote actual 
project sources (e.g. required for unit testing).


http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/

This new descriptor will eventually be incorporated into the Apache 
Parent POM. If you want to try out the source-release descriptor in the 
meantime, you can include a configuration like the following:



  

  maven-assembly-plugin
  2.2-beta-4

  

  org.apache.apache.resources

apache-source-release-assembly-descriptor
  1.0.2


  
  org.codehaus.plexus
  plexus-utils
  2.0.1

  

  

  source-release
  package
  
single
  
  

  source-release

gnu
true
  

  

  


Enjoy,

The Maven Team


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Release Apache Maven 3.0-alpha-3

[Benjamin Bentmann]

Hi,

The vote has passed with the following result:

+1 (binding): Benjamin Bentmann, Arnaud Héritier, Olivier Lamy, Jason 
van Zyl, Stéphane Nicoll, Dan Fabulich, Brian Fox, Brett Porter, Vincent 
Siveton, John Casey, Hervé Boutemy


+1 (non-binding): Stephen Connolly, Stuart McCulloch, Paul Benedict, 
Tony Chemit, Kristian Rosenvold, Paul Gier


+0: Henri Gomez

I will promote the artifacts to the central repository and continue with 
the release. Thanks for all the feedback!



Benjamin

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Site Update for Maven 3.0-alpha-3

[Benjamin Bentmann]

Hi,

I noticed that we didn't mention previous alphas of 3.0 on the Maven 
site. How do we want to go about that with alpha-3?


To attract more testers, I think we should have this alpha listed in the 
download section. E.g. some structure like


* Stable Releases
  2.2.1
  2.1.0
  2.0.10
* Alpha/Beta Releases
  3.0-alpha-3
* Previous Releases

WDYT?


Benjamin

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Site Update for Maven 3.0-alpha-3

[Jason van Zyl]

Can't hurt. I have no problem promoting alpha-3. It's the best Maven  
that's existed. I say go for it.


On 2009-11-13, at 12:59 AM, Benjamin Bentmann wrote:


Hi,

I noticed that we didn't mention previous alphas of 3.0 on the Maven  
site. How do we want to go about that with alpha-3?


To attract more testers, I think we should have this alpha listed in  
the download section. E.g. some structure like


* Stable Releases
 2.2.1
 2.1.0
 2.0.10
* Alpha/Beta Releases
 3.0-alpha-3
* Previous Releases

WDYT?


Benjamin

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Site Update for Maven 3.0-alpha-3

[Brett Porter]

On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote:

> Hi,
> 
> I noticed that we didn't mention previous alphas of 3.0 on the Maven site. 
> How do we want to go about that with alpha-3?
> 
> To attract more testers, I think we should have this alpha listed in the 
> download section. E.g. some structure like
> 
> * Stable Releases
>  2.2.1
>  2.1.0
>  2.0.10
> * Alpha/Beta Releases
>  3.0-alpha-3
> * Previous Releases
> 
> WDYT?

+1, though I think we can remove 2.1.0 from the list as it is superceded by 
2.2.1.

When I started trying to automate more of the release process for 2.0.11, I 
already did this (moved to a branch now):

http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808

There was general support, but I also split the release notes which raised some 
concerns. And then I ran out of spare time with my holiday, etc. :)

I believe consensus was:
- use JIRA as the authoritative source for release notes
- support the split structure provided above for posting online (later moving 
to pull information from JIRA)
- also produce an aggregated release notes (I believe for a series, not all 
releases), which can be done automatically

So, options:
- merge down just the bits that split into stable / preview versions
- fix the aggregated release notes and merge the lot

Thoughts?

I'll update the branch for current versions.

- Brett
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[jira] Subscription: Design & Best Practices

[jira]

Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist

Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-2584Rebuild on pom change
http://jira.codehaus.org/browse/MNG-2584
MNG-139 server definitions should be reusable - review use of repository IDs
http://jira.codehaus.org/browse/MNG-139
MNG-2125[doc] when and how to define plugins in a pom
http://jira.codehaus.org/browse/MNG-2125
MNG-474 performance improvement for forked lifecycles
http://jira.codehaus.org/browse/MNG-474
MNG-1381best practices: testing strategies
http://jira.codehaus.org/browse/MNG-1381
MNG-1563how to write integration tests
http://jira.codehaus.org/browse/MNG-1563
MNG-2381improved control over the repositories in the POM
http://jira.codehaus.org/browse/MNG-2381
MNG-1950Ability to introduce new lifecycles phases
http://jira.codehaus.org/browse/MNG-1950
MNG-1931add a reportingManagement section
http://jira.codehaus.org/browse/MNG-1931
MNG-1468best practices: version management in multi project builds
http://jira.codehaus.org/browse/MNG-1468
MNG-1885Uniquely identify modules by module name and version number
http://jira.codehaus.org/browse/MNG-1885
MNG-647 Allow Maven 2 to be monitored using JMX.
http://jira.codehaus.org/browse/MNG-647
MNG-416 best practices:  multiple profile deployments
http://jira.codehaus.org/browse/MNG-416
MNG-367 best practices: multi-user installation
http://jira.codehaus.org/browse/MNG-367
MNG-125 guarded mojo execution
http://jira.codehaus.org/browse/MNG-125
MNG-1569Make build process info read-only to mojos, and provide mechanism 
for explicit out-params for mojos to declare
http://jira.codehaus.org/browse/MNG-1569
MNG-41  best practices: site management
http://jira.codehaus.org/browse/MNG-41
MNG-657 possible chicken and egg problem with extensions
http://jira.codehaus.org/browse/MNG-657
MNG-1867deprecate system scope, analyse other use cases
http://jira.codehaus.org/browse/MNG-1867
MNG-1441Starting thinking about a proper distributed repository mechanism a 
la CPAN
http://jira.codehaus.org/browse/MNG-1441
MNG-868 Use uniform format for  and other tags
http://jira.codehaus.org/browse/MNG-868
MNG-1423best practices: setting up multi-module build
http://jira.codehaus.org/browse/MNG-1423
MNG-1439Organization Object Model (OOM) 
http://jira.codehaus.org/browse/MNG-1439
MNG-1440Developer Object Model (DOM)
http://jira.codehaus.org/browse/MNG-1440
MNG-1463best practices: plugin inheritance for a multi project build
http://jira.codehaus.org/browse/MNG-1463
MNG-1425best practices: the location of configuration files vs resources
http://jira.codehaus.org/browse/MNG-1425

You may edit this subscription at:
http://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341&filterId=11471

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Site Update for Maven 3.0-alpha-3

[Brett Porter]

On 13/11/2009, at 11:28 AM, Brett Porter wrote:

> 
> 
> On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote:
> 
>> Hi,
>> 
>> I noticed that we didn't mention previous alphas of 3.0 on the Maven site. 
>> How do we want to go about that with alpha-3?
>> 
>> To attract more testers, I think we should have this alpha listed in the 
>> download section. E.g. some structure like
>> 
>> * Stable Releases
>> 2.2.1
>> 2.1.0
>> 2.0.10
>> * Alpha/Beta Releases
>> 3.0-alpha-3
>> * Previous Releases
>> 
>> WDYT?
> 
> +1, though I think we can remove 2.1.0 from the list as it is superceded by 
> 2.2.1.
> 
> When I started trying to automate more of the release process for 2.0.11, I 
> already did this (moved to a branch now):
> 
> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808
> 
> There was general support, but I also split the release notes which raised 
> some concerns. And then I ran out of spare time with my holiday, etc. :)
> 
> I believe consensus was:
> - use JIRA as the authoritative source for release notes
> - support the split structure provided above for posting online (later moving 
> to pull information from JIRA)
> - also produce an aggregated release notes (I believe for a series, not all 
> releases), which can be done automatically
> 
> So, options:
> - merge down just the bits that split into stable / preview versions
> - fix the aggregated release notes and merge the lot
> 
> Thoughts?
> 
> I'll update the branch for current versions.

I've updated the branch here: 
http://svn.apache.org/repos/asf/maven/site/branches/release-presentation

What would be required to add a new release is illustrated here: 
http://svn.apache.org/repos/asf/maven/site/branches/release-presentation/README.txt

I've staged a sample site here: 
http://people.apache.org/~brett/staged-maven-site/

Alpha 3 is on the download page only, and release notes are drafted: 
http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html

The aggregated release notes are here: 
http://people.apache.org/~brett/staged-maven-site/release-notes-all.html

Cheers,
Brett



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Checkstyle plugin version 2.4

[nicolas de loof]

+1

2009/11/12 Mark Hobson 

> Hi,
>
> The big new feature in this release is an upgrade to Checkstyle 5.0,
> which brings Java 5 compatibility.
>
> We solved 6 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&version=15336
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-001/
>
> Staging site:
> http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/
> (Wait for sync, or use proxy)
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers,
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Site Update for Maven 3.0-alpha-3

[Stevo Slavić]

IMO 2.1.0 should stay as it is, if I'm not mistaken, most recent stable
release of maven which is compatible with Java 1.4. When maven 2.2.1 is
configured as default external maven installation m2eclipse 0.9.9 refuses to
build projects (like maven core plugins) which still require Java 1.4. Maybe
2.0.10 could be removed instead.

Regards,
Stevo.

On Fri, Nov 13, 2009 at 5:25 AM, Brett Porter  wrote:

>
> On 13/11/2009, at 11:28 AM, Brett Porter wrote:
>
> >
> >
> > On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote:
> >
> >> Hi,
> >>
> >> I noticed that we didn't mention previous alphas of 3.0 on the Maven
> site. How do we want to go about that with alpha-3?
> >>
> >> To attract more testers, I think we should have this alpha listed in the
> download section. E.g. some structure like
> >>
> >> * Stable Releases
> >> 2.2.1
> >> 2.1.0
> >> 2.0.10
> >> * Alpha/Beta Releases
> >> 3.0-alpha-3
> >> * Previous Releases
> >>
> >> WDYT?
> >
> > +1, though I think we can remove 2.1.0 from the list as it is superceded
> by 2.2.1.
> >
> > When I started trying to automate more of the release process for 2.0.11,
> I already did this (moved to a branch now):
> >
> >
> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808
> >
> > There was general support, but I also split the release notes which
> raised some concerns. And then I ran out of spare time with my holiday, etc.
> :)
> >
> > I believe consensus was:
> > - use JIRA as the authoritative source for release notes
> > - support the split structure provided above for posting online (later
> moving to pull information from JIRA)
> > - also produce an aggregated release notes (I believe for a series, not
> all releases), which can be done automatically
> >
> > So, options:
> > - merge down just the bits that split into stable / preview versions
> > - fix the aggregated release notes and merge the lot
> >
> > Thoughts?
> >
> > I'll update the branch for current versions.
>
> I've updated the branch here:
> http://svn.apache.org/repos/asf/maven/site/branches/release-presentation
>
> What would be required to add a new release is illustrated here:
> http://svn.apache.org/repos/asf/maven/site/branches/release-presentation/README.txt
>
> I've staged a sample site here:
> http://people.apache.org/~brett/staged-maven-site/
>
> Alpha 3 is on the download page only, and release notes are drafted:
> http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html
>
> The aggregated release notes are here:
> http://people.apache.org/~brett/staged-maven-site/release-notes-all.html
>
> Cheers,
> Brett
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>