Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)

[Olivier Lamy]

+1

2013/6/1 Jason van Zyl :
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-046/
>
> Staged distribution:
> https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/
>
> Staged Site:
> http://maven.apache.org/ref/3.1.0-alpha-1
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> First, the taking in of scattered particulars under one Idea,
> so that everyone understands what is being talked about ... Second,
> the separation of the Idea into parts, by dividing it at the joints,
> as nature directs, not breaking any limb in half as a bad carver might.
>
>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [Fluido Skin] Downgrading Bootstrap back to 2.2

[Olivier Lamy]

as no response/complain you can assume it's ok :-)

2013/6/8 Michael-O <1983-01...@gmx.net>:
> Hi folks,
>
> I recently proposed in MSKINS-80 to downgrade to 2.2.x for two reasons:
>
> 1. No one has updated the site.vm and custom.css to Bootstrap 2.3 or does
> not yet knows the real changes in the model
> 2. Such a change must not happen in a patch version
>
> But haven't received any feedback -- neither positive nor negative.
> I'd like to take up on this and perform the downgrade. Site rendering will
> work as expected again. Additionally, I have made several improvements to
> the CSS and rendering stuff locally in my parent project which I would like
> to merge back to the plugin itself and bring it on par with the other site
> plugins.
>
> Let's postpone Bootstrap 2.3.x to Fluido Skin 1.4.x.
>
> Objections, opinions?
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: CMS appears down

[Olivier Lamy]

I think there are currently some os upgrade
see https://twitter.com/infrabot/status/343347807542968320
and email send to committer@


2013/6/9 Jason van Zyl :
> I can't get https://cms.apache.org/maven/publish to load? Anyone know how to 
> kick it?
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> You are never dedicated to something you have complete confidence in.
> No one is fanatically shouting that the sun is going to rise tomorrow.
> They know it is going to rise tomorrow. When people are fanatically
> dedicated to political or religious faiths or any other kind of
> dogmas or goals, it's always because these dogmas or
> goals are in doubt.
>
>   -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Maven Surefire Plugin version 2.15

[Olivier Lamy]

+1


2013/6/7 Andreas Gudian :
> Hi,
>
> This is my first release, so please check carefully what I may have missed
> :).
>
> We solved 16 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19174
>
> This is the first release that does not support JVM versions prior 1.5 to
> be forked.
>
> There are still lots of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-075
> https://repository.apache.org/content/repositories/maven-075/org/apache/maven/plugins/maven-surefire-plugin/2.15/maven-surefire-plugin-2.15-sources.jar
> https://repository.apache.org/content/repositories/maven-075/org/apache/maven/plugins/maven-failsafe-plugin/2.15/maven-failsafe-plugin-2.15-sources.jar
> Source: https://git-wip-us.apache.org/repos/asf/maven-surefire.git tag
> surefire-2.15
>
> Staging site:
> http://maven.apache.org/surefire-archives/maven-surefire-2.15/maven-surefire-plugin/index.html
> http://maven.apache.org/surefire-archives/maven-surefire-2.15/maven-failsafe-plugin/index.html
> http://maven.apache.org/surefire-archives/maven-surefire-2.15/maven-surefire-report-plugin/index.html
>
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

javadoc updater tool

[Olivier Lamy]

Hi,
I did that for our all javadocs (normally applied on all :-) )
See: 
http://www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html#jpi-upt

Cheers
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: JavadocFixTool integration with Javadoc plugin?

[Olivier Lamy]

See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
JavadocFixTool.java in javadoc plugin (
https://github.com/olamy/JavadocUpdaterTool/blob/master/LICENSE )

2013/6/20 sebb :
> On 19 June 2013 22:40, Baptiste MATHUS  wrote:
>> Hi,
>> I think the best way to track this is to file a JIRA ticket on
>> http://jira.codehaus.org/browse/MJAVADOC
>
> Well OK, I can raise an enhancement request there too.
>
>> Btw, we might be interested by
>> https://github.com/AdoptOpenJDK/JavadocUpdaterTool/blob/master/src/main/java/JavadocFixTool.java
>
> That looks exactly like the file that was released by Oracle; anyone
> can pick up the tool packaged as a jar from the Oracle web-site.
> On it's own, it does not help.
>
>> Cheers
>>
>>
>>
>> 2013/6/19 sebb 
>>
>>> I expect you have all see the news about the Javadoc javascript bug.
>>>
>>> It's going to take a long time for everyone to update their Java
>>> installations to Java 1.7 u25. Likewise for builds that need to use
>>> other Java versions, tweaking poms so Java 7 is used for Javadocs
>>> whilst still maintaining compatibility is a non-trivial task.
>>>
>>> Is there any interest in releasing a "quick-fix" version of the
>>> javadoc plugin that automatically runs the tool after Javadoc
>>> completes?
>>>
>>> The fix code is in Java, and can easily be directly called from the
>>> plugin (no need to start a new process).
>>>
>>> The license looks friendly so long as the code is only used for
>>> Javadoc fixups, and changes are allowed, which is just as well -
>>>
>>> There are a couple of bugs in the tool as currently released.
>>> It does not close all the resources; and failure to close the input
>>> file means it cannot delete the original input file on Windows; that
>>> needs to be fixed as it would not make sense to keep the old faulty
>>> file (even if it is now called index.html.orig).
>>>
>>> I can provide details of the fixes, but a decent IDE will probably
>>> warn about them anyway.
>>>
>>> It would be a great service to the Java community if this could be
>>> fast-tracked.
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: JavadocFixTool integration with Javadoc plugin?

[Olivier Lamy]

2013/6/20 sebb :
> On 20 June 2013 12:15, Olivier Lamy  wrote:
>> See https://github.com/olamy/JavadocUpdaterTool
>> I added a maven build and a mojo.
>> IANAL so I don't know if we can integrate the source of
>> JavadocFixTool.java in javadoc plugin (
>> https://github.com/olamy/JavadocUpdaterTool/blob/master/LICENSE )
>
> As far as I can tell, so long as the code is only used for the
> intended purpose then it's OK.
>
> However, I don't think your plugin fixes all instances of bad javadoc;
> certainly the instructions only solve the problem for site builds.
>
> What about javadoc jars?

it simply depends the phase you bind the plugin (per default it's not
bind to any phase)

>
> The Maven javadoc jar has lots of goals that occur in different
> phases; the only way to be sure to fix all the issues is to always run
> the tool after running Javadoc.
>
>> 2013/6/20 sebb :
>>> On 19 June 2013 22:40, Baptiste MATHUS  wrote:
>>>> Hi,
>>>> I think the best way to track this is to file a JIRA ticket on
>>>> http://jira.codehaus.org/browse/MJAVADOC
>>>
>>> Well OK, I can raise an enhancement request there too.
>>>
>>>> Btw, we might be interested by
>>>> https://github.com/AdoptOpenJDK/JavadocUpdaterTool/blob/master/src/main/java/JavadocFixTool.java
>>>
>>> That looks exactly like the file that was released by Oracle; anyone
>>> can pick up the tool packaged as a jar from the Oracle web-site.
>>> On it's own, it does not help.
>>>
>>>> Cheers
>>>>
>>>>
>>>>
>>>> 2013/6/19 sebb 
>>>>
>>>>> I expect you have all see the news about the Javadoc javascript bug.
>>>>>
>>>>> It's going to take a long time for everyone to update their Java
>>>>> installations to Java 1.7 u25. Likewise for builds that need to use
>>>>> other Java versions, tweaking poms so Java 7 is used for Javadocs
>>>>> whilst still maintaining compatibility is a non-trivial task.
>>>>>
>>>>> Is there any interest in releasing a "quick-fix" version of the
>>>>> javadoc plugin that automatically runs the tool after Javadoc
>>>>> completes?
>>>>>
>>>>> The fix code is in Java, and can easily be directly called from the
>>>>> plugin (no need to start a new process).
>>>>>
>>>>> The license looks friendly so long as the code is only used for
>>>>> Javadoc fixups, and changes are allowed, which is just as well -
>>>>>
>>>>> There are a couple of bugs in the tool as currently released.
>>>>> It does not close all the resources; and failure to close the input
>>>>> file means it cannot delete the original input file on Windows; that
>>>>> needs to be fixed as it would not make sense to keep the old faulty
>>>>> file (even if it is now called index.html.orig).
>>>>>
>>>>> I can provide details of the fixes, but a decent IDE will probably
>>>>> warn about them anyway.
>>>>>
>>>>> It would be a great service to the Java community if this could be
>>>>> fast-tracked.
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Baptiste  MATHUS - http://batmat.net
>>>> Sauvez un arbre,
>>>> Mangez un castor !
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Poposed Sandbox plugins - digest and gpg:signfiles

[Olivier Lamy]

2013/6/23 sebb :
> I've just been told about the Maven Sandbox, which seems like it might
> be a better location for two general purpose plugins that are
> currently being developed at Apache Commons.
>
> Digest
> The digest plugin is a simple plugin that can generate hashes
> (currently just MD5 and SHA1) for any files specified via
> includes/excludes (or on command-line).
> Although it's possible to use Antrun to create the hashes, it's a bit
> awkward to configure.
> The plugin could be extended to check digests as well, and of course
> to generate other digest types.
> I'm hoping it might be generally useful.
>
> Gpg-signfiles
> This is an extension of the Maven Gpg Plugin which can sign arbitrary
> files, not just ones attached to the project
> I'm hoping it might be merged with the existing Gpg plugin one day;
> having the code in the sandbox should make it easier for other Maven
> devs to help.
>
> I propose creating the following directories under
> https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins
>
> maven-digest-plugin
> maven-gpgsignfiles-plugin
>
> Any objections?

Just do it!

>
> Also, is there a Sandbox repo where the plugins can be deployed for testing?
> Or is it up to users to checkout the source and install the plugins locally?

We can deploy snapshots to repository.a.o

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



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Poposed Sandbox plugins - digest and gpg:signfiles

[Olivier Lamy]

We can work a bit with those snapshots for review etc..
Then promote to non snapshot path and release it.
BTW if you prefer move those plugins to mojo@codehaus svn it's possible too.

2013/6/23 sebb :
> On 23 June 2013 01:00, Olivier Lamy  wrote:
>> 2013/6/23 sebb :
>>> Also, is there a Sandbox repo where the plugins can be deployed for testing?
>>> Or is it up to users to checkout the source and install the plugins locally?
>>
>> We can deploy snapshots to repository.a.o
>
> OK but what about non-snapshot versions?
> Obviously they cannot be published to the Maven Central repo, but is
> there a local repo like Codehaus have?
>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Maven Enforcer version 1.3

[Olivier Lamy]

+1

2013/6/22 Robert Scholte :
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19011
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-056/
> https://repository.apache.org/content/repositories/maven-056/org/apache/maven/enforcer/enforcer/1.3/enforcer-1.3-source-release.zip
>
> Staging site:
> http://maven.apache.org/enforcer-archives/enforcer-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[VOTE] Apache Maven Javadoc Plugin 2.9.1

[Olivier Lamy]

Hi,
I'd like to release Apache Maven Javadoc Plugin 2.9.1.

This version contains the code to fix the javadoc security issue after
the javadoc generation.

We fixed 6 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create

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

Staging site: 
http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/

Vote open for 72H

[+1]
[0]
[-1]

Thanks,
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven Javadoc Plugin 2.9.1

[Olivier Lamy]

2013/6/25 sebb :
> On 24 June 2013 13:04, Olivier Lamy  wrote:
>> Hi,
>> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>>
>> This version contains the code to fix the javadoc security issue after
>> the javadoc generation.
>>
>> We fixed 6 issues:
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create
>>
>> Staging repository: 
>> https://repository.apache.org/content/repositories/maven-062
>>
>> Staging site: 
>> http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/
>
> SVN tag?

It's a bit implicit if you know our sources tree

>
> KEYS file?

I believe it's available as most of ASF project at
svn.a.o/repos/asf/$tlp/project/KEYS

>
>> Vote open for 72H
>>
>> [+1]
>> [0]
>> [-1]
>
> The parameter applyJavadocSecurityFix  in the class
> AbstractJavadocMojo is documented as being @since 2.10.
Argh good catch I will fix that
>
> The Release Notes page on the site is empty.
?
>
> There's no NOTICE and LICENSE in SVN at the level of the plugin.
Those files are in the voted artifacts.
>
> The NOTICE file looks wrong to me.
> It has a spurious blank line at the start.
> The next line says:
> Maven Javadoc Plugin
> This should be
>Apache Maven Javadoc Plugin
Easy to fix
>
> The index.html file in the javadoc jar appears to have the frame bug;
> certainly it does not contain a "function validURL(url)" line.
Chicken and egg issue as I need the fix but I'm build the fix.
So this will be probably the last javadoc jar we publish :-). At least
the most (public website has been generated with the fix).

BTW I cancel the release.

>
> Sorry, but I would have to vote -1 if mine were binding.
>
>> Thanks,
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: svn commit: r1496315 - /maven/sandbox/trunk/plugins/maven-digest-plugin/src/main/java/org/apache/maven/plugins/digest/DigestMojo.java

[Olivier Lamy]

Great.
Quick note have a look at
http://maven.apache.org/developers/conventions/code.html
:-)


2013/6/25  :
> Author: sebb
> Date: Tue Jun 25 00:51:03 2013
> New Revision: 1496315
>
> URL: http://svn.apache.org/r1496315
> Log:
> Allow list of digests to be provided on command-line
> Allow extension name to be overridden
>
> Modified:
> 
> maven/sandbox/trunk/plugins/maven-digest-plugin/src/main/java/org/apache/maven/plugins/digest/DigestMojo.java
>
> Modified: 
> maven/sandbox/trunk/plugins/maven-digest-plugin/src/main/java/org/apache/maven/plugins/digest/DigestMojo.java
> URL: 
> http://svn.apache.org/viewvc/maven/sandbox/trunk/plugins/maven-digest-plugin/src/main/java/org/apache/maven/plugins/digest/DigestMojo.java?rev=1496315&r1=1496314&r2=1496315&view=diff
> ==
> --- 
> maven/sandbox/trunk/plugins/maven-digest-plugin/src/main/java/org/apache/maven/plugins/digest/DigestMojo.java
>  (original)
> +++ 
> maven/sandbox/trunk/plugins/maven-digest-plugin/src/main/java/org/apache/maven/plugins/digest/DigestMojo.java
>  Tue Jun 25 00:51:03 2013
> @@ -69,10 +69,19 @@ public class DigestMojo extends Abstract
>  private String files;
>
>  /**
> + * List of digests (algorithms) to create, comma-separated (intended for 
> command-line usage).
> + * Overrides algorithms; uses same syntax
> + */
> +@Parameter (property="maven.digest.digests")
> +private String digests;
> +
> +/**
>   * The list of algorithm names with which to create digests.
>   * If none specified, the default is {@code MD5} and {@code SHA1}.
>   * By default the file extension is assumed to be the algorithm name
>   * converted to lower-case, and any "-" characters removed.
> + * The extension name can be provided by suffixing the algorithm name
> + * with ">" followed by the extension, for example: "SHA-1>sha".
>   */
>  @Parameter
>  private Set algorithms;
> @@ -87,8 +96,15 @@ public class DigestMojo extends Abstract
>  String files[] = scanForSources();
>  Log log = getLog();
>  if (files.length == 0) {
> -log.warn("No files found. Please configure at least one 
>  item or use -Ddigest.files");
> +log.warn("No files found. Please configure at least one 
>  item or use -Dmaven.digest.files");
>  } else {
> +if (digests != null && digests.length() > 0) {
> +String [] digest = digests.split(",");
> +algorithms = new HashSet(digest.length);
> +for (String d : digest) {
> +   algorithms.add(d);
> +}
> +}
>  if (algorithms == null || algorithms.size() == 0) {
>  algorithms = new HashSet(2);
>  algorithms.add("MD5");
> @@ -97,7 +113,7 @@ public class DigestMojo extends Abstract
>  try {
>  for(String file : files) {
>  for(String algorithm : algorithms) {
> -String[] parts = algorithm.split("|");
> +String[] parts = algorithm.split(">");
>  String extension;
>  if (parts.length == 2) {
>  algorithm = parts[0];
> @@ -126,10 +142,12 @@ public class DigestMojo extends Abstract
>  }
>
>  private void createDigest(String algorithm, String extension, String 
> file) throws Exception {
> +// Unfortunately DigestUtils.getDigest is not public
> +// Do this before opening file in case not found
> +MessageDigest digest = MessageDigest.getInstance(algorithm);
>  FileInputStream is = new FileInputStream(file);
>  PrintWriter pw = new PrintWriter(file+extension, "UTF-8");
> -// Unfortunately DigestUtils.getDigest is not public
> -pw.print(digestHex(MessageDigest.getInstance(algorithm), is));
> +pw.print(digestHex(digest, is));
>  if (appendFilename) {
>  pw.println(" *" + file);
>  } else {
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[VOTE] Apache Maven Javadoc Plugin 2.9.1 (take 2)

[Olivier Lamy]

Hi,
I'd like to release Apache Maven Javadoc Plugin 2.9.1.

This version contains the code to fix the javadoc security issue after
the javadoc generation.

Since previous try I fix the @since for applying the javadoc security fix.

We fixed 6 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create

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

Staging site: 
http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/

Vote open for 72H

[+1]
[0]
[-1]

Thanks,
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven Javadoc Plugin 2.9.1 (take 2)

[Olivier Lamy]

I will try to fix that. (as I remember changes plugin need to be
upgraded with new jira version)
So I can try redeploy the site with the fix.



2013/6/25 Ralph Goers :
> KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS
>
> svn tag - 
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1
>
> +1 on the release however it is odd that the Release Notes page is empty.
>
> Ralph
>
> On Jun 24, 2013, at 7:15 PM, sebb wrote:
>
>> On 25 June 2013 02:48, Olivier Lamy  wrote:
>>> Hi,
>>> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>>>
>>> This version contains the code to fix the javadoc security issue after
>>> the javadoc generation.
>>>
>>> Since previous try I fix the @since for applying the javadoc security fix.
>>>
>>> We fixed 6 issues:
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/maven-066/
>>
>> The NOTICE file still has a spurious blank line at the start; it
>> should be removed before the next release candidate.
>>
>>> Staging site: 
>>> http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/
>>
>> The release notes page is empty, as before.
>> Given that this release has a vital change in it, that is very unfortunate.
>>
>> SVN tag and revision?
>> Without them, how can reviewers determine the provenance of the source
>> files in the source release?
>>
>> KEYS file?
>> How can we check the sigs?
>>
>>> Vote open for 72H
>>>
>>> [+1]
>>> [0]
>>> [-1]
>>>
>>> Thanks,
>>> --
>>> Olivier Lamy
>>> Ecetera: http://ecetera.com.au
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------
>>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven Javadoc Plugin 2.9.1 (take 2)

[Olivier Lamy]

fixed: 
http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/jira-report.html


2013/6/25 Olivier Lamy :
> I will try to fix that. (as I remember changes plugin need to be
> upgraded with new jira version)
> So I can try redeploy the site with the fix.
>
>
>
> 2013/6/25 Ralph Goers :
>> KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS
>>
>> svn tag - 
>> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1
>>
>> +1 on the release however it is odd that the Release Notes page is empty.
>>
>> Ralph
>>
>> On Jun 24, 2013, at 7:15 PM, sebb wrote:
>>
>>> On 25 June 2013 02:48, Olivier Lamy  wrote:
>>>> Hi,
>>>> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>>>>
>>>> This version contains the code to fix the javadoc security issue after
>>>> the javadoc generation.
>>>>
>>>> Since previous try I fix the @since for applying the javadoc security fix.
>>>>
>>>> We fixed 6 issues:
>>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/maven-066/
>>>
>>> The NOTICE file still has a spurious blank line at the start; it
>>> should be removed before the next release candidate.
>>>
>>>> Staging site: 
>>>> http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/
>>>
>>> The release notes page is empty, as before.
>>> Given that this release has a vital change in it, that is very unfortunate.
>>>
>>> SVN tag and revision?
>>> Without them, how can reviewers determine the provenance of the source
>>> files in the source release?
>>>
>>> KEYS file?
>>> How can we check the sigs?
>>>
>>>> Vote open for 72H
>>>>
>>>> [+1]
>>>> [0]
>>>> [-1]
>>>>
>>>> Thanks,
>>>> --
>>>> Olivier Lamy
>>>> Ecetera: http://ecetera.com.au
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> -
>>>> 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 Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven Javadoc Plugin 2.9.1 (take 2)

[Olivier Lamy]

2013/6/25 sebb :
> On 25 June 2013 07:46, Ralph Goers  wrote:
>> KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS
>
> Thanks, the key id used for signing is in the file.
> Also the id is available from key servers.
>
>> svn tag - 
>> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1
>
> Thanks, but that is insufficient as the tag has been recreated several times.
> I think the last one was r1496317
>
> If there is ever a question about how a certain file got into a
> release, it's vital to have traceability.
AFAIK svn log can give you informations ?
>

> The source archive agrees with the SVN tag, apart from some expected
> differences - e.g. DEPENDENCIES is only in the source archive

We use this release process for very long time now. Not sure this
thread is the good place to discuss that.
If you want to discuss that start an other thread but perso I'm happy
with the current process as it's very simple and doesn't require to
many manual actions required.
That's documented here:
http://maven.apache.org/developers/release/releasing.html.


>
>> +1 on the release however it is odd that the Release Notes page is empty.
>
> Please fix that on the actual site deploy.

I think it's fixed now see:
http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/jira-report.html

>
>> Ralph
>>
>> On Jun 24, 2013, at 7:15 PM, sebb wrote:
>>
>>> On 25 June 2013 02:48, Olivier Lamy  wrote:
>>>> Hi,
>>>> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>>>>
>>>> This version contains the code to fix the javadoc security issue after
>>>> the javadoc generation.
>>>>
>>>> Since previous try I fix the @since for applying the javadoc security fix.
>>>>
>>>> We fixed 6 issues:
>>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/maven-066/
>>>
>>> The NOTICE file still has a spurious blank line at the start; it
>>> should be removed before the next release candidate.
>>>
>>>> Staging site: 
>>>> http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/
>>>
>>> The release notes page is empty, as before.
>>> Given that this release has a vital change in it, that is very unfortunate.
>>>
>>> SVN tag and revision?
>>> Without them, how can reviewers determine the provenance of the source
>>> files in the source release?
>>>
>>> KEYS file?
>>> How can we check the sigs?
>>>
>>>> Vote open for 72H
>>>>
>>>> [+1]
>>>> [0]
>>>> [-1]
>>>>
>>>> Thanks,
>>>> --
>>>> Olivier Lamy
>>>> Ecetera: http://ecetera.com.au
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> -
>>>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Sandbox - cannot deploy snapshot of maven-digest-plugin; access denied

[Olivier Lamy]

2013/6/25 sebb :
> I'd like to try deploying a snapshot of the new digest plugin but I
> get "access denied" errors.
>
> Any idea why that should be?
IMHO you need to be in the maven group.
>
> I can deploy Common snapshots OK to the same repo; is there an ACL
> that only allows Maven committers to deploy snapshots. or is some
> other config needed?
I deployed the digest one.
If you fix the groupId and artifactId for the
maven-gpgsignfiles-plugin,  I can do it for you too.

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



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Sandbox - cannot deploy snapshot of maven-digest-plugin; access denied

[Olivier Lamy]

2013/6/25 sebb :
> On 25 June 2013 11:49, Olivier Lamy  wrote:
>> 2013/6/25 sebb :
>>> I'd like to try deploying a snapshot of the new digest plugin but I
>>> get "access denied" errors.
>>>
>>> Any idea why that should be?
>> IMHO you need to be in the maven group.
>
> OK, NP.
>
>>>
>>> I can deploy Common snapshots OK to the same repo; is there an ACL
>>> that only allows Maven committers to deploy snapshots. or is some
>>> other config needed?
>> I deployed the digest one.
>
> Thanks.
>
>> If you fix the groupId and artifactId for the
>> maven-gpgsignfiles-plugin,  I can do it for you too.
>
> Ta.
>
> There's quite a lot of other stuff that needs fixing as well to
> replace the Commons references.
> I hope to get to it soon.

no worries we can fix that too.

>
>>>
>>> ---------
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Release process updates

[Olivier Lamy]

re far
>>>>>>> too many files in the average source archive to check individually.
>>>>>>> And how would one check their provenance? The obvious way is to
>>>>>>> compare them with the entries in SCM.
>>>>>>>
>>>>>>> Therefore, I contend that a release vote does not make sense without
>>>>>>> the SCM tag.
>>>>>>> In the case of SVN, since tags are not immutable, the vote e-mail also
>>>>>>> needs the revision.
>>>>>>>
>>>>>>> Whether every reviewer actually checks the source archive against SCM
>>>>>>> is another matter.
>>>>>>> But if the required SCM information is not present, it would be
>>>>>>> difficult to argue that the RM had provided sufficient information for
>>>>>>> a valid review to take place.
>>>>>>>
>>>>>>> -
>>>>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second 
>>> Edition<http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: org.apache.maven.plugin or org.apache.maven.plugins ?

[Olivier Lamy]

For historical reason this has changed etc..
Use org.apache.maven.plugins (same as groupId)


2013/6/26 sebb :
> Most plugins seem to be sub-packages of org.apache.maven.plugin; just
> a few use org.apache.maven.plugins (e.g. enforcer, shade).
>
> Is there a convention as to which to choose, or are the plugins that
> use "plugins" an anomaly?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Release process updates

[Olivier Lamy]

correct.
In case of failure during deploy:
* cd target/checkout && mvn clean deploy -Papache-release
or
* export/checkout the tag && mvn clean deploy -Papache-release



2013/6/26 Barrie Treloar :
>> And if the "mvn deploy" fails for any reason?
>
> We get this often enough with a crappy connection to our nexus servers.
>
>> Is it necessary to re-run release:perform?
>
> release:perform may be at the stage where it has deleted the
> configuration file details, in which case you just revert to the
> manual steps that release:perform is automating for you.
>
> If its tagged everything correctly, and you build is fine - but the
> upload to the staging repository failed, then you can do this
> yourself.
>
> Or you can just re-spin the release process. No drama.
>
>> And does that always create a fresh workspace?
>
> Yes.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Download links for source packages - where are they?

[Olivier Lamy]

2013/6/26 sebb :
> I could not find any download links for Maven source packages.
>
> As the ASF primary purpose is to release source, and that must be
> released via the mirror system, there ought to be download pages with
> links to the source package, sigs, hashes and KEYS file.
>
> Yes, there are source packages for some Maven plugins, but that is not
> the same as providing download pages.
>
> AFAIK every single other ASF project has download pages.

Is that mandatory ? Do you have any link saying that ?
At least for core I understand but for plugins...
BTW we started to put everything is here: http://www.us.apache.org/dist/maven/


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



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Download links for source packages - where are they?

[Olivier Lamy]

 a plugin from source and
>> then installing it into their local Maven cache, it is much easier to
>> get Maven to download the binaries and use them that way.
>>
>> The only reason I can think of a user wanting access to the source is
>> so they can make modifications, and if they dont know about the ASF
>> distribution pages, we give them the source repository link, e.g.
>> http://maven.apache.org/plugins/maven-compiler-plugin/source-repository.html,
>> on the automatically generated web pages. To me this is better as they
>> can then create patches.
>>
>> Does that make sense?
>
> The point is that the ASF release source, and it must be provided for
> download via the ASF mirrors.
>
> See:
>
> http://www.apache.org/dev/release.html#host-GA
>
> If you don't point users to the source, I don't see how you can claim
> it has been properly released.
>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Release process updates

[Olivier Lamy]

;> >> >> > >>>>>
>> >> >> >> > >>>>> Ralph
>> >> >> >> > >>>>>
>> >> >> >> > >>>>> On Jun 25, 2013, at 9:52 AM, sebb wrote:
>> >> >> >> > >>>>>> The mission of the ASF is to release software as source,
>> >> and to
>> >> >> >> >
>> >> >> >> > ensure
>> >> >> >> >
>> >> >> >> > >>>>>> that the released source is available under the Apache
>> >> Licence.
>> >> >> >> > >>>>>>
>> >> >> >> > >>>>>> Before a release can be approved it must be voted on by
>> the
>> >> PMC.
>> >> >> >> > >>>>>> The review process needs to establish that the proposed
>> >> source
>> >> >> >> >
>> >> >> >> > release
>> >> >> >> >
>> >> >> >> > >>>>>> meets those aims.
>> >> >> >> > >>>>>>
>> >> >> >> > >>>>>> It's all but impossible for reviewers to examine every
>> >> single
>> >> >> >> > >>>>>> file
>> >> >> >> >
>> >> >> >> > in
>> >> >> >> >
>> >> >> >> > >>>>>> a source archive to determine if it meets the criteria.
>> >> >> >> > >>>>>> And it's not unknown for spurious files to creep into a
>> >> release
>> >> >> >> > >>>>>> (perhaps from a stale workspace - are releases always
>> built
>> >> from
>> >> >> >> > >>>>>> a
>> >> >> >> > >>>>>> fresh checkout of the tag?)
>> >> >> >> > >>>>>>
>> >> >> >> > >>>>>> However, PMCs are also required to check what is added to
>> >> the
>> >> >> >> > >>>>>> SCM
>> >> >> >> > >>>>>> (SVN/Git) to make sure it meets the required license
>> >> criteria.
>> >> >> >> > >>>>>> This is done on an ongoing basis as part of reviewing
>> >> check-ins
>> >> >> >>
>> >> >> >> and
>> >> >> >>
>> >> >> >> > >>>>>> accepting new contributions.
>> >> >> >> > >>>>>> So provided that all the files in the source release are
>> >> also
>> >> >> >> >
>> >> >> >> > present
>> >> >> >> >
>> >> >> >> > >>>>>> in SCM, the PMC can be reasonably sure that the source
>> >> release
>> >> >> >>
>> >> >> >> meets
>> >> >> >>
>> >> >> >> > >>>>>> the ASF criteria.
>> >> >> >> > >>>>>>
>> >> >> >> > >>>>>> Without having the SCM as a database of validated files,
>> >> there
>> >> >> >> > >>>>>> are
>> >> >> >> >
>> >> >> >> > far
>> >> >> >> >
>> >> >> >> > >>>>>> too many files in the average source archive to check
>> >> >> >>
>> >> >> >> individually.
>> >> >> >>
>> >> >> >> > >>>>>> And how would one check their provenance? The obvious way
>> >> is to
>> >> >> >> > >>>>>> compare them with the entries in SCM.
>> >> >> >> > >>>>>>
>> >> >> >> > >>>>>> Therefore, I contend that a release vote does not make
>> sense
>> >> >> >>
>> >> >> >> without
>> >> >> >>
>> >> >> >> > >>>>>> the SCM tag.
>> >> >> >> > >>>>>> In the case of SVN, since tags are not immutable, the
>> vote
>> >> >> >> > >>>>>> e-mail
>> >> >> >> >
>> >> >> >> > also
>> >> >> >> >
>> >> >> >> > >>>>>> needs the revision.
>> >> >> >> > >>>>>>
>> >> >> >> > >>>>>> Whether every reviewer actually checks the source archive
>> >> >> >> > >>>>>> against
>> >> >> >> >
>> >> >> >> > SCM
>> >> >> >> >
>> >> >> >> > >>>>>> is another matter.
>> >> >> >> > >>>>>> But if the required SCM information is not present, it
>> >> would be
>> >> >> >> > >>>>>> difficult to argue that the RM had provided sufficient
>> >> >> >> > >>>>>> information
>> >> >> >> >
>> >> >> >> > for
>> >> >> >> >
>> >> >> >> > >>>>>> a valid review to take place.
>> >> >> >> >
>> >> >> >> >
>> >> -
>> >> >> >> >
>> >> >> >> > >>>>>> 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
>> >> >> >> > >>
>> >> >> >> > >> --
>> >> >> >> > >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> >> >> >> > >> Java Persistence with Hibernate, Second Edition<
>> >> >> >> >
>> >> >> >> > http://www.manning.com/bauer3/>
>> >> >> >> >
>> >> >> >> > >> JUnit in Action, Second Edition <
>> >> http://www.manning.com/tahchiev/>
>> >> >> >> > >> Spring Batch in Action <http://www.manning.com/templier/>
>> >> >> >> > >> Blog: http://garygregory.wordpress.com
>> >> >> >> > >> Home: http://garygregory.com/
>> >> >> >> > >> Tweet! http://twitter.com/GaryGregory
>> >> >> >> > >
>> >> >> >> > >
>> >> -
>> >> >> >> > > 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
>> >> >> >>
>> >> >> >> --
>> >> >> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> >> >> >> Java Persistence with Hibernate, Second Edition<
>> >> >> >> http://www.manning.com/bauer3/>
>> >> >> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/
>> >
>> >> >> >> Spring Batch in Action <http://www.manning.com/templier/>
>> >> >> >> Blog: http://garygregory.wordpress.com
>> >> >> >> Home: http://garygregory.com/
>> >> >> >> Tweet! http://twitter.com/GaryGregory
>> >> >>
>> >> >> -
>> >> >> 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
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Maven Enforcer version 1.3 (take 2)

[Olivier Lamy]

+1

2013/6/26 Robert Scholte :
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19011
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-070/
> https://repository.apache.org/content/repositories/maven-070/org/apache/maven/enforcer/enforcer/1.3/enforcer-1.3-source-release.zip
>
> Staging site:
> http://maven.apache.org/enforcer-archives/enforcer-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven Javadoc Plugin 2.9.1 (take 2)

[Olivier Lamy]

+1

2013/6/25 Olivier Lamy :
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>
> This version contains the code to fix the javadoc security issue after
> the javadoc generation.
>
> Since previous try I fix the @since for applying the javadoc security fix.
>
> We fixed 6 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-066/
>
> Staging site: 
> http://maven.apache.org/plugins-archives/maven-javadoc-plugin-2.9.1/
>
> Vote open for 72H
>
> [+1]
> [0]
> [-1]
>
> Thanks,
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[RESULT] [VOTE] Apache Maven Javadoc Plugin 2.9.1

[Olivier Lamy]

Hi,
The vote has passed with the following result:
+1 (binding): Kristian, Ralph, Robert, Hervé, Olivier
+1 (non binding): Tony
-1 (non binding): Fred Cooke

Will finish release complete.

--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[ANN] Apache Maven Javadoc Plugin 2.9.1 Released

[Olivier Lamy]

The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 2.9.1

The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.

This version contains the code to fix the javadoc security issue after
the javadoc generation.

http://maven.apache.org/plugins/maven-javadoc-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-javadoc-plugin
  2.9.1


Release Notes - Apache Maven Javadoc Plugin - Version 2.9.1

** Bug
* [MJAVADOC-354] - isValidJavadocLink is too strict: doesn't
support unnamed package
* [MJAVADOC-358] - maven-javadoc-plugin is missing threadsafe on
some goals like test-jar

** Improvement
* [MJAVADOC-361] - Improve linguistic style of bottom
* [MJAVADOC-363] - [Patch] Port maven-javadoc-plugin from
httpclient 3 to httpclient 4
* [MJAVADOC-370] - Javadoc vulnerability (CVE-2013-1571 [1], VU#225657 [2])

** Task
* [MJAVADOC-364] - Upgrade QDox to 1.12.1

Have Fun,
--
The Apache Maven team

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

Re: KEYS file has duplicate entry for F0E309FF - Vincent Massol

[Olivier Lamy]

fixed.
Thanks for reporting.

2013/6/28 sebb :
> The file
>
> http://www.apache.org/dist/maven/KEYS
>
> has two entries for F0E309FF - Vincent Massol
>
> One of them should be deleted.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Donay

[Olivier Lamy]

2013/6/29 Robert Scholte :
> Hi,
>
> recently I noticed a new thing at the Jira of Codehaus: Donay
> It is saying "Facing this issue? Let the Developers help you out."
>
> Here Donay explains how it works:
> https://secure.donay.com/site/how-it-works
>
> Has this been shared with the community?
AFAIK nope.

> Does anybody have experience with this?
No.

>
> IIRC we had a similar situation with http://www.freedomsponsors.org/ and
> we've removed their comments if they were actively busy with crowdfunding.
Maybe is it possible to remove it per project? (you can probably ask
in HAUS jira ?)

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



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Release process updates

[Olivier Lamy]

2013/6/26 sebb :
> The mission of the ASF is to release software as source, and to ensure
> that the released source is available under the Apache Licence.

Excuse me but I have always understand the ASF mission as building
communities around softwares.
Community over Code and not Process over Code.

I believe (my personal opinion) we are here to make two communities
happy: dev community with easing their task to build and release good
software for the users community.

With all of those emails, it's just a way to discourage people who
want to release software for their users.
Yes too much (non useful) process tend/will discourage volunteers to
release something.

My 0,02AUD
--
Olivier


>
> Before a release can be approved it must be voted on by the PMC.
> The review process needs to establish that the proposed source release
> meets those aims.
>
> It's all but impossible for reviewers to examine every single file in
> a source archive to determine if it meets the criteria.
> And it's not unknown for spurious files to creep into a release
> (perhaps from a stale workspace - are releases always built from a
> fresh checkout of the tag?)
>
> However, PMCs are also required to check what is added to the SCM
> (SVN/Git) to make sure it meets the required license criteria.
> This is done on an ongoing basis as part of reviewing check-ins and
> accepting new contributions.
> So provided that all the files in the source release are also present
> in SCM, the PMC can be reasonably sure that the source release meets
> the ASF criteria.
>
> Without having the SCM as a database of validated files, there are far
> too many files in the average source archive to check individually.
> And how would one check their provenance? The obvious way is to
> compare them with the entries in SCM.
>
> Therefore, I contend that a release vote does not make sense without
> the SCM tag.
> In the case of SVN, since tags are not immutable, the vote e-mail also
> needs the revision.
>
> Whether every reviewer actually checks the source archive against SCM
> is another matter.
> But if the required SCM information is not present, it would be
> difficult to argue that the RM had provided sufficient information for
> a valid review to take place.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Issue# svn scm maven plugin doenot work with special character @ in SVN passwords

[Olivier Lamy]

Hi Akanksha,
We need more informations.
Which context are you using the plugin?
Can you record an issue here http://jira.codehaus.org/browse/SCM with
some details?
The scm api is used by various plugins. So we need those informations
to be able to investigate.

Cheers,
--
Olivier

2013/7/3 Greg Stein :
> Or to be a bit more helpful, please send this to dev@maven.apache.org (cc'd).
>
> Cheers,
> -g
>
> On Tue, Jul 2, 2013 at 6:02 PM, Daniel Shahaf  wrote:
>> Report this to the maven guys.  We don't maintain that plugin.
>>
>> Akanksha Dayal wrote on Tue, Jul 02, 2013 at 14:33:53 -0700:
>>> Hi Developers,
>>>
>>> I bumped into this issue while working with scm svn maven plugin.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: svn commit: r1498969 - /maven/site/trunk/content/markdown/project-roles.md

[Olivier Lamy]

on the [Maven user list][2]
>> +* Joined one of the other Maven user communities.
>> +
>> +We hope your bug report has received some attention, if it
>> +hasn't why don't you see if you can fix the issue yourself
>> +and submit a patch?
>> +
>> +We hope your question was answered, if it hasn't think of
>> +all the other users who's questions sit unanswered, how many
>> +of them do you know an answer for (even if only a partial
>> +answer)? Why don't you respond to their questions with the
>> +answers you know? If everybody did that, your question would
>> +have an answer. Pay it forward!
>> +
>> +We hope your experience in one of the other Maven user
>> +communities is a positive one, so why not join the canonical
>> +Maven user community and subscribe to the [Maven user list][2]?
>> +
>> +### Contributors
>> +
>> +People who use Maven, have joined the Maven community and contribute
>> +back to the community. This includes people who:
>> +* Submit reports of the results of testing proposed releases of
>> +Maven and Maven plugins
>> +* Answer questions on the [Maven user list][2] (or even other Maven user
>> communities)
>> +* Submit patches to resolve reported bugs in Maven or Maven plugins
>> hosted at Apache.
>> +* Help curate bug reports by identifying duplicate reports, or
>> +related issues.
>> +
>> +Keep up the contributions, you are a critical member of our
>> +community. If we like what we see, we may even ask you to
>> +consider taking a formal role in our project.
>> +
>> +## Formal roles
>> +
>> +### [Committers](
>> http://www.apache.org/foundation/how-it-works.html#committers)
>> +
>> +These are those people who have been given write access to the
>> +Apache Maven code repository and have a signed
>> +[Contributor License Agreement (CLA)][4] on file with the ASF.
>> +
>> +The Apache Maven project uses a Commit then Review policy.
>> +
>> +Committers are responsible for ensuring that every file they
>> +commit is covered by a valid CLA.
>> +
>> +### Emeritus committers
>> +
>> +If a committer decides that they cannot currently continue with
>> +the responsibilities of a committer, they may elect to go
>> +emeritus.
>> +
>> +At any time an emeritus committer for the Apache Maven project
>> +may decide that they want to become an active committer again
>> +by informing the [project management committee][3]. The current
>> +policy is that committer role reinstatement is automatic.
>> +
>> +### [Project Management Committee][
>> http://www.apache.org/foundation/how-it-works.html#pmc-members]
>> +
>> +The Project Management Committee as a whole is the entity that
>> +controls the project. Membership of the Project Management Committee
>> +is decided by the board of the Apache Software Foundation based on
>> +nominations from the Project Management Committee.
>> +
>> +It is a long standing tradition of the Apache Maven Project that
>> +the Project Management Committee reviews the active committers
>> +approximately every 6 months with a view to determining whether
>> +any of those committers would be suitable candidates to
>> +recommend to the board for inclusion on the PMC. It should be
>> +noted that this is simply a tradition and not a right. There
>> +are significant responsibilities that accompany the PMC role
>> +and as such if a person is not demonstrating those responsibilities
>> +they may not be nominated or their nomination
>> +may be rejected by the board. Such decisions are not a
>> +reflection of the technical competence of the person, and
>> +indeed the person themselves may even decide to turn down the
>> +nomination. For that reason the results of such periodic reviews
>> +are kept confidential.
>> +
>> +The Project Management Committee has the following responsibilities:
>> +
>> +* Proposing active contributors for committership.
>> +* Binding votes in project decisions.
>> +* Voting on release artifacts.
>> +* 
>> +
>> +### [Project Management Chair][
>> http://www.apache.org/foundation/how-it-works.html#pmc-chair]
>> +
>> +For various legal reasons, there are certain things that the Apache
>> +Software Foundation can only delegate to an officer of the foundation.
>> +
>> +The Project Management Committee is responsible for nominating
>> +the lucky victim who gets made an officer of the foundation (subject
>> +to the approval of the board).
>> +
>> +This person then becomes the interface between the board and
>> +the project management committee. They do not have any other
>> +additional gravitas in the project, it is the Project Management
>> +Committee as a whole that is responsible for the direction of the project.
>> +
>> +  [1]: http://stackoverflow.com/questions/tagged/maven
>> +  [2]: mailto:us...@maven.apache.org
>> +  [3]: mailto:priv...@maven.apache.org
>> +  [4]: http://www.apache.org/licenses/#clas
>> \ No newline at end of file
>>
>>
>>



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: svn commit: r1498969 - /maven/site/trunk/content/markdown/project-roles.md

[Olivier Lamy]

2013/7/3 Stephen Connolly :
> It is important, but it interrupts the flow of the sentence. It is good
> english to put interruptions in a subordinate clause so that the reader
> knows to skip them in making sense of the sentence. If you want another way
> would be to put it in a different interuption style - such as within a
> minus block - assuming they make sense for the current sentence structure.
>

thanks for the english lesson!
As that could be different in French it looks we reach a cultural
language difference :-)

/me not a native english writer/speaker but learning aussie language :-)

>
> On 3 July 2013 10:17, Olivier Lamy  wrote:
>
>> 2013/7/3 Stephen Connolly :
>> > Anyone who has suggestions for improvements or additional content, please
>> > shout out or commit your changes...
>> >
>> > The aim is to let people understand the different roles and
>> > responsibilities in the Maven community
>> >
>> >
>> > On 2 July 2013 16:13,  wrote:
>> >
>> >> Author: stephenc
>> >> Date: Tue Jul  2 15:13:59 2013
>> >> New Revision: 1498969
>> >>
>> >> URL: http://svn.apache.org/r1498969
>> >> Log:
>> >> This is only a draft... and there is still a lot of review needed
>> >>
>> >> Added:
>> >> maven/site/trunk/content/markdown/project-roles.md
>> >>
>> >> Added: maven/site/trunk/content/markdown/project-roles.md
>> >> URL:
>> >>
>> http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-roles.md?rev=1498969&view=auto
>> >>
>> >>
>> ==
>> >> --- maven/site/trunk/content/markdown/project-roles.md (added)
>> >> +++ maven/site/trunk/content/markdown/project-roles.md Tue Jul  2
>> >> 15:13:59 2013
>> >> @@ -0,0 +1,194 @@
>> >> +
>> >> +# Apache Maven Project Roles
>> >> +
>> >> +The Apache Maven project is not just the software it produces.
>> >> +The Apache Foundation has a phrase: “Community over code† which
>> >> +is about how it is the community that grows around a project
>> >> +that is the most important thing.
>> >> +
>> >> +Everyone reading this is part of the Apache Maven community,
>> >> +and even if you are an invisible part of the Apache Maven
>> >> +community you are still part of the community.
>> >> +
>> >> +There are many ways we can sort the people in our
>> >> +community, we present the following as one such way.
>> >> +Please do not take offence if you disagree with this
>> >> +categorisation. It is important to remember that we are
>> >> +a *community* not a *clique* so you are entitled to disagree
>> >> +with others in the community. (Note that the right to disagree
>> >> +comes with a responsibility not to deliberately cause offence
>> >> +or discord.)
>>
>> Why parentheses here? That give me the impression it's not important.
>> Perso I believe it's important :-)
>>
>> >> +
>> >> +## Informal roles
>> >> +
>> >> +### Lurkers
>> >> +
>> >> +People who do not use Maven at all, but have an interest in
>> >> +the project. This can include people who are developing
>> >> +competing software tools to Apache Maven.
>> >> +
>> >> +It would be great if the lurkers would come out of the shadows
>> >> +and make themselves visible, but every community needs its
>> >> +lurkers, so if you are a lurker sulking about on the fringes
>> >> +of the Apache Maven project, know that you are a valued member
>> >> +of our community. If you ever feel the need to change your role
>> >> +we will welcome you with open arms… (and if we don't welcome you
>> >> +with open arms, please advise the [Project management committee][3]
>> >> +who are responsible for ensuring that the community is a healthy
>> >> +one)
>> >> +
>> >> +### Consumers
>> >> +
>> >> +People who use Maven, but do not actively join the community.
>> >> +This does not include people who are: subscribed to one of the
>> >> +Maven mailing lists; active in a Maven user community (e.g.
>> >> +something like [stackoverflow][1]; submitting bug reports; etc.
>> >> +
>> >> +Maybe Apache Maven is the perf

[VOTE] Apache Maven War plugin 2.4

[Olivier Lamy]

Hi,
I'd like to release Apache Maven War Plugin 2.4.

We fixed 10 issue
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&projectId=11150

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

Source release:
https://repository.apache.org/content/repositories/maven-105/org/apache/maven/plugins/maven-war-plugin/2.4/maven-war-plugin-2.4-source-release.zip

Staged web site:
http://maven.apache.org/plugins-archives/maven-war-plugin-LATEST/

Vote open for 72H
[+1]
[0]
[-1]


--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven War plugin 2.4

[Olivier Lamy]

2013/7/5 sebb :
> On 5 July 2013 12:48, Olivier Lamy  wrote:
>> Hi,
>> I'd like to release Apache Maven War Plugin 2.4.
>>
>> We fixed 10 issue
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&projectId=11150
>>
>> Staging repository: 
>> https://repository.apache.org/content/repositories/maven-105
>>
>> Source release:
>> https://repository.apache.org/content/repositories/maven-105/org/apache/maven/plugins/maven-war-plugin/2.4/maven-war-plugin-2.4-source-release.zip
>>
>> Staged web site:
>> http://maven.apache.org/plugins-archives/maven-war-plugin-LATEST/
>
> SVN Tag + revision?
>
> Link to KEYS file?

already answered see http://markmail.org/message/crdfbuipblwly4mv

And as already answered our release procedure is described here:
http://maven.apache.org/developers/release/releasing.html

>
>> Vote open for 72H
>> [+1]
>> [0]
>> [-1] X
>
> The list of options normally looks like this:
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> which makes it easier to vote.
>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven War plugin 2.4

[Olivier Lamy]

My +1.


2013/7/5 Olivier Lamy :
> Hi,
> I'd like to release Apache Maven War Plugin 2.4.
>
> We fixed 10 issue
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&projectId=11150
>
> Staging repository: 
> https://repository.apache.org/content/repositories/maven-105
>
> Source release:
> https://repository.apache.org/content/repositories/maven-105/org/apache/maven/plugins/maven-war-plugin/2.4/maven-war-plugin-2.4-source-release.zip
>
> Staged web site:
> http://maven.apache.org/plugins-archives/maven-war-plugin-LATEST/
>
> Vote open for 72H
> [+1]
> [0]
> [-1]
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[RESULT] [VOTE] Apache Maven War plugin 2.4

[Olivier Lamy]

The vote has passed with the following result:
+1 (binding): Hervé, Robert, Stéphane, Olivier
+1 (non binding): Baptiste
-1 (non binding): sebb

I will continue the release process.

Cheers,
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Spurious file in Apache Maven War plugin 2.4 reelease candidate - broken release process?

[Olivier Lamy]

2013/7/7 sebb :
> On 6 July 2013 19:53, John Casey  wrote:
>> Hmm, actually, from running a few builds of the source-release archive, I
>> can see that the unit tests appear to be creating the
>> ${basedir}/maven-archive/ directory. I wonder if this has to do with
>> incomplete configuration of the test harness?
>
> Looks like:
>
> http://svn.apache.org/r1498096
>
> was supposed to fix this; seems to be in the release candidate but
> looks like the fix did not work.

ah yes. Strange I will have a look for next release. Grhh this file is
in svn:ignore property so svn st didn't detect that.

I noticed javadoc plugin source release has the same issue with a file
called javadoc-options-javadoc-resources.xml which must not be in
here.


>
>> In any case, I can see why the source-release assembly did the wrong thing
>> here; it's not in target, so not really expected to be a generated file.
>
> Yes, that is basically the point I made early on else-thread.
> I said that the release process did not guarantee that the source
> archive would contain exactly the correct files - no more, no less.
>
> The issue here is not that this particular file found its way into the
> source archive.
> Luckily the file looks to be harmless. It might not be next time.
> The point is that the the release process is not infallible (in spite
> of what people have stated).
>
> Every so often, a vote reviewer needs to check that the source output
> from the build process agrees with the source input.
> If a discrepancy is found, it can be investigated and fixed.
>
> But the important thing to take from this is that the current release
> vote checking process could (and should) be improved.
>
>>
>> On 7/6/13 1:35 PM, John Casey wrote:
>>>
>>> On 7/6/13 11:28 AM, sebb wrote:
>>>>
>>>> The curent release candidate for Apache Maven War plugin 2.4 contains
>>>> the following file in the source zip:
>>>>
>>>> maven-archiver/pom.properties
>>>>
>>>> The file is not in SVN or the source jar
>>>> As far as I can tell it does not belong in the source zip.
>>>>
>>>> The file is unlikely to do any harm, however the fact that it somehow
>>>> has crept into the source archive points to a problem with the release
>>>> process.
>>>>
>>>> The file is present in all the WAR source zips back to 2.1 (previously
>>>> there were no source archives)
>>>> AFAICT these WAR source archives were built by several different people.
>>>>
>>>> It does not seem to be present in sources for the few other plugin
>>>> sources that I checked.
>>>>
>>>> So why does the file end up in the WAR source archive?
>>>>
>>>> What is broken?
>>>
>>>
>>> I'd be surprised if you didn't find the same file in other
>>> source-release archives. I'm guessing it's an exclusion that's missing
>>> from the source-release.xml assembly descriptor that we use to construct
>>> these archives.
>>>
>>>>
>>>> I found the problem by comparing the source archive with the SVN tag.
>>>>
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>
>>>
>>>
>>
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> GitHub - http://github.com/jdcasey
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: svn commit: r1500550 - /maven/archetype/trunk/pom.xml

[Olivier Lamy]

this means archetype will be 1.6 required
(http://commons.apache.org/proper/commons-io/).
Is it the goal?

2013/7/8  :
> Author: aheritier
> Date: Sun Jul  7 23:21:09 2013
> New Revision: 1500550
>
> URL: http://svn.apache.org/r1500550
> Log:
> Update commons-io 2.2 -> 2.4
>
> Modified:
> maven/archetype/trunk/pom.xml
>
> Modified: maven/archetype/trunk/pom.xml
> URL: 
> http://svn.apache.org/viewvc/maven/archetype/trunk/pom.xml?rev=1500550&r1=1500549&r2=1500550&view=diff
> ==
> --- maven/archetype/trunk/pom.xml (original)
> +++ maven/archetype/trunk/pom.xml Sun Jul  7 23:21:09 2013
> @@ -146,7 +146,7 @@ under the License.
>
>  commons-io
>  commons-io
> -2.2
> +    2.4
>
>
>  org.codehaus.plexus
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [RESULT] [VOTE] Apache Maven War plugin 2.4

[Olivier Lamy]

FYI.
I hit the release button on repository.a.o but that's still not synced
so waiting before sending announce email.

2013/7/7 Olivier Lamy :
> The vote has passed with the following result:
> +1 (binding): Hervé, Robert, Stéphane, Olivier
> +1 (non binding): Baptiste
> -1 (non binding): sebb
>
> I will continue the release process.
>
> Cheers,
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: maven-release-manager/src/main/components-fragment.xml

[Olivier Lamy]

see the pom: 
http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/pom.xml

plexus-maven-plugin merge the content
I agree that's not the usual place :-)

2013/7/9 Chris Graham :
> Hi All.
>
> The full path is:
> http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/components-fragment.xml
>
> Can someone please explain to me how this file is used (and why it's not
> under the META-INF/plexus dir [at the very least]) ?
>
> I'm struggling to see how it is incorporated into the build.
>
> Also why -fragments? it's a complete XML file...
>
> -Chris



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[ANN] Apache Maven War Plugin 2.4 Released

[Olivier Lamy]

The Apache Maven team is pleased to announce the release of the Apache
Maven War Plugin, version 2.4

The WAR Plugin is responsible for collecting all artifact
dependencies, classes and resources of the web application and
packaging them into a web application archive.

http://maven.apache.org/plugins/maven-war-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-war-plugin
  2.4


Release Notes - Apache Maven 2.x WAR Plugin - Version 2.4

** Bug
* [MWAR-128] - war goal does not copy empty directories from
webapp directory
* [MWAR-192] - Conflict with workspace resoutlion in m2eclipse
* [MWAR-258] - Filtering of webResources stops on @ character
* [MWAR-267] - Maven WAR plugin does not copy dependencies of type
"bundle" into WEB-INF/lib
* [MWAR-280] - Big performance hit in overlay
* [MWAR-295] - weird icon on mac due awt toolkit setup
* [MWAR-296] - maven-war-plugin can cause multiple dependent lib
files with same snapshot version.

** Improvement
* [MWAR-269] - war fails to build while using m2e in workspace
resolution mode
* [MWAR-297] - Change default value for recompressZippedFiles to true

** New Feature
* [MWAR-298] - Make it possible to set warName form command line.


Have fun,
--
The Apache Maven team

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

Re: [VOTE] Apache 3.1.0

[Olivier Lamy]

+1

2013/7/7 Hervé BOUTEMY :
> +1
>
> works fine here
>
> Regards,
>
> Hervé
>
> Le dimanche 30 juin 2013 15:00:40 Jason van Zyl a écrit :
>> Here are the release bits for 3.1.0:
>>
>> Release notes:
>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
>> 967
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/maven-084/
>>
>> Staged distribution:
>> https://repository.apache.org/content/repositories/maven-084/org/apache/mave
>> n/apache-maven/3.1.0/
>>
>> Staged Site:
>> http://maven.apache.org/ref/3.1.0
>>
>> Thanks,
>>
>> Jason
>>
>> --
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> -
>>
>> There's no sense in being precise when you don't even know what you're
>> talking about.
>>
>>  -- John von Neumann
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Putting the distro in the release area

[Olivier Lamy]

done

2013/7/14 Jason van Zyl :
> Can someone with permissions execute:
>
> svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.1.0 
> https://dist.apache.org/repos/dist/release/maven/maven-3 -m 'o release maven 
> 3.1
> .0'
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> You are never dedicated to something you have complete confidence in.
> No one is fanatically shouting that the sun is going to rise tomorrow.
> They know it is going to rise tomorrow. When people are fanatically
> dedicated to political or religious faiths or any other kind of
> dogmas or goals, it's always because these dogmas or
> goals are in doubt.
>
>   -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
>
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Java version usage survey

[Olivier Lamy]

; -Chris
>> > >
>> > >
>> > > On Tue, Jul 16, 2013 at 4:19 PM, Arnaud Héritier
>> > > > > > >wrote:
>> > >
>> > > > Good point. I updated the survey to tell it is the Oracle JDK EOL
>> > > > Survey :
>> > > >
>> > > >
>> > >
>> > https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu
>> > gPmGW4/viewform
>> > > > Replies :
>> > > >
>> > > >
>> > >
>> > https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8Jhusu
>> > gPmGW4/viewanalytics
>> > > >
>> > > >
>> > > > On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham
>> > > > 
>> > > > wrote:
>> > > >
>> > > > > On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier <
>> > aherit...@gmail.com
>> > > > > >wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > >   Java 6 EOL was in feb and Maven and its plugins are always
>> > > compatible
>> > > > > >
>> > > > >
>> > > > > Oracle Java 6 was EOL'd.
>> > > > >
>> > > > > IBM Java 6 was, and is not due to be for a few more years. They
>> > > > > even
>> > > > > *extended* 1.5's life for a year. Sept this year, I think.
>> > > > >
>> > > > > -Chris
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > -
>> > > > Arnaud Héritier
>> > > > http://aheritier.net
>> > > > Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
>> > > >
>> > >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Java version usage survey

[Olivier Lamy]

2013/7/17 Stephen Connolly :
> On 16 July 2013 23:01, Arnaud Héritier  wrote:
>
>> >  >
>> >
>> > Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
>> > personal view) Maven job type will be unable to run 1.5
>> >
>> >
>> The crappy one which doesn't work with Maven 3.1.0 too (I tested it this
>> afternoon)
>>
>
> I'm sure Olivier will rush to try and defend that job type...

I prefer to keep my time to maybe update it to get it working with
3.1.x rather than waste my time on mailing list discussions.


>
>
>>
>>
>> > Can still keep trucking with a FreeStyle + Maven Build Step though (and I
>> > prefer that way anyway)
>> >
>> >
>> 
>> Me too if we backport features from the crappy maven integration into the
>> freestyle job (automatic dependencies, post build deployment ..).
>> What was done in Hudson was good from my point UI (excepted the GWT UI
>> which was ugly)
>> 
>>
>
> Ahem... there are other ways to skin this cat... but the people who know
> have been sworn to secrecy under pain of being shot, hung, drawn and
> quartered before having the entire troupé of Riverdance dance on their
> grave... so you'll just have to wait a month of so to find out!



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Enforcer version 1.3.1

[Olivier Lamy]

+1

2013/7/13 Robert Scholte :
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&styleName=Html&version=19426
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-140/
> https://repository.apache.org/content/repositories/maven-140/org/apache/maven/enforcer/enforcer/1.3.1/enforcer-1.3.1-source-release.zip
>
> Staging site:
> http://maven.apache.org/enforcer-archives/enforcer-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Java version usage survey

[Olivier Lamy]

2013/7/17 Olivier Lamy :
> 2013/7/17 Stephen Connolly :
>> On 16 July 2013 23:01, Arnaud Héritier  wrote:
>>
>>> >  >
>>> >
>>> > Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
>>> > personal view) Maven job type will be unable to run 1.5
>>> >
>>> >
>>> The crappy one which doesn't work with Maven 3.1.0 too (I tested it this
>>> afternoon)
>>>
>>
>> I'm sure Olivier will rush to try and defend that job type...
>
> I prefer to keep my time to maybe update it to get it working with
> 3.1.x rather than waste my time on mailing list discussions.
>

Apologize if the response looks rude.
I'm probably too upset to not have tested neither take care of that before...

First, I agree on the fact the Maven Integration in Jenkins is optimum
especially in the case of non backward compat change in maven core.
But now we have two options:
1. rewrite that but we have to build a compatibility layer for all
plugins using MavenReporter extension point (and maybe having
something to move datas to the new model) (probably something to
discuss on jenkins-dev@)
2. hack the current one to make it working with 3.1.x too

Perso, I don't have time for 1 (this can take a bit of time) (but I
have some ideas too :-)).
So at least we could take care of users and work on 2. (I already did
that for 3.0.x so I can again not sure for an other time :-))  (btw
thanks again to Hervé for the work on maven plugins!)



>
>>
>>
>>>
>>>
>>> > Can still keep trucking with a FreeStyle + Maven Build Step though (and I
>>> > prefer that way anyway)
>>> >
>>> >
>>> 
>>> Me too if we backport features from the crappy maven integration into the
>>> freestyle job (automatic dependencies, post build deployment ..).
>>> What was done in Hudson was good from my point UI (excepted the GWT UI
>>> which was ugly)
>>> 
>>>
>>
>> Ahem... there are other ways to skin this cat... but the people who know
>> have been sworn to secrecy under pain of being shot, hung, drawn and
>> quartered before having the entire troupé of Riverdance dance on their
>> grave... so you'll just have to wait a month of so to find out!
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Maven 3.1 - Stable ?

[Olivier Lamy]

2013/7/20 Paul Benedict :
> Herve, I noticed the release history uses a national date format that I
> don't recognize. I think the standard ISO date format of -MM-DD is most
> recognized by developers. What do you think? Is it worth changing?
>

Make sense sure! I will change it.
Ah those bloody french folks and their date format :-)

>
> On Fri, Jul 19, 2013 at 12:37 PM, Paul Benedict wrote:
>
>> Glad to see Maven 3.1 finally be listed on the home page as the preferred
>> version. But the release date is wrong; it's currently display the prior
>> 3.0.5 release date (23 February 2013).
>>
>>
>>
>> On Thu, Jul 18, 2013 at 2:10 PM, Hervé BOUTEMY wrote:
>>
>>> sure :)
>>>
>>> Le jeudi 18 juillet 2013 11:54:19 Jason van Zyl a écrit :
>>> > Am I staging and not publishing? Maybe that's why my stuff never comes
>>> up.
>>> >
>>> > On Jul 18, 2013, at 11:48 AM, Hervé BOUTEMY 
>>> wrote:
>>> > > I fixed the typo a few days ago, it was staged but not published
>>> > >
>>> > > I just published it, so the problem is not here any more
>>> > >
>>> > > Regards,
>>> > >
>>> > > Hervé
>>> > >
>>> > > Le jeudi 18 juillet 2013 12:29:54 Stephen Connolly a écrit :
>>> > >> Why is 3.1.0 labelled as 3.1.0-alpha-1 (and why have we two
>>> 3.1.0-alpha-1
>>> > >> labels... I expect the same answer)
>>> > >>
>>> > >> On 17 July 2013 21:01, Hervé BOUTEMY  wrote:
>>> > >>> Le mercredi 17 juillet 2013 14:13:38 Paul Benedict a écrit :
>>> > >>>> Is 3.0.5 still the preferred version? I ask because the right-hand
>>> > >>>> aside
>>> > >>>
>>> > >>> is
>>> > >>>
>>> > >>>> still "Get Maven 3.0.5" -- which makes sense if 3.1 is not GA, but
>>> I
>>> > >>>
>>> > >>> think
>>> > >>>
>>> > >>>> it is, right?
>>> > >>>>
>>> > >>>> PS: None of the release-notes.html pages include the release date.
>>> Can
>>> > >>>
>>> > >>> this
>>> > >>>
>>> > >>>> information be added (in the future)? It is difficult to determine
>>> how
>>> > >>>
>>> > >>> long
>>> > >>>
>>> > >>>> it has been since a prior release.
>>> > >>>
>>> > >>> I wrote http://maven.apache.org/docs/history.html recently exactly
>>> for
>>> > >>> this
>>> > >>> purpose
>>> > >>>
>>> > >>> Regards,
>>> > >>>
>>> > >>> Hervé
>>> > >>>
>>> > >>>
>>> > >>>
>>> -
>>> > >>> 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
>>> >
>>> > Thanks,
>>> >
>>> > Jason
>>> >
>>> > --
>>> > Jason van Zyl
>>> > Founder,  Apache Maven
>>> > http://twitter.com/jvanzyl
>>> > -
>>> >
>>> > Selfish deeds are the shortest path to self destruction.
>>> >
>>> >  -- The Seven Samuari, Akira Kurosawa
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Paul
>>
>
>
>
> --
> Cheers,
> Paul



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

[Olivier Lamy]

ary use in describing the
> +  origin of the Work and reproducing the content of the NOTICE file.
> +
> +   7. Disclaimer of Warranty. Unless required by applicable law or
> +  agreed to in writing, Licensor provides the Work (and each
> +  Contributor provides its Contributions) on an "AS IS" BASIS,
> +  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> +  implied, including, without limitation, any warranties or conditions
> +  of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
> +  PARTICULAR PURPOSE. You are solely responsible for determining the
> +  appropriateness of using or redistributing the Work and assume any
> +  risks associated with Your exercise of permissions under this License.
> +
> +   8. Limitation of Liability. In no event and under no legal theory,
> +  whether in tort (including negligence), contract, or otherwise,
> +  unless required by applicable law (such as deliberate and grossly
> +  negligent acts) or agreed to in writing, shall any Contributor be
> +  liable to You for damages, including any direct, indirect, special,
> +  incidental, or consequential damages of any character arising as a
> +  result of this License or out of the use or inability to use the
> +  Work (including but not limited to damages for loss of goodwill,
> +  work stoppage, computer failure or malfunction, or any and all
> +  other commercial damages or losses), even if such Contributor
> +  has been advised of the possibility of such damages.
> +
> +   9. Accepting Warranty or Additional Liability. While redistributing
> +  the Work or Derivative Works thereof, You may choose to offer,
> +  and charge a fee for, acceptance of support, warranty, indemnity,
> +  or other liability obligations and/or rights consistent with this
> +  License. However, in accepting such obligations, You may act only
> +  on Your own behalf and on Your sole responsibility, not on behalf
> +  of any other Contributor, and only if You agree to indemnify,
> +  defend, and hold each Contributor harmless for any liability
> +  incurred by, or claims asserted against, such Contributor by reason
> +  of your accepting any such warranty or additional liability.
> +
> +   END OF TERMS AND CONDITIONS
> +
> +   APPENDIX: How to apply the Apache License to your work.
> +
> +  To apply the Apache License to your work, attach the following
> +  boilerplate notice, with the fields enclosed by brackets "[]"
> +  replaced with your own identifying information. (Don't include
> +  the brackets!)  The text should be enclosed in the appropriate
> +  comment syntax for the file format. We also recommend that a
> +  file or class name and description of purpose be included on the
> +  same "printed page" as the copyright notice for easier
> +  identification within third-party archives.
> +
> +   Copyright [] [name of copyright owner]
> +
> +   Licensed under the Apache License, Version 2.0 (the "License");
> +   you may not use this file except in compliance with the License.
> +   You may obtain a copy of the License at
> +
> +   http://www.apache.org/licenses/LICENSE-2.0
> +
> +   Unless required by applicable law or agreed to in writing, software
> +   distributed under the License is distributed on an "AS IS" BASIS,
> +   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> +   See the License for the specific language governing permissions and
> +   limitations under the License.
>
> Added: maven/plugins/trunk/maven-install-plugin/NOTICE
> URL: 
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/NOTICE?rev=1505129&view=auto
> ==
> --- maven/plugins/trunk/maven-install-plugin/NOTICE (added)
> +++ maven/plugins/trunk/maven-install-plugin/NOTICE Sat Jul 20 12:58:34 2013
> @@ -0,0 +1,5 @@
> +Apache Maven Install Plugin
> +Copyright 2007-2013 The Apache Software Foundation
> +
> +This product includes software developed at
> +The Apache Software Foundation (http://www.apache.org/).
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

[Olivier Lamy]

Damned there are plenty of Apache projects which don't do that :-)

But in this case the plugin maven-remote-resources-plugin doesn't have
to be used anymore?
Because now we can have duplicate N&L with possible different content.
As one will be maintained manually which mean we can miss to add content etc...

But so


2013/7/21 Robert Scholte :
> From http://www.apache.org/dev/licensing-howto.html#source-tree-location
>
> "Location Within the Source Tree
>
> LICENSE and NOTICE belong at the top level of the source tree. They may be
> named LICENSE.txt and NOTICE.txt, but the bare names are preferred."
>
> If you consider a release root as the top level of the source tree, then
> they need to be placed here.
> And yes, I'm aware that they are already bundled with the binairy, but these
> lines are quite clear where these files are expected.
>
> Robert
>
> Op Sun, 21 Jul 2013 08:57:28 +0200 schreef Olivier Lamy :
>
>
>> why?
>> Is it mandatory? If yes I'd like to have some links.
>> AFAIK those files are generated.
>> This mean we will have to add those files for all artifacts we produce.
>> If one day the content change we will have to change all files in the
>> scm instead of only the plugin which generate that.
>>
>> Seriously?
>>
>> 2013/7/20  :
>>>
>>> Author: rfscholte
>>> Date: Sat Jul 20 12:58:34 2013
>>> New Revision: 1505129
>>>
>>> URL: http://svn.apache.org/r1505129
>>> Log:
>>> Add LICENSE and NOTICE files
>>>
>>> Added:
>>> maven/plugins/trunk/maven-install-plugin/LICENSE
>>> maven/plugins/trunk/maven-install-plugin/NOTICE
>>>
>>> Added: maven/plugins/trunk/maven-install-plugin/LICENSE
>>> URL:
>>> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129&view=auto
>>>
>>> ==
>>> --- maven/plugins/trunk/maven-install-plugin/LICENSE (added)
>>> +++ maven/plugins/trunk/maven-install-plugin/LICENSE Sat Jul 20 12:58:34
>>> 2013
>>> @@ -0,0 +1,202 @@
>>> +
>>> + Apache License
>>> +   Version 2.0, January 2004
>>> +http://www.apache.org/licenses/
>>> +
>>> +   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
>>> +
>>> +   1. Definitions.
>>> +
>>> +  "License" shall mean the terms and conditions for use,
>>> reproduction,
>>> +  and distribution as defined by Sections 1 through 9 of this
>>> document.
>>> +
>>> +  "Licensor" shall mean the copyright owner or entity authorized by
>>> +  the copyright owner that is granting the License.
>>> +
>>> +  "Legal Entity" shall mean the union of the acting entity and all
>>> +  other entities that control, are controlled by, or are under
>>> common
>>> +  control with that entity. For the purposes of this definition,
>>> +  "control" means (i) the power, direct or indirect, to cause the
>>> +  direction or management of such entity, whether by contract or
>>> +  otherwise, or (ii) ownership of fifty percent (50%) or more of the
>>> +  outstanding shares, or (iii) beneficial ownership of such entity.
>>> +
>>> +  "You" (or "Your") shall mean an individual or Legal Entity
>>> +  exercising permissions granted by this License.
>>> +
>>> +  "Source" form shall mean the preferred form for making
>>> modifications,
>>> +  including but not limited to software source code, documentation
>>> +  source, and configuration files.
>>> +
>>> +  "Object" form shall mean any form resulting from mechanical
>>> +  transformation or translation of a Source form, including but
>>> +  not limited to compiled object code, generated documentation,
>>> +  and conversions to other media types.
>>> +
>>> +  "Work" shall mean the work of authorship, whether in Source or
>>> +  Object form, made available under the License, as indicated by a
>>> +  copyright notice that is included in or attached to the work
>>> +  (an example is provided in the Appendix below).
>>> +
>>> +  "Derivative Works" shall mean any work, whether in Source or
>

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

[Olivier Lamy]

2013/7/21 sebb :
> On 21 July 2013 13:30, Robert Scholte  wrote:
>> "Also, the files change relatively rarely once set up."
>>
>> I thought you strongly believed in Murphy's Law...
>
> Not sure how that is relevant.
>
>>
>> I agree with Dennis: let's ask for the *facts* why these files are required
>> here.
>
> Robert already quoted this earlier in the thread:
> From http://www.apache.org/dev/licensing-howto.html#source-tree-location
>
> If you think that's wrong, it needs to be take up with Infra.

why infra? they decide about our licensing mode?

>
>> If it is because they need to be included in the source-release file,
>> then add them additionally instead of maintaining them per project.
>
> No, they need to be included in SCM as well.
>
> Since the SCM tree is basically what becomes the source archive, the
> same files will do for both.
> It's trivial to include the files in the source assembly descriptor so
> they become part of the source archive.
>
>>
>> Op Sun, 21 Jul 2013 14:17:12 +0200 schreef sebb :
>>
>>> On 21 July 2013 13:09, Dennis Lundberg  wrote:
>>>>
>>>> Hi
>>>>
>>>> Has anyone asked if we can use generated files instead?
>>>>
>>>> Many of the ASF rules are written by people that have not concidered the
>>>> fact that things such as these can be automated. Therefore many of these
>>>> rules are stated in a way that does not fit directly into the Maven way
>>>> of
>>>> doing things.
>>>
>>>
>>> And some things are not readily automateable - AFAIK there is no
>>> accuratate data from which to automate this.
>>> How do you track code imports with copyright statements? There are
>>> several different ways to treat these.
>>> Also, different licenses have different attribution requirements, and
>>> for ones that do require attribution it has to be determined from the
>>> license, which does not have a fixed format.
>>>
>>> Also, the files change relatively rarely once set up.
>>> Addition of 3rd party source or binaries to the archives is the main
>>> reason to change the N&L files.
>>>
>>>> We do include these files in "every Apache distribution" we make. It's
>>>> just
>>>> that we do not store them in SCM.
>>>>
>>>> --
>>>> Dennis Lundberg
>>>> Den 21 jul 2013 11:13 skrev "Robert Scholte" :
>>>>
>>>>> From http://www.apache.org/dev/**licensing-howto.html#source-**
>>>>>
>>>>> tree-location<http://www.apache.org/dev/licensing-howto.html#source-tree-location>
>>>>>
>>>>> "Location Within the Source Tree
>>>>>
>>>>> LICENSE and NOTICE belong at the top level of the source tree. They may
>>>>> be
>>>>> named LICENSE.txt and NOTICE.txt, but the bare names are preferred."
>>>>>
>>>>> If you consider a release root as the top level of the source tree, then
>>>>> they need to be placed here.
>>>>> And yes, I'm aware that they are already bundled with the binairy, but
>>>>> these lines are quite clear where these files are expected.
>>>>>
>>>>> Robert
>>>>>
>>>>> Op Sun, 21 Jul 2013 08:57:28 +0200 schreef Olivier Lamy
>>>>> >>>> >:
>>>>>
>>>>>  why?
>>>>>>
>>>>>> Is it mandatory? If yes I'd like to have some links.
>>>>>> AFAIK those files are generated.
>>>>>> This mean we will have to add those files for all artifacts we produce.
>>>>>> If one day the content change we will have to change all files in the
>>>>>> scm instead of only the plugin which generate that.
>>>>>>
>>>>>> Seriously?
>>>>>>
>>>>>> 2013/7/20  :
>>>>>>
>>>>>>> Author: rfscholte
>>>>>>> Date: Sat Jul 20 12:58:34 2013
>>>>>>> New Revision: 1505129
>>>>>>>
>>>>>>> URL: http://svn.apache.org/r1505129
>>>>>>> Log:
>>>>>>> Add LICENSE and NOTICE files
>>>>>>>
>>>>>>> Added:
>>>>>>> maven/plugins/trunk/maven-**install-plugin/LICENSE
>>>>>

Re: [maven-scm] add some debugging but still does not work locally on osx (665256d)

[Olivier Lamy]

Hi,
@Domi, we usually mailing list to communicate here.

So yes for some reasons I don't know, this fail on my laptop but work fine
on all others. (the famous: It doesn't work on my machine :-) )



2013/7/22 Dominik Bartholdi 

> @olamy <https://github.com/olamy> is there anyone we could ask for help
> on this? too sad we can't do a release soon...
>
> —
> Reply to this email directly or view it on 
> GitHub<https://github.com/apache/maven-scm/commit/665256d0534307b093b228b4117f8435fffdb17a#commitcomment-3682148>
> .
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+

[Olivier Lamy]

+1

2013/7/23 Stephen Connolly :
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> require to stick to the minimum Java requirements of that Maven Core
> version. In other words, if for example maven-compiler-plugin advertises
> compatibility with Maven Core 2.0.11+ then that will still need to be
> compiled targeting Java 1.4 and only using dependencies that are aligned
> with that runtime requirement.
>
> Additionally patch releases to existing releases of Maven Core will not be
> subject to this requirement.
>
> For example [example]*if* this vote passes and *if* on Sep 29th we release
> Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven
> 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security
> issue that affected all versions of Maven) then only Maven 3.3.0 would be
> require Java 6 as a minimum runtime requirement, the 2.0.12 release would
> still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would
> all still require Java 1.5.[/example]
>
> This is not a requirement that 3rd party plugins need use Java 6 as a
> minimum. Third party plugins are free to require any Java version >= the
> corresponding Maven minimum requirement, though obviously from a users
> perspective it is best if plugins try to adhere to our contracts for
> corresponding versions of Maven Core.
>
> Justification for the cut-off date:
>
> * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still
> extended and sustaining support for existing Oracle customers using Java 5)
> * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are
> still with support, but there are other Java vendors for other platforms)
> * Apple no longer supports any hardware that does not have at least an
> Apple Java 6 version available.
> * Red Hat is providing support for OpenJDK 6
> * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available.
>
> As I see it, that essentially ensures that for the vast majority of
> platforms there is a very strong likelihood of a Java 6 compatible version
> of Java available for that platform. Toolchains support or forking of the
> compiler and surefire can provide support for users who still need to build
> with older versions of Java (e.g., as was the case for Java 1.4.2 with
> Maven 2.2.1). Additionally users who are forced to use a java version older
> than Java 6 also are likely unable to upgrade their version of Maven, so
> this change will not affect them
>
> This vote is open for 72 hours. A minimum of three +1 binding votes (i.e.
> from the PMC) and the majority of votes cast from committers will be
> required to pass this vote.
>
> +1000: Yes, and when can we have the vote to go for Java 7 as a minimum?
> (This option is equivalent to +1 but provides people the ability to
> indicate an additional preference while not contributing to the inevitible
> noise)
> +1: Yes
> 0: No opinion
> -1: No
>
> -Stephen



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Model Converter version 2.3

[Olivier Lamy]

+1

2013/7/24 Dennis Lundberg :
> Hi,
>
> This will be the final release of this shared component. After this
> release it will retire from the Apache Maven project and move to the
> Apache Archiva project. See separate vote thread about that.
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14389
>
> There are no issues left in JIRA (except for the one to retire, which
> I'll close later):
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&component=13272&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-010/
> https://repository.apache.org/content/repositories/maven-010/org/apache/maven/shared/maven-model-converter/2.3/maven-model-converter-2.3-source-release.zip
>
> Staging site (not synced yet):
> http://maven.apache.org/shared-archives/maven-model-converter-2.3/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven IDEA Plugin version 2.2.1

[Olivier Lamy]

+1

2013/7/24 Dennis Lundberg :
> Hi,
>
> This is the final release of this plugin. After this release it will
> be retired, see separate vote thread for more info on that.
>
> We solved 1 issue:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135&styleName=Html&version=14478
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11135&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-008/
> https://repository.apache.org/content/repositories/maven-008/org/apache/maven/plugins/maven-idea-plugin/2.2.1/maven-idea-plugin-2.2.1-source-release.zip
>
> For those interested, the SCM URL can be found in the pom.xml that is
> in the staging repo.
>
> Staging site:
> http://maven.apache.org/plugins-archives/maven-idea-plugin-2.2.1/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Images in table not properly rendered

[Olivier Lamy]

Hi,
Simply create an issue here http://jira.codehaus.org/browse/DOXIA and
attach your patch.

2013/7/24 Mark Schenk :
> All,
>
>
>
> In noticed that images within tables are not properly rendered, for example:
>
>
>
> ||Symbol||Description||
>
> |!images/symbol.png!|text|
>
>
>
> Doesn’t result in an image shown in the table cell. After investigation I
> found out that the renderer of the table (TableBlockParser) only applies the
> ParagraphBlockParser and not other parsers like SectionBlockParser,
> FigureBlockParser, and ListBlockParser.
>
>
>
> To fix this I created the included patch. With this patch applied to version
> 1.4 of Doxia the example as shown above was properly parsed.
>
>
>
> Hope this patch can make it in any form to the new release to Doxia
> confluence module.
>
>
>
> Cheers,
>
> Mark Schenk
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Plugin testing

[Olivier Lamy]

2013/7/23 Jason van Zyl :
> Hi,
>
> I updated the plugin-testing tools to work with Maven 3.1.0 to help Manfred 
> get the Android Maven Plugin's test harness working with 3.1.0. A couple 
> things:
>
> 1. There is an @Override for a method implemented for an interface which you 
> can only start doing in Java 1.6 and the compiler was defaulting to 1.5 
> because no target/source were being specific. So I'm not sure if this is a 
> mistake but I set the source/target to 1.6 so that I didn't have to remove 
> the annotation.
>
> 2. I should probably bump the version to 3.0.0-SNAPSHOT instead of the 
> 2.2-SNAPSHOT, any thoughts here?

sounds good due to the change.

>
> 3. And now that I'm working on this I'd like to get it out of Subversion and 
> push it over to Git, any objections? I'd prefer to do that before making a 
> branch for the older version.
>

No objection from me.

> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> Script timed out
>
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: What are the current SCM locations for our Maven 2 branches

[Olivier Lamy]

2013/7/26 Dennis Lundberg :
> Hi
>
> I'm setting up builds in a local Jenkins to run RAT on all our release roots.
>
> I've gotten to Maven 2 now and have some problems on where to get it from...
>
> 2.0.x seems to be here:
> https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/
>
> 2.2.x is both here
> https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x/
> and here:
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/maven-2.2.x
>
> I couldn't find a GIT-MOVE.txt file in SVN for 2.2.x (like we have for
> the other sub projects that have moved to git) and the Jenkins job for
> it at builds.apache.org uses the Subversion URL.
>
> Can someone shed som light on this?

should be on git now.
I fixed the jenkins build.


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



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: maven-scm-provider-jgit

[Olivier Lamy]

lucky :-)

Here
mvn clean install -pl :maven-scm-provider-jgit -am

Results :

Failed tests:
testChangeLogCommand(org.apache.maven.scm.provider.git.jgit.command.changelog.JGitChangeLogCommandTckTest):
expected:<1> but was:<0>

Tests run: 9, Failures: 1, Errors: 0, Skipped: 0


For some reason when "walking" in the revs the filter receive a
RevCommit with a commit time of 0. So doesn't work with the filtering
by date.



2013/8/8 Brett Porter :
> Works here:
>
> maven-scm-provider-jgit (master=)$ mvn clean install -Ptck
>
> Results :
>
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
>
> - Brett
>
> On 08/08/2013, at 7:12 AM, domi  wrote:
>
>> Hi everyone,
>>
>> a couple of weeks ago I have contributed a git scm provider based on jgit. 
>> This one was pulled into the master branch by Olivier Lamy:
>>
>> Origin: git://git.apache.org/maven-scm.git
>> Mirror: https://github.com/apache/maven-scm
>> https://github.com/apache/maven-scm/tree/master/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit
>>
>> All the tests work fine, except for one single test which fails on one 
>> single Mac of Olivier - on all other test systems it works fine.
>> As its hard to debug something which we can't really reproduce, I'm asking 
>> for some support on this list. I don't even know
>> what exactly fails - so if you could just checkout the repo and run a build 
>> on it and tell us if it fails, that would already be of value.
>>
>> I hope we can solve this issue soon and do a release with the new 
>> scm-provider - I'm really waiting for this.
>>
>> regards Domi
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> --
> Brett Porter   @brettporter
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: maven-scm-provider-jgit

[Olivier Lamy]

2013/8/8 Olivier Lamy :
> lucky :-)
>
> Here
> mvn clean install -pl :maven-scm-provider-jgit -am
>
> Results :
>
> Failed tests:
> testChangeLogCommand(org.apache.maven.scm.provider.git.jgit.command.changelog.JGitChangeLogCommandTckTest):
> expected:<1> but was:<0>
>
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0
>
>
> For some reason when "walking" in the revs the filter receive a
> RevCommit with a commit time of 0. So doesn't work with the filtering
> by date.
>

code is here: 
https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blob;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/src/main/java/org/apache/maven/scm/provider/git/jgit/command/JGitUtils.java;h=dabcf022a695e4e96ce68d8742103868fe59a926;hb=HEAD#l354

so this time it's IDWOMM ! (not very usual :-) )

>
>
> 2013/8/8 Brett Porter :
>> Works here:
>>
>> maven-scm-provider-jgit (master=)$ mvn clean install -Ptck
>>
>> Results :
>>
>> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
>>
>> - Brett
>>
>> On 08/08/2013, at 7:12 AM, domi  wrote:
>>
>>> Hi everyone,
>>>
>>> a couple of weeks ago I have contributed a git scm provider based on jgit. 
>>> This one was pulled into the master branch by Olivier Lamy:
>>>
>>> Origin: git://git.apache.org/maven-scm.git
>>> Mirror: https://github.com/apache/maven-scm
>>> https://github.com/apache/maven-scm/tree/master/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit
>>>
>>> All the tests work fine, except for one single test which fails on one 
>>> single Mac of Olivier - on all other test systems it works fine.
>>> As its hard to debug something which we can't really reproduce, I'm asking 
>>> for some support on this list. I don't even know
>>> what exactly fails - so if you could just checkout the repo and run a build 
>>> on it and tell us if it fails, that would already be of value.
>>>
>>> I hope we can solve this issue soon and do a release with the new 
>>> scm-provider - I'm really waiting for this.
>>>
>>> regards Domi
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>> --
>> Brett Porter   @brettporter
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>>
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: maven-scm-provider-jgit

[Olivier Lamy]

Here:

mb-olamy:maven-scm olamy$ mvn -v
Apache Maven 3.1-SNAPSHOT (7bb5f1957a3bd9ee8357f8ddaee6f61e975ae954;
2013-07-05 22:50:43+1000)
Maven home: /Users/olamy/softs/maven/trunk
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"




On 9 August 2013 13:25, domi  wrote:
> The versions I used are:
>
> elongatus:resources domi$ java -version
> java version "1.6.0_45"
> Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
> elongatus:resources domi$ mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /usr/share/maven
> Java version: 1.6.0_45, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
> elongatus:resources domi$
>
>
> On 08.08.2013, at 11:26, Baptiste MATHUS  wrote:
>
>> Maybe there's a difference between java/maven versions in use?
>>
>> Where does it [not] work? Olivier? Domi, what was the version you
>> tested/dev'd it against?
>>
>>
>> 2013/8/8 Stephen Connolly 
>>
>>> On 8 August 2013 02:12, Olivier Lamy  wrote:
>>>
>>>> mvn clean install -pl :maven-scm-provider-jgit -am
>>>
>>>
>>> works on my mac
>>>
>>> --
>>> Baptiste  MATHUS - http://batmat.net
>>> Sauvez un arbre,
>>> Mangez un castor ! nbsp;!
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: What is the correct Git SCM URL for a branch?

[Olivier Lamy]

On 10 August 2013 21:12, Dennis Lundberg  wrote:
> Hi,
>
> I'm looking at the sources for Maven core in Git, which I'm learning
> as I go along.
>
> "master" is at version 3.1.1-SNAPSHOT and has this in its pom.xml
>   
> 
> scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
> 
> scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
> https://git-wip-us.apache.org/repos/asf?p=maven.git
> HEAD
>   
>
> The head "maven-3.0.x" is at version 3.0.6-SNAPSHOT and has this in its 
> pom.xml
>   
> 
> scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
> 
> scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
> https://git-wip-us.apache.org/repos/asf?p=maven.git
> HEAD
>   
>
> Since this is identical to what is in "master" I don't think this
> would work if you tried to do a release using the Release Plugin.
> Wouldn't that release what is specified in  i.e. "HEAD". Now, I
> have looked through our documentation and used Google to find a
> solution, but to no avail. From what I have gathered we should change
> the value of , but to what? Would it involve
> "ref/heads/maven-3.0.x"?
>
> The head "maven-2.2.x" is at version 2.2.2-RC1-SNAPSHOT and has this
> in its pom.xml
>   
> 
> scm:svn:http://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x
> 
> scm:svn:https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x
> http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x
>   
>
> Obviously this has not been updated since the move to Git, which is
> one of the things I'm trying to fix.

scm url will be the same for all branches.
It simply depend of the branch you are working on locally.
btw the HEAD in maven-3.0.x branch is wrong.
IHMO It's something to improve in the release plugin to put here the
current branch in use.

>
> Hopefully someone who has made a release using Maven Release Plugin
> from a Git branch can shed some light on this.
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: What is the correct Git SCM URL for a branch?

[Olivier Lamy]

On 10 August 2013 23:06, Fred Cooke  wrote:
> Please keep such information leakage optional. The editing of, and indeed
> adding of, the "tag" element by the release plugin should already be
> optional IMO.

Why?
With such information I know which tag has been used to build
artifacts. ( 
http://repo.maven.apache.org/maven2/org/apache/maven/maven/3.0.5/maven-3.0.5.pom
)
Without this it's not possible with only the git url.
For people/tools using scm informations for rebuilding packages etc..
it can be very interesting.


>Especially if it breaks formatting of the POM, which it does
> in some cases, at least. And yeah, I know why, and I know it's not a
> trivial fix. (Thanks to Robert for educating me many months ago).
>
> On Sat, Aug 10, 2013 at 2:54 PM, Olivier Lamy  wrote:
>
>> On 10 August 2013 21:12, Dennis Lundberg  wrote:
>> > Hi,
>> >
>> > I'm looking at the sources for Maven core in Git, which I'm learning
>> > as I go along.
>> >
>> > "master" is at version 3.1.1-SNAPSHOT and has this in its pom.xml
>> >   
>> > scm:git:
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> > scm:git:
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> > https://git-wip-us.apache.org/repos/asf?p=maven.git
>> > HEAD
>> >   
>> >
>> > The head "maven-3.0.x" is at version 3.0.6-SNAPSHOT and has this in its
>> pom.xml
>> >   
>> > scm:git:
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> > scm:git:
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> > https://git-wip-us.apache.org/repos/asf?p=maven.git
>> > HEAD
>> >   
>> >
>> > Since this is identical to what is in "master" I don't think this
>> > would work if you tried to do a release using the Release Plugin.
>> > Wouldn't that release what is specified in  i.e. "HEAD". Now, I
>> > have looked through our documentation and used Google to find a
>> > solution, but to no avail. From what I have gathered we should change
>> > the value of , but to what? Would it involve
>> > "ref/heads/maven-3.0.x"?
>> >
>> > The head "maven-2.2.x" is at version 2.2.2-RC1-SNAPSHOT and has this
>> > in its pom.xml
>> >   
>> > scm:svn:
>> http://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x
>> 
>> > scm:svn:
>> https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x
>> 
>> > http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x
>> 
>> >   
>> >
>> > Obviously this has not been updated since the move to Git, which is
>> > one of the things I'm trying to fix.
>>
>> scm url will be the same for all branches.
>> It simply depend of the branch you are working on locally.
>> btw the HEAD in maven-3.0.x branch is wrong.
>> IHMO It's something to improve in the release plugin to put here the
>> current branch in use.
>>
>> >
>> > Hopefully someone who has made a release using Maven Release Plugin
>> > from a Git branch can shed some light on this.
>> >
>> > --
>> > Dennis Lundberg
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: dev-h...@maven.apache.org
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Mapping version 1.0

[Olivier Lamy]

+1

On 11 August 2013 09:09, Dennis Lundberg  wrote:
> Hi,
>
> This is a new shared component consisting of code from Maven WAR
> Plugin, that has been repackaged for reuse by other plugins.
>
> We solved 1 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=19526
>
> There no issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&component=16150&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-083/
> https://repository.apache.org/content/repositories/maven-083/org/apache/maven/shared/maven-mapping/1.0/maven-mapping-1.0-source-release.zip
>
> Staging site:
> http://maven.apache.org/shared-archives/maven-mapping-1.0/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Model Converter version 2.3

[Olivier Lamy]

On 15 August 2013 08:53, sebb  wrote:
> On 14 August 2013 21:21, Dennis Lundberg  wrote:
>> On Wed, Aug 14, 2013 at 10:47 AM, sebb  wrote:
>>
>>> On 13 August 2013 18:58, Dennis Lundberg  wrote:
>>> > On Tue, Aug 13, 2013 at 12:30 AM, sebb  wrote:
>>> >> On 12 August 2013 20:10, Jason van Zyl  wrote:
>>> >>>
>>> >>>>>
>>> >>>>> I have now read the threads that are referring to, and have not found
>>> >>>>> a single link to any ASF rule stating that we need to include these
>>> >>>>> things in a VOTE thread.
>>> >>>>
>>> >>>> So how do you propose that reviewers check the provenance of the files
>>> >>>> in the source release?
>>> >>>
>>> >>> Are you looking for files that are in a distribution that didn't come
>>> from source control? Everything else as far as provenance goes is covered.
>>> Errant content is a potential problem, but everything in a distribution
>>> should come from source control which no one has access to until they have
>>> a signed CLA on file.
>>> >>
>>> >> Yes. That is where the whole saga started.
>>> >>
>>> >> Proving provenance is why the SCM coordinates are needed for the vote.
>>> >>
>>> >> The SCM details may also be useful to discover files accidentally
>>> >> omitted from the source archive.
>>> >
>>> > You want to compare the contents of the *-source-release.zip with
>>> > something from SCM, to make nothing bad has crept into the source
>>> > bundle. So you need to know where in SCM you can find it. Have I
>>> > understood you correctly?
>>>
>>> It's vital to be able to link the files in the source release
>>> archive(s) to their origin in SCM.
>>>
>>> The provenance of any source files the ASF releases must be clearly
>>> traceable.
>>>
>>
>> This information is clearly traceable and available to anyone who wants to
>> review a release made by the Maven project. Our process uses the Release
>> Plugin, which will put the POM from the SCM tag in the staging directory
>> along with the source-release.zip. In that POM wou will find the URL to the
>> original sources in SCM.
>>
>
> As has already been pointed out, SVN tags are not immutable, so the
> tag name alone is not sufficient.

I think Stephen perfectly sum up the situation.
If you're not happy follow that.

But please STOP the troll!

Thanks!


>
>>
>>>
>>> >>> 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
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Dennis Lundberg
>>> >
>>> > -
>>> > 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
>>>
>>> --
>>> Dennis Lundberg 
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Maven Surefire Plugin version 2.16

[Olivier Lamy]

+1

On 12 August 2013 03:51, Andreas Gudian  wrote:
> Hi,
>
> We solved 13 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19331
>
> This release addresses some serious problems with character encodings in
> the test report XML files and adds a new Parallel Computer implementation
> to the JUnit 4.7+ provider, offering a bunch of new options and features
> around in-process parallel execution (submitted by Tibor17, thanks again!).
>
> There are still lots of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-085
> https://repository.apache.org/content/repositories/maven-085/org/apache/maven/plugins/maven-surefire-plugin/2.16/maven-surefire-plugin-2.16-sources.jar
> https://repository.apache.org/content/repositories/maven-085/org/apache/maven/plugins/maven-failsafe-plugin/2.16/maven-failsafe-plugin-2.16-sources.jar
> Source: https://git-wip-us.apache.org/repos/asf/maven-surefire.git tag
> surefire-2.16_vote-1
>
> Staging site:
> http://maven.apache.org/surefire-archives/maven-surefire-2.16/maven-surefire-plugin/index.html
> http://maven.apache.org/surefire-archives/maven-surefire-2.16/maven-failsafe-plugin/index.html
> http://maven.apache.org/surefire-archives/maven-surefire-2.16/maven-surefire-report-plugin/index.html
>
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Model Converter version 2.3

[Olivier Lamy]

On 15 August 2013 18:50, Jörg Schaible  wrote:
> Hi Oliver,
>
> Olivier Lamy wrote:
>
>> On 15 August 2013 08:53, sebb  wrote:
>>> On 14 August 2013 21:21, Dennis Lundberg  wrote:
>>>> On Wed, Aug 14, 2013 at 10:47 AM, sebb  wrote:
>>>>
>>>>> On 13 August 2013 18:58, Dennis Lundberg  wrote:
>>>>> > On Tue, Aug 13, 2013 at 12:30 AM, sebb  wrote:
>>>>> >> On 12 August 2013 20:10, Jason van Zyl  wrote:
>>>>> >>>
>>>>> >>>>>
>>>>> >>>>> I have now read the threads that are referring to, and have not
>>>>> >>>>> found a single link to any ASF rule stating that we need to
>>>>> >>>>> include these things in a VOTE thread.
>>>>> >>>>
>>>>> >>>> So how do you propose that reviewers check the provenance of the
>>>>> >>>> files in the source release?
>>>>> >>>
>>>>> >>> Are you looking for files that are in a distribution that didn't
>>>>> >>> come
>>>>> from source control? Everything else as far as provenance goes is
>>>>> covered. Errant content is a potential problem, but everything in a
>>>>> distribution should come from source control which no one has access to
>>>>> until they have a signed CLA on file.
>>>>> >>
>>>>> >> Yes. That is where the whole saga started.
>>>>> >>
>>>>> >> Proving provenance is why the SCM coordinates are needed for the
>>>>> >> vote.
>>>>> >>
>>>>> >> The SCM details may also be useful to discover files accidentally
>>>>> >> omitted from the source archive.
>>>>> >
>>>>> > You want to compare the contents of the *-source-release.zip with
>>>>> > something from SCM, to make nothing bad has crept into the source
>>>>> > bundle. So you need to know where in SCM you can find it. Have I
>>>>> > understood you correctly?
>>>>>
>>>>> It's vital to be able to link the files in the source release
>>>>> archive(s) to their origin in SCM.
>>>>>
>>>>> The provenance of any source files the ASF releases must be clearly
>>>>> traceable.
>>>>>
>>>>
>>>> This information is clearly traceable and available to anyone who wants
>>>> to review a release made by the Maven project. Our process uses the
>>>> Release Plugin, which will put the POM from the SCM tag in the staging
>>>> directory along with the source-release.zip. In that POM wou will find
>>>> the URL to the original sources in SCM.
>>>>
>>>
>>> As has already been pointed out, SVN tags are not immutable, so the
>>> tag name alone is not sufficient.
>>
>> I think Stephen perfectly sum up the situation.
>> If you're not happy follow that.
>>
>> But please STOP the troll!
>
> The Maven PMC has made clear, that it knows about the problems and want to
> ignore it. However, please understand that Sebb is playing devil's advocate
> here, because the same release process is used for other Apache projects
> where the PMCs will *not* ignore this flaws. Sebb is more or less pestering
> you, because he is tired of having the same discussions in projects where he
> *is* PMC and is therefore responsible for the release. So, it is a bit short
> sighted to declare him as troll, simply because you (the Maven PMC) decided
> to ignore the problem.

I declared the thread as a troll not someone and BTW I'm not english
native speaker so the troll word is not so rude for me :-)
If it was read as something rude and a sort of personal attack so I apologize.

I'm just tired by all of those threads.
As described by Stephen we provide what ASF rules need.
Perso I'm a volunteer here and I spend my spare time on writing code
here to help our users.
So my time here is limited and I prefer coding rather than waste my
time on non needed procedure steps.
So if someone want to add extra/over prodecure steps why not but in
these case tools must be provided to ease our life.
I'm a developer and yes maybe I tend to be lazy so I prefer
using/writing tools to avoid manual tasks :-).

That won't be too complicated as the src tarball contains the pom with
scm information.
But perso no time for that so I prefer to not feed troll when I don't
have time to 

Re: [VOTE] Release Maven Remote Resources Plugin 1.5

[Olivier Lamy]

+1

On 16 August 2013 06:14, Kristian Rosenvold
 wrote:
> +1 (Yeah, the vote)
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [RESULT] [VOTE] Release Maven Surefire Plugin version 2.16

[Olivier Lamy]

On 16 August 2013 17:43, Andreas Gudian  wrote:
> Hi,
>
> The vote has passed with the following result:
>
> +1 (binding): Kristian Rosenvold, Olivier Lamy, Stephen Connolly
> +1 (non binding): Andreas Gudian
>
> I will promote the artifacts to the central repo.
>
> @PMC: could one of you please put the source bundles to the dist area and
> file the release for the project report? Thanks!

done

>
> Andreas
>
>
> 2013/8/16 Andreas Gudian 
>
>> And here's my +1.
>>
>>
>> 2013/8/16 Stephen Connolly 
>>
>>> +1
>>>
>>> On Friday, 16 August 2013, Andreas Gudian wrote:
>>>
>>> > One more PMC vote would be great to get this over with... ;-)
>>> >
>>> >
>>> > Am Donnerstag, 15. August 2013 schrieb Olivier Lamy :
>>> >
>>> > > +1
>>> > >
>>> > > On 12 August 2013 03:51, Andreas Gudian >> 
>>> > >
>>> > > wrote:
>>> > > > Hi,
>>> > > >
>>> > > > We solved 13 issues:
>>> > > >
>>> > >
>>> >
>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19331
>>> > > >
>>> > > > This release addresses some serious problems with character
>>> encodings
>>> > in
>>> > > > the test report XML files and adds a new Parallel Computer
>>> > implementation
>>> > > > to the JUnit 4.7+ provider, offering a bunch of new options and
>>> > features
>>> > > > around in-process parallel execution (submitted by Tibor17, thanks
>>> > > again!).
>>> > > >
>>> > > > There are still lots of issues left in JIRA:
>>> > > >
>>> > >
>>> >
>>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
>>> > > >
>>> > > > Staging repo:
>>> > > > https://repository.apache.org/content/repositories/maven-085
>>> > > >
>>> > >
>>> >
>>> https://repository.apache.org/content/repositories/maven-085/org/apache/maven/plugins/maven-surefire-plugin/2.16/maven-surefire-plugin-2.16-sources.jar
>>> > > >
>>> > >
>>> >
>>> https://repository.apache.org/content/repositories/maven-085/org/apache/maven/plugins/maven-failsafe-plugin/2.16/maven-failsafe-plugin-2.16-sources.jar
>>> > > > Source: https://git-wip-us.apache.org/repos/asf/maven-surefire.gittag
>>> > > > surefire-2.16_vote-1
>>> > > >
>>> > > > Staging site:
>>> > > >
>>> > >
>>> >
>>> http://maven.apache.org/surefire-archives/maven-surefire-2.16/maven-surefire-plugin/index.html
>>> > > >
>>> > >
>>> >
>>> http://maven.apache.org/surefire-archives/maven-surefire-2.16/maven-failsafe-plugin/index.html
>>> > > >
>>> > >
>>> >
>>> http://maven.apache.org/surefire-archives/maven-surefire-2.16/maven-surefire-report-plugin/index.html
>>> > > >
>>> > > >
>>> > > > Guide to testing staged releases:
>>> > > >
>>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>> > > >
>>> > > > Vote open for 72 hours.
>>> > > >
>>> > > > [ ] +1
>>> > > > [ ] +0
>>> > > > [ ] -1
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Olivier Lamy
>>> > > Ecetera: http://ecetera.com.au
>>> > > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> > >
>>> > > -
>>> > > To unsubscribe, e-mail: 
>>> > > dev-unsubscr...@maven.apache.org
>>> > > For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>>> > >
>>> > >
>>> >
>>>
>>>
>>> --
>>> Sent from my phone
>>>
>>
>>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Adding support for new dependency mediation strategy

[Olivier Lamy]

No this has moved here:
http://git.eclipse.org/c/aether/aether-core.git/tree/aether-util/src/main/java/org/eclipse/aether/util/graph/transformer/NearestVersionSelector.java

The issue will be to configure maven core to use your new implementation.
That's "hardcoded" currently here [1].

--
Olivier

[1] 
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java;h=b7ed320158887cacbb48fa893b767ceedca3e028;hb=master#l107

On 20 August 2013 16:15, Vogt Bernd  wrote:
> Hi Phillip,
>
> take a look at NearestVersionConflictResolver [1] an surroundings.
>
> Regards,
> Bernd
>
>
> [1] 
> https://github.com/sonatype/sonatype-aether/blob/master/aether-util/src/main/java/org/sonatype/aether/util/graph/transformer/NearestVersionConflictResolver.java
>
>
>
> -Ursprüngliche Nachricht-
> Von: Phillip Hellewell [mailto:ssh...@gmail.com]
> Gesendet: Montag, 19. August 2013 20:12
> An: dev@maven.apache.org
> Betreff: Adding support for new dependency mediation strategy
>
> Hi all,
>
> I'd like to take a stab at adding support for Maven to be able to mediate 
> dependency conflicts using "highest version" strategy rather than "nearest 
> definition".
>
> I'll be happy if anyone can point me in the right direction on which source 
> files I'll need to modify, and any other guidance.  Also, how long do you 
> expect such a task would take for a competent developer?
>
> Finally, I'm curious to know what are the chances of a patch being accepted 
> when I'm done?  I'll of course do it in such a way that the default remains 
> "nearest definition", and this new strategy has to be enabled with a setting 
> in settings.xml or something.
>
> Thanks,
> Phillip Hellewell
>
> ---------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Installed/deployed pom with dependency in a profile

[Olivier Lamy]

Hi,
I have an issue I don't know how to fix :-(

The goal is to have a dependency on tools.jar.
This activated by a profile


  tools.jar
  

  ${java.home}/../lib/tools.jar

  
  

  openjdk
  tools
  1.6
  system
  ${java.home}/../lib/tools.jar

  


So all is fine at this point.

But now the installed/deployed pom add this dependency in the
dependencies section.
That's something I definitely don't want because the ${java.home} is
interpolated so except everybody use the same as me that won't work
and furthermore I don't need it for using this library.

Any idea?

Thanks
-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: This CI build doesn't look right

[Olivier Lamy]

On 20 August 2013 23:13, Jason van Zyl  wrote:
> I'm not sure what this "jdk-1.6-guice-from-google" build is but is referring 
> to the 1.5-S of MRR which is not being used anymore. Is this job valid?
>
> https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.6-guice-from-google/4/consoleFull

Cloning repository https://git-wip-us.apache.org/repos/asf/maven.git
git --version
git version 1.7.9.5
Fetching upstream changes from origin
Commencing build of Revision d0abbad1c22e7d10bfa401f8896b8a6439902850
(origin/guice-from-google)

so it's from a branch called guice-from-google
This branch use the last guice version released by google.


>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> We know what we are, but know not what we may be.
>
>   -- Shakespeare
>
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: This CI build doesn't look right

[Olivier Lamy]

On 21 August 2013 00:08, Jason van Zyl  wrote:
> Doesn't answer the question whether the job is valid. It's referencing 
> incorrect plugins and why would you consume the latest version of Guice and 
> not through Sisu?
>
Branch has been started while the plugin was in SNAPSHOT versio, I
just fixed that.

And because it's probably good to use an official version of Guice
rather than a fork.




> But in general I think we need to clean up the IT jobs:
>
> https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/
>
> Like the Windows and OSX builds there that haven't worked in 8 months and a 
> year. These are not helpful. I would just like to remove them.
>
> On Aug 20, 2013, at 6:18 AM, Olivier Lamy  wrote:
>
>> On 20 August 2013 23:13, Jason van Zyl  wrote:
>>> I'm not sure what this "jdk-1.6-guice-from-google" build is but is 
>>> referring to the 1.5-S of MRR which is not being used anymore. Is this job 
>>> valid?
>>>
>>> https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.6-guice-from-google/4/consoleFull
>>
>> Cloning repository https://git-wip-us.apache.org/repos/asf/maven.git
>> git --version
>> git version 1.7.9.5
>> Fetching upstream changes from origin
>> Commencing build of Revision d0abbad1c22e7d10bfa401f8896b8a6439902850
>> (origin/guice-from-google)
>>
>> so it's from a branch called guice-from-google
>> This branch use the last guice version released by google.
>>
>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> --
>>> Jason van Zyl
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> -
>>>
>>> We know what we are, but know not what we may be.
>>>
>>>  -- Shakespeare
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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
> -
>
> A language that doesn’t affect the way you think about programming is not 
> worth knowing.
>
>  -- Alan Perlis
>
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Installed/deployed pom with dependency in a profile

[Olivier Lamy]

On 20 August 2013 22:16, Arnaud Héritier  wrote:
> Transitively it won't be propagated AFAIK. You want to reuse it by
> inheritance (and from a Pom out of your current project) ?

?? No it's resolved.
Sample:
git clone https://code.google.com/r/alexeagle-guava/ guava
cd guava

guava module has a dependency to:

  
com.google.errorprone
error_prone_core
1.0
  

See the pom here:
https://oss.sonatype.org/content/repositories/comgoogleerrorprone-1000/com/google/errorprone/error_prone_core/1.0/error_prone_core-1.0.pom

He has a dependency to:


openjdk
tools
1.6
system

/usr/local/buildtools/java/jdk7-google-v5-32/jre/../lib/tools.jar



whereas the original pom (
https://code.google.com/p/error-prone/source/browse/core/pom.xml )
says:


  tools.jar
  


  ${java.home}/../lib/tools.jar

  
  

  openjdk
  tools
  1.6
  system
  ${java.home}/../lib/tools.jar

  


So except adding an exclusion to openjdk:tools it doesn't work.
which is pain

Any solutions for that?





> I always used / saw such system dep usage in low level module. I don't
> know how we could allow this but I already had such issue with the
> java.home interpolation in the past. It is annoying to not be able to
> control what we filter.
>
> -
> Arnaud
>
> Le 20 août 2013 à 13:43, Olivier Lamy  a écrit :
>
>> Hi,
>> I have an issue I don't know how to fix :-(
>>
>> The goal is to have a dependency on tools.jar.
>> This activated by a profile
>>
>>
>>  tools.jar
>>  
>>
>>  ${java.home}/../lib/tools.jar
>>
>>  
>>  
>>
>>  openjdk
>>  tools
>>  1.6
>>  system
>>  ${java.home}/../lib/tools.jar
>>
>>  
>>
>>
>> So all is fine at this point.
>>
>> But now the installed/deployed pom add this dependency in the
>> dependencies section.
>> That's something I definitely don't want because the ${java.home} is
>> interpolated so except everybody use the same as me that won't work
>> and furthermore I don't need it for using this library.
>>
>> Any idea?
>>
>> Thanks
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: maven-scm-provider-jgit

[Olivier Lamy]

grhhh
same with:
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-20
00:51:28+1100)
Maven home: /Users/olamy/softs/maven/apache-maven-3.0.5
Java version: 1.6.0_51, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"

maybe a jgit bug?

It looks I will have to use a vm to release that :-)

On 20 August 2013 06:21, domi  wrote:
> I tried again with the same maven and java version Olivier has used -
only Maven is a release version instead of the SNAPSHOT used by Olivier.
> @Olivier: can you have a try with a released Maven Version?
>
> elongatus:maven-scm domi$
/Users/domi/Downloads/apache-maven-3.1.0/bin/mvn -version
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-28
04:15:32+0200)
> Maven home: /Users/domi/Downloads/apache-maven-3.1.0
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
>
>
>
> On 10.08.2013, at 04:00, Olivier Lamy  wrote:
>
>> Here:
>>
>> mb-olamy:maven-scm olamy$ mvn -v
>> Apache Maven 3.1-SNAPSHOT (7bb5f1957a3bd9ee8357f8ddaee6f61e975ae954;
>> 2013-07-05 22:50:43+1000)
>> Maven home: /Users/olamy/softs/maven/trunk
>> Java version: 1.7.0_25, vendor: Oracle Corporation
>> Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
>>
>>
>>
>>
>> On 9 August 2013 13:25, domi  wrote:
>>> The versions I used are:
>>>
>>> elongatus:resources domi$ java -version
>>> java version "1.6.0_45"
>>> Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
>>> elongatus:resources domi$ mvn -version
>>> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
>>> Maven home: /usr/share/maven
>>> Java version: 1.6.0_45, vendor: Apple Inc.
>>> Java home:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>> Default locale: en_US, platform encoding: MacRoman
>>> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
>>> elongatus:resources domi$
>>>
>>>
>>> On 08.08.2013, at 11:26, Baptiste MATHUS  wrote:
>>>
>>>> Maybe there's a difference between java/maven versions in use?
>>>>
>>>> Where does it [not] work? Olivier? Domi, what was the version you
>>>> tested/dev'd it against?
>>>>
>>>>
>>>> 2013/8/8 Stephen Connolly 
>>>>
>>>>> On 8 August 2013 02:12, Olivier Lamy  wrote:
>>>>>
>>>>>> mvn clean install -pl :maven-scm-provider-jgit -am
>>>>>
>>>>>
>>>>> works on my mac
>>>>>
>>>>> --
>>>>> Baptiste  MATHUS - http://batmat.net
>>>>> Sauvez un arbre,
>>>>> Mangez un castor ! nbsp;!
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Making (sisu-)guice a provided scope dependency of Sisu?

[Olivier Lamy]

I believe Stuart just want to ease life of users consuming maven artifatcs
but prefer google guice rather than a fork ( preventing them having to
write too many exclusions xml elements and avoid having twice guice as a
dependency).
I think it's a good idea and doesn't prevent us using the version we prefer.

What is the problem for you exactly with such change?

--
Olivier
On Aug 23, 2013 2:26 PM, "Jason van Zyl"  wrote:

>
> On Aug 22, 2013, at 8:57 PM, Stuart McCulloch  wrote:
>
> > As one of the main downstream users of Sisu would you prefer it to
> declare
> > a provided scope dependency to (sisu-)guice rather than the current
> compile
> > scope dependency?
> >
>
> Not really.
>
> > Making it provided should make it easier to swap in alternative versions
> > while still documenting the dependency - and avoid lots of tedious
> > exclusions. The only downside I can see is that downstream users like the
> > Maven runtime would then need to explicitly remember to add the
> > (sisu-)guice dependency in their final application artifact/assembly (and
> > potentially in some tests) as it would no longer be transitively
> included.
> > (though that might be a good thing documentation-wise)
> >
> > WDYT?
>
> I think you understand what the requirements are, and we need the
> additional changes for it all to work well. I don't think it's very
> practical to accommodate variants when we can't really use stock Guice.
> When all the patches are in, which you do your best to integrate, then we
> can switch. As the one doing the core releases right now I don't see any
> benefit of swapping in alternate versions.
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> Script timed out
>
>
>
>
>
>
>

Re: Why is wagon shaded in core ?

[Olivier Lamy]

it's shaded but not relocated.
What is the trouble?

On 2 September 2013 18:28, Kristian Rosenvold
 wrote:
> I understand that the deps of wagon need to be shaded, but why does
> the actual wagon code itself need to be shaded ?
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Making (sisu-)guice a provided scope dependency of Sisu?

[Olivier Lamy]

On 23 August 2013 17:07, Jason van Zyl  wrote:
>
> On Aug 22, 2013, at 9:58 PM, Olivier Lamy  wrote:
>
>> I believe Stuart just want to ease life of users consuming maven artifatcs
>> but prefer google guice rather than a fork ( preventing them having to
>> write too many exclusions xml elements and avoid having twice guice as a
>> dependency).
>> I think it's a good idea and doesn't prevent us using the version we prefer.
>>
>> What is the problem for you exactly with such change?
>>
>
> Ultimately I don't think it's useful. No user cares what version of Guice is 
> used, they care that the distribution works.
>

I said "users consuming maven artifatcs" which is different from final
Apache Maven users.

> If you have a philosophical objection to using a fork then I think a more 
> practical use of time is to help Stuart remove any of the differences between 
> our fork and stock Guice. I believe Stuart has done everything he can to 
> remove those differences. What differences remain are those he feels are of 
> benefit to Maven.
>
> I'm doing the core releases right now and I'm not going to put stock Guice in 
> the distribution, I'm going to use sisu-guice so I think it's fine the way it 
> is.
>

Did I talk about changing something in the Apache Maven distribution?
I believe no.

My use case is only for users (read devs) who consume Apache Maven
artifacts and already use non forked Guice and prefer this one.

So the Stuart proposition sounds good.



>> --
>> Olivier
>> On Aug 23, 2013 2:26 PM, "Jason van Zyl"  wrote:
>>
>>>
>>> On Aug 22, 2013, at 8:57 PM, Stuart McCulloch  wrote:
>>>
>>>> As one of the main downstream users of Sisu would you prefer it to
>>> declare
>>>> a provided scope dependency to (sisu-)guice rather than the current
>>> compile
>>>> scope dependency?
>>>>
>>>
>>> Not really.
>>>
>>>> Making it provided should make it easier to swap in alternative versions
>>>> while still documenting the dependency - and avoid lots of tedious
>>>> exclusions. The only downside I can see is that downstream users like the
>>>> Maven runtime would then need to explicitly remember to add the
>>>> (sisu-)guice dependency in their final application artifact/assembly (and
>>>> potentially in some tests) as it would no longer be transitively
>>> included.
>>>> (though that might be a good thing documentation-wise)
>>>>
>>>> WDYT?
>>>
>>> I think you understand what the requirements are, and we need the
>>> additional changes for it all to work well. I don't think it's very
>>> practical to accommodate variants when we can't really use stock Guice.
>>> When all the patches are in, which you do your best to integrate, then we
>>> can switch. As the one doing the core releases right now I don't see any
>>> benefit of swapping in alternate versions.
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> --
>>> Jason van Zyl
>>> Founder,  Apache Maven
>>> http://twitter.com/jvanzyl
>>> -
>>>
>>> Script timed out
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> Script timed out
>
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Wagon & PRoxy auth ??

[Olivier Lamy]

Yup someone (me) miss to remove this deprecated call.
I will fix that now.


On 3 September 2013 15:42, Kristian Rosenvold
 wrote:
> While looking at the access denied problem for wagon, I ran into this code
> line:
>
> https://github.com/apache/maven-wagon/blob/master/wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/AbstractHttpClientWagon.java#L740
>
> The call uses a deprecated version of "authenticated" that regenerates the
> BasicHttpContext every time.
> The new (not deprecated) version would seem to be just
>
> Header bs = new BasicScheme().authenticate( creds,
> httpMethod, localContext );
>
> (Where we add the existing localContext variable)
>
> I am a bit puzzled that the current code works with authenticated proxies
> at all, but this code is
> certainly not my domain. Is this a bug ?
>
> Kristian



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Maven ITs (embedded)

[Olivier Lamy]

testitMNG2201(org.apache.maven.it.MavenITmng2201PluginConfigInterpolationTest)
 Time elapsed: 0.603 sec  <<< FAILURE!
junit.framework.AssertionFailedError:
expected:
but 
was:

AFAICS unit test doesn't handle correctly symlinks.



On 8 September 2013 12:50, Jason van Zyl  wrote:
> Olivier,
>
> Not sure what the problem is exactly but look at the tests that are failing 
> but it looks like an issue where path names aren't identical but looks like 
> the same path. Do you know if anything changed on the instance lately?
>
> https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/core-integration-testing-maven-3-embedded/4969/console
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -----
>
>
>
>
>
>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Install Plugin version 2.5

[Olivier Lamy]

+1

On 7 September 2013 05:35, Robert Scholte  wrote:
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?styleName=Html&projectId=11136&version=18760
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11136&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-022/
> https://repository.apache.org/content/repositories/maven-022/org/apache/maven/plugins/maven-install-plugin/2.5/maven-install-plugin-2.5-source-release.zip
>
> Source release checksum(s):
> maven-install-plugin-2.5-source-release.zip sha1:
> 4c997aa314cd6dee54c4f44caf23b2ed4bca5e5c
>  md5: 2fdd4dc66ce64864be1e0d542fefe8e5
>
> Staging site:
> http://maven.apache.org/plugins-archives/maven-install-plugin-2.5
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Wagon version 2.5

[Olivier Lamy]

+1

On 12 September 2013 21:29, Tamás Cservenák  wrote:
> Hi,
>
> We solved 6 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&version=19092
>
> There are still a couple of issues left in JIRA:
> https://jira.codehaus.org/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-036/
> https://repository.apache.org/content/repositories/maven-036/org/apache/maven/wagon/wagon/2.5/wagon-2.5-source-release.zip
>
> Source release checksum:
> wagon-2.5-source-release.zip sha1: f0fca0335061d21ca1306298033299c244ea88f1
>
> Staging site:
> http://maven.apache.org/wagon-archives/wagon-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Thanks,
> ~t~



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Plugin testing release for 3.1.1

[Olivier Lamy]

Maybe can be release from svn.

On 13 September 2013 14:05, Manfred Moser  wrote:
> Hi!
>
> With the 3.1.1 release of Maven coming up hopefully soon I would like to
> move forward with the plugin testing harness using it as well. Jason fixed
> it to work with 3.0 and requested the repo to be moved from svn to git so
> he can release 2.2 over a month ago.
>
> It seems like nothing happen on the infra side of things. Can somebody
> take this up and get it done asap. Or could I get some sort of access
> (maybe through the committer school) to do it myself at Apache?
>
> Worst case I could of course just temporarily fork it into my namespace
> and use it in the android maven plugin but I would rather not waste my
> time on that.
>
> manfred
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: pull requests on github?

[Olivier Lamy]

both merged.
Thanks for your contribution!

On 24 September 2013 10:09, ryenus  wrote:
> Thank you Andreas.
>
> I've commented on that issue, with almost the same words I used here
> about the copyright/license stuff.
>
> Could someone please look at the patches instead of merely worrying
> about the license issue (there's no issue at all). They're very
> simple, and I have to wait to release my next version with separate
> jar/sources-jar/javadoc-jar differentiated via classifiers (for
> multiple jdk versions).
>
> Thank you
>
> On Mon, Sep 23, 2013 at 11:58 PM, ryenus  wrote:
>> @Stephen, @Daniel, sorry I didn't subscribe the ML so just read your
>> replies via markmail.org
>>
>> Regarding license, my github repo is simply a clone of
>> https://github.com/apache/maven-plugins, hence should inherit the same
>> license, and I kinda agree with Daniel that pull requests on github
>> are now defacto OSS contribution 'protocol' with enough implications
>> about the copyright grant stuff. Also a pull request is basically
>> saying, here is what I can give, you can either take it or abandon it,
>> at your own wish, of course, for the sake of goodness.
>>
>> Regarding JIRA tickets, I did create them accordingly in the first
>> place, you can see that the JIRA ticket IDs are included as prefixes
>> in pull requests titles, respectively. Also the JIRA tickets and GH
>> pull requests are now crossed linked to each other(s).
>>
>> About the 6 criteria Stephen mentioned
>>> 1. Does it have tests that fail when the bug is not fixed?
>> N/A, my PR's are more about enhancement
>>
>>> 2. Does it have tests that pass when the bug is fixed?
>> I haven't got the time to learn and write tests for these maven
>> plugins yet, for me it's mostly a matter of time and priority, which
>> highly depends on the business. However, I made the fixes only to
>> resolve real issues in my projects, see
>> https://github.com/ryenus/rop/blob/backport/pom.xml, checking the
>> tests you can see I'm a strong advocator of TDD as well.
>>
>> 3. Does it leave code formatting alone except for the lines that are
>> touched?
>> Yes
>>
>> 4. Does it apply cleanly?
>> Yes, GitHub now can automatically verify if a pull request can be
>> cleanly merged or not.
>>
>> 5. Is there a bug ID associated with the bug?
>> Yes, as mentioned above, JIRA tickets are created and cross linked to
>> the pull requests.
>>
>> 6. Is it super obvious that we can accept the contribution?
>> Yes, should be, it's very simple actually, even more so to maven developers.
>>
>>
>> On Mon, Sep 23, 2013 at 1:24 PM, ryenus  wrote:
>>> Would anyone be taking care of the pull requests on github:
>>>
>>> https://github.com/apache/maven-plugins/pulls
>>>
>>> I just made 2 but saw there're pull requests open for years.
>>>
>>> Thanks
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Subject: [VOTE] Release Apache Maven Deploy Plugin version 2.8

[Olivier Lamy]

+1

On 25 September 2013 06:04, Robert Scholte  wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11131&version=17634&styleName=Html
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11131&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-095/
> https://repository.apache.org/content/repositories/maven-095/org/apache/maven/plugins/maven-deploy-plugin/2.8/maven-deploy-plugin-2.8-source-release.zip
>
> Source release checksum(s):
> maven-deploy-plugin-source-release.zip sha1:
> 94620a9fc891efb075c2b61e164b30640b5bd908
>
> Staging site:
> http://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/index.html
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [ANN] Maven 3.1.1 Release

[Olivier Lamy]

For last release, I believe I used the easy/fast/lazy path to copy binaries
in the layout Jenkins knows.

--
Olivier
On Oct 15, 2013 7:31 AM, "jieryn"  wrote:

> Greetings,
>
> On Mon, Oct 14, 2013 at 4:24 PM, Brett Porter  wrote:
> > It's in the archive at the same location:
> https://archive.apache.org/dist/maven/maven-3/3.1.1/binaries/
>
> Thanks for that link.
>
> > I thought Jenkins had been updated for the new layout.
>
> As you can see from
> https://github.com/jenkinsci/backend-crawler/blob/master/ant_maven.groovy
> it does not appear to have been updated. And it doesn't look like it
> will easily play well with a nested directory structure.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [ANN] Maven 3.1.1 Release

[Olivier Lamy]

fixed.
Sorry I don't have time to change the Jenkins script so use a lazy mode.

On 15 October 2013 07:34, Olivier Lamy  wrote:
> For last release, I believe I used the easy/fast/lazy path to copy binaries
> in the layout Jenkins knows.
>
> --
> Olivier
>
> On Oct 15, 2013 7:31 AM, "jieryn"  wrote:
>>
>> Greetings,
>>
>> On Mon, Oct 14, 2013 at 4:24 PM, Brett Porter  wrote:
>> > It's in the archive at the same location:
>> > https://archive.apache.org/dist/maven/maven-3/3.1.1/binaries/
>>
>> Thanks for that link.
>>
>> > I thought Jenkins had been updated for the new layout.
>>
>> As you can see from
>> https://github.com/jenkinsci/backend-crawler/blob/master/ant_maven.groovy
>> it does not appear to have been updated. And it doesn't look like it
>> will easily play well with a nested directory structure.
>>
>> ---------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Welcome Bartholdi Dominik as a new committer

[Olivier Lamy]

Hi all,

Please welcome Bartholdi Dominik as a new committer of the Apache
Maven project. The Apache Maven PMC has voted to grant committership
to him.

The account have already been set up and he can begin working on the
Apache Maven code

Domi, welcome to the team !

Have Fun
--
The Apache Maven PMC

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

Re: [VOTE] Release Apache Maven Install Plugin version 2.5.1 and Apache Maven Deploy Plugin version 2.8.1

[Olivier Lamy]

2 * +1

On 15 October 2013 08:09, Robert Scholte  wrote:
> Hi,
>
> since the same type of issues have been fixed for both the Apache Maven
> Install Plugin and Apache Maven Deploy Plugin, I've decided to stage both
> plugins at once.
>
> We solved 2x2 issues:
> MINSTALL:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136&version=19574&styleName=Html
> MDEPLOY:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11131&version=19592&styleName=Html
>
> There are still a couple of issues left in JIRA:
> MINSTALL:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&11136=XXX&status=1
> MDEPLOY:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&11131=XXX&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-170/
> https://repository.apache.org/content/repositories/maven-170/org/apache/maven/plugins/maven-install-plugin/2.5.1/maven-install-plugin-2.5.1-source-release.zip
> https://repository.apache.org/content/repositories/maven-170/org/apache/maven/plugins/maven-deploy-plugin/2.8.1/maven-deploy-plugin-2.8.1-source-release.zip
>
> Source release checksum(s):
> maven-install-plugin-2.5.1-source-release.zip sha1:
> 11895c3e5fed3c30cd00a010c2d3a8dffa20aaa2
> maven-deploy-plugin-2.8.1-source-release.zip sha1:
> 8b9df3047ed417e255136eaaa402b192d1b65f58
>
> Staging site:
> http://maven.apache.org/plugins-archives/maven-install-plugin-2.5.1/
> http://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: plugin-testing release for 3.1.1

[Olivier Lamy]

I believe there is github fork mirror here:
https://github.com/apache/maven-plugin-testing/tree/trunk
So you can certainly create a pull request.


On 17 October 2013 04:36, Manfred Moser  wrote:
> Given its all in the git repo already.. do you want me to create a patch
> for whatever is in svn then? And maybe attach it to some jira issue or
> something?
>
> manfred
>
>> Any work that gets patches applied is valid work. You don't get commit
>> access if you are in the school, only a bunch of mentors who have commit
>> access to shout at if your patches are being ignored ;-)
>>
>> IOW self starters wanted ;-)
>>
>> On Wednesday, 16 October 2013, Manfred Moser wrote:
>>
>>> Hi!
>>>
>>> I have a fork of plugin-testing that works for 3.1.1 at
>>> https://github.com/mosabua/plugin-testing/tree/maven311
>>>
>>> It works fine and we currently use it for the android maven plugin
>>> master
>>> branch that is migrating to 3.1.1. Could someone please apply the
>>> patches
>>> back to the repo and release this project asap?
>>>
>>> Potentially I could do the work myself as well. Would this be a feasible
>>> approach for a first committer school work?
>>>
>>> manfred
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org 
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>> 
>>>
>>>
>>
>> --
>> Sent from my phone
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: Maven compiler options

[Olivier Lamy]

On 18 October 2013 03:26, Arnaud Héritier  wrote:
> Hi,
>
>   Today in my build I had the well known warning :
>
> [WARNING] x.java: x.java uses unchecked or unsafe operations.
> [WARNING] x.java: Recompile with -Xlint:unchecked for details.
>
>   Thus I updated my compiler plugin with
>
> 
>   
> 
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
> 
>   -Xlint:unchecked
> 
>   
> 
>   
> 
>
>   And it works while the documentation is saying
>
> http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgs
> Sets the arguments to be passed to the compiler """if fork is set to true
> ."""
>
>   Which isn't my case.
>
> [DEBUG]   (f) fork = false
>
>   Should we update the doc ? Do I miss something ?

Yes and no.
using javax.tools.$ has changed how it works for this.


>
>   Cheers
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

[VOTE] Apache Maven SCM 1.9

[Olivier Lamy]

Hi,
We fixed 9 issues. The new feature is the jgit provider (based on jgit).
Details: 
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783

Staging repository:
https://repository.apache.org/content/repositories/maven-027/
Staged site: http://maven.apache.org/scm-archives/scm-LATEST/

Sources release:
https://repository.apache.org/content/repositories/maven-027/org/apache/maven/scm/maven-scm/1.9/maven-scm-1.9-source-release.zip

Vote open for 72H

[+1]
[0]
[-1]


Thanks
-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Apache Maven SCM 1.9

[Olivier Lamy]

versions fixed in the site.


On 25 October 2013 06:56, domi  wrote:
> There are some small issues on the docu of jgit: 
> http://maven.apache.org/scm-archives/scm-LATEST/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
> - nativ -> native
> - Formatting of "Examples" + "changelog" titles
> - the versions in the snippets are wrong 1.8.1 -> 1.9
>
> I'm not sure if this has to be fixed before publish…
>
>
>
> On 24.10.2013, at 05:35, Olivier Lamy  wrote:
>
>> Hi,
>> We fixed 9 issues. The new feature is the jgit provider (based on jgit).
>> Details: 
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/maven-027/
>> Staged site: http://maven.apache.org/scm-archives/scm-LATEST/
>>
>> Sources release:
>> https://repository.apache.org/content/repositories/maven-027/org/apache/maven/scm/maven-scm/1.9/maven-scm-1.9-source-release.zip
>>
>> Vote open for 72H
>>
>> [+1]
>> [0]
>> [-1]
>>
>>
>> Thanks
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> 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 Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: SSH support for wagon-ssh [WAGON-403, PATCH]

[Olivier Lamy]

applied.
Thanks!

On 24 October 2013 09:27, Charles Duffy  wrote:
> Howdy, all --
>
> I have a patch attached to http://jira.codehaus.org/browse/WAGON-403 which
> adds support for using an SSH agent to authenticate with the native-Java
> provider (whereas previously this required the native provider, supporting
> scp but not sftp).
>
> This has been in the bugtracker for three weeks without feedback. Any
> chance I could get some notes with respect to any changes necessary for
> this to be accepted upstream?
>
>
> This was created as a work-for-hire by Indeed, Inc; we have a CCLA on file.
>
> Thanks,
> -- Charles Duffy
> char...@dyfis.net



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

Re: [VOTE] Release Apache Maven Release Plugin version 2.4.2

[Olivier Lamy]

+1

--
Olivier
On Oct 24, 2013 6:55 AM, "Robert Scholte"  wrote:

> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/**secure/ReleaseNote.jspa?**
> projectId=11144&version=19618&**styleName=Html
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/**secure/IssueNavigator.jspa?**
> reset=true&pid=11144&status=1
>
> Staging repo:
> https://repository.apache.org/**content/repositories/maven-**026/
> https://repository.apache.org/**content/repositories/maven-**
> 026/org/apache/maven/release/**maven-release/2.4.2/maven-**
> release-2.4.2-source-release.**zip
> Source release checksum(s):
> maven-release-2.4.2-source-**release.zip sha1:
> f9077fa71c4515241c37ce47f620c3**ada0c2f45f
>
> Staging site:
> http://maven.apache.org/maven-**release-archives/maven-**
> release-2.4.2/maven-release-**plugin/
>
> Guide to testing staged releases:
> http://maven.apache.org/**guides/development/guide-**testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@maven.apache.**org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Apache Maven SCM 1.9

[Olivier Lamy]

;>> file:///G:/apache/maven/git/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/target/scm-test/repository
>>>> [INFO] OK - RemoteRefUpdate[remoteName=refs/heads/test-branch, OK,
>>>> (null)...92f139dfec4d1dfb79c3cd2f94e83bf13129668b, fastForward,
>>>> srcRef=refs/heads/test-branch, message=null]
>>>> [INFO] commit done: commit message
>>>> [INFO] push changes to remote... refs/heads/master:refs/heads/master
>>>> [INFO] fetch url:
>>>>
>>>> file:///G:/apache/maven/git/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/target/scm-test/repository
>>>> [INFO] push url:
>>>>
>>>> file:///G:/apache/maven/git/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/target/scm-test/repository
>>>> [INFO] OK - RemoteRefUpdate[remoteName=refs/heads/master, OK,
>>>> (null)...dad31f52c2e81b71c2b4954ec9e2bc6dacfe9bef, fastForward,
>>>> srcRef=refs/heads/master, message=null]
>>>> [INFO] cloning [master] to
>>>>
>>>> G:\apache\maven\git\maven-scm\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-jgit\target\scm-test\assertion-copy
>>>> remote: Counting objects: 1
>>>> remote: Finding sources: 100% (14/14)
>>>> remote: Getting sizes:  100% (12/12)
>>>> remote: Compressing objects: 100% (363/363)
>>>> Receiving objects:  100% (14/14)
>>>> Resolving deltas:   100% (1/1)
>>>> Updating references:100% (2/2)
>>>> [INFO] fetch url:
>>>>
>>>> file:///G:/apache/maven/git/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/target/scm-test/repository
>>>> [INFO] push url:
>>>>
>>>> file:///G:/apache/maven/git/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/target/scm-test/repository
>>>> [INFO] checkout [master] at
>>>>
>>>> G:\apache\maven\git\maven-scm\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-jgit\target\scm-test\assertion-copy
>>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.656
>>>> sec <<< FAILURE! - in
>>>>
>>>> org.apache.maven.scm.provider.git.jgit.command.branch.JGitBranchCommandTckTest
>>>>
>>>> testBranchCommandTest(org.apache.maven.scm.provider.git.jgit.command.branch.JGitBranchCommandTckTest)
>>>> Time elapsed: 5.602 sec  <<< ERROR!
>>>> java.io.IOException: File
>>>>
>>>> G:\apache\maven\git\maven-scm\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-jgit\target\scm-test\assertion-copy\.git\objects\pack\pack-a06d224d673591806e6a66da6d8f27915e18184d.pack
>>>> unable to
>>>> be deleted.
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1413)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1673)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1618)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1401)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1673)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1618)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1401)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1673)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1618)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1401)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1673)
>>>>at
>>>> org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1618)
>>>>at
>>>> org.apache.maven.scm.tck.command.branch.BranchCommandTckTest.testBranchCommandTest(BranchCommandTckTest.java:77)
>>>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>at java.lan

Re: [VOTE] Apache Maven SCM 1.9

[Olivier Lamy]

tId)
>>>> org.eclipse.jgit.revwalk.RevWalk.parseCommit(AnyObjectId)
>>>> org.eclipse.jgit.api.CloneCommand.parseCommit(Repository, Ref)
>>>> org.eclipse.jgit.api.CloneCommand.checkout(Repository, FetchResult)
>>>> org.eclipse.jgit.api.CloneCommand.call()
>>>> org.apache.maven.scm.provider.git.jgit.command.checkout.JGitCheckOutCommand.executeCheckOutCommand(ScmProviderRepository,
>>>> ScmFileSet, ScmVersion, boolean)
>>>> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(ScmProviderRepository,
>>>> ScmFileSet, CommandParameters)
>>>> org.apache.maven.scm.command.AbstractCommand.execute(ScmProviderRepository,
>>>> ScmFileSet, CommandParameters)
>>>> org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(GitCommand,
>>>> ScmProviderRepository, ScmFileSet, CommandParameters)
>>>> org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkout(ScmProviderRepository,
>>>> ScmFileSet, CommandParameters)
>>>> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(ScmRepository,
>>>> ScmFileSet, ScmVersion, boolean)
>>>> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(ScmRepository,
>>>> ScmFileSet)
>>>> org.apache.maven.scm.manager.AbstractScmManager.checkOut(ScmRepository,
>>>> ScmFileSet)
>>>> org.apache.maven.scm.tck.command.tag.TagCommandTckTest.testTagCommandTest()
>>>> junit.framework.TestSuite.run(TestResult)
>>>> org.junit.internal.runners.JUnit38ClassRunner.run(RunNotifier)
>>>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(Class,
>>>> RunNotifier, String[])
>>>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(Class,
>>>> RunListener, RunNotifier)
>>>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(Object)
>>>> java.lang.reflect.Method.invoke(Object, Object[])
>>>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(Object,
>>>> Method, Object[])
>>>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(Object)
>>>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(Object,
>>>> ClassLoader, Object, ProviderConfiguration, boolean,
>>>> StartupConfiguration, boolean)
>>>> org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(DefaultScanResult)
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(ProviderInfo,
>>>> DefaultScanResult)
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(DefaultScanResult)
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute()
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(MavenSession,
>>>> MojoExecution)
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MavenSession,
>>>> MojoExecution, ProjectIndex, DependencyContext)
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MavenSession,
>>>> MojoExecution, ProjectIndex, DependencyContext, PhaseRecorder)
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MavenSession,
>>>> List, ProjectIndex)
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(MavenSession,
>>>> MavenSession, ReactorContext, MavenProject, TaskSegment)
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(MavenSession,
>>>> ReactorContext, MavenProject, TaskSegment)
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(MavenSession,
>>>> ReactorContext, ProjectBuildList, List, ReactorBuildStatus)
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(MavenSession)
>>>> org.apache.maven.DefaultMaven.doExecute(MavenExecutionRequest)
>>>> org.apache.maven.DefaultMaven.execute(MavenExecutionRequest)
>>>> org.apache.maven.cli.MavenCli.execute(MavenCli$CliRequest)
>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli$CliRequest)
>>>> org.apache.maven.cli.MavenCli.main(String[], ClassWorld)
>>>> java.lang.reflect.Method.invoke(Object, Object[])
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(String[])
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(String[])
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(String[])
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(String[])
>>>>
>>&g