Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-11-01 Thread Olivier Lamy
Hi
@Karl Are you available to release it?
If not I can release it with the assembly plugin

Let me know.


On 31 October 2016 at 01:02, Robert Scholte  wrote:

> Hi,
>
> Patch looks good to me, apply it if you want.
>
> I don't know the details about the deprecation of ArtifactMetadata, I
> could imagine that it should be a Maven internal thing and plugins
> shouldn't matter about its details. But as long as we need something like
> ProjectArtifactMetadata we cannot remove it.
>
> Robert
>
>
> On Sat, 29 Oct 2016 23:12:42 +0200, Guillaume Boué <
> guillaume_b...@orange.fr> wrote:
>
> About Maven Artifact Transfer, I have https://issues.apache.org/jira
>> /browse/MSHARED-596, which would help notably in the Install Plugin, and
>> would also simplify the usage of the ProjectInstaller.
>>
>> It would be great to have this in the release; there's a patch attached,
>> but looking for feedback.
>>
>> Thanks,
>> Guillaume
>>
>> Le 29/10/2016 à 18:48, Karl Heinz Marbaise a écrit :
>>
>>> Hi Robert,
>>>
>>> On 29/10/16 16:24, Robert Scholte wrote:
>>>
 1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
 0.10.0 is a valid version too, still many see 0.9 as "almost final" )

>>>
>>> 0.9.0 ...sure 0.10.0 is valid too...
>>>
>>>
>>> Yes that makes it more clear that it is not fully ready...
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>>
 Robert

 On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise
  wrote:

 Hi to all,
>
> cause the missing release of the shared component is currently
> blocking other plugins from being released...
>
>
> I would suggest to make a 1.0.0 release of the maven-artifact-transfer
> shared component so we have the chance to release other plugins like:
>
> maven-install-plugin,
> maven-deploy-plugin,
> maven-dependency-plugin,
> maven-assembly-plugin
>
> afterwards...
>
> I have intentially selected an 1.0.0 so we are able to change the
> interfaces if we need and can create a release 2.0.0 or 3.0.0 to
> reflect those changes simply...
>
> WDYT ?
>
>
>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>> ---
>> L'absence de virus dans ce courrier électronique a été vérifiée par le
>> logiciel antivirus Avast.
>> https://www.avast.com/antivirus
>>
>>
>> -
>> 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
http://twitter.com/olamy | http://linkedin.com/in/olamy


Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-10-30 Thread Robert Scholte

Hi,

Patch looks good to me, apply it if you want.

I don't know the details about the deprecation of ArtifactMetadata, I  
could imagine that it should be a Maven internal thing and plugins  
shouldn't matter about its details. But as long as we need something like  
ProjectArtifactMetadata we cannot remove it.


Robert

On Sat, 29 Oct 2016 23:12:42 +0200, Guillaume Boué  
 wrote:


About Maven Artifact Transfer, I have  
https://issues.apache.org/jira/browse/MSHARED-596, which would help  
notably in the Install Plugin, and would also simplify the usage of the  
ProjectInstaller.


It would be great to have this in the release; there's a patch attached,  
but looking for feedback.


Thanks,
Guillaume

Le 29/10/2016 à 18:48, Karl Heinz Marbaise a écrit :

Hi Robert,

On 29/10/16 16:24, Robert Scholte wrote:

1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
0.10.0 is a valid version too, still many see 0.9 as "almost final" )


0.9.0 ...sure 0.10.0 is valid too...


Yes that makes it more clear that it is not fully ready...

Kind regards
Karl Heinz Marbaise



Robert

On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise
 wrote:


Hi to all,

cause the missing release of the shared component is currently
blocking other plugins from being released...


I would suggest to make a 1.0.0 release of the maven-artifact-transfer
shared component so we have the chance to release other plugins like:

maven-install-plugin,
maven-deploy-plugin,
maven-dependency-plugin,
maven-assembly-plugin

afterwards...

I have intentially selected an 1.0.0 so we are able to change the
interfaces if we need and can create a release 2.0.0 or 3.0.0 to
reflect those changes simply...

WDYT ?




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




---
L'absence de virus dans ce courrier électronique a été vérifiée par le  
logiciel antivirus Avast.

https://www.avast.com/antivirus


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


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



Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-10-30 Thread Olivier Lamy
Hi
1.0.0-beta-1 sounds a good idea.
Anyway as you release it do whatever you want :-)

On 30 October 2016 at 03:48, Karl Heinz Marbaise  wrote:

> Hi Robert,
>
> On 29/10/16 16:24, Robert Scholte wrote:
>
>> 1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
>> 0.10.0 is a valid version too, still many see 0.9 as "almost final" )
>>
>
> 0.9.0 ...sure 0.10.0 is valid too...
>
>
> Yes that makes it more clear that it is not fully ready...
>
> Kind regards
> Karl Heinz Marbaise
>
>
>> Robert
>>
>> On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise
>>  wrote:
>>
>> Hi to all,
>>>
>>> cause the missing release of the shared component is currently
>>> blocking other plugins from being released...
>>>
>>>
>>> I would suggest to make a 1.0.0 release of the maven-artifact-transfer
>>> shared component so we have the chance to release other plugins like:
>>>
>>> maven-install-plugin,
>>> maven-deploy-plugin,
>>> maven-dependency-plugin,
>>> maven-assembly-plugin
>>>
>>> afterwards...
>>>
>>> I have intentially selected an 1.0.0 so we are able to change the
>>> interfaces if we need and can create a release 2.0.0 or 3.0.0 to
>>> reflect those changes simply...
>>>
>>> WDYT ?
>>>
>>>
>>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


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


Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-10-29 Thread Guillaume Boué
About Maven Artifact Transfer, I have 
https://issues.apache.org/jira/browse/MSHARED-596, which would help 
notably in the Install Plugin, and would also simplify the usage of the 
ProjectInstaller.


It would be great to have this in the release; there's a patch attached, 
but looking for feedback.


Thanks,
Guillaume

Le 29/10/2016 à 18:48, Karl Heinz Marbaise a écrit :

Hi Robert,

On 29/10/16 16:24, Robert Scholte wrote:

1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
0.10.0 is a valid version too, still many see 0.9 as "almost final" )


0.9.0 ...sure 0.10.0 is valid too...


Yes that makes it more clear that it is not fully ready...

Kind regards
Karl Heinz Marbaise



Robert

On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise
 wrote:


Hi to all,

cause the missing release of the shared component is currently
blocking other plugins from being released...


I would suggest to make a 1.0.0 release of the maven-artifact-transfer
shared component so we have the chance to release other plugins like:

maven-install-plugin,
maven-deploy-plugin,
maven-dependency-plugin,
maven-assembly-plugin

afterwards...

I have intentially selected an 1.0.0 so we are able to change the
interfaces if we need and can create a release 2.0.0 or 3.0.0 to
reflect those changes simply...

WDYT ?




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




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus


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



Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-10-29 Thread Karl Heinz Marbaise

Hi Robert,

On 29/10/16 16:24, Robert Scholte wrote:

1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
0.10.0 is a valid version too, still many see 0.9 as "almost final" )


0.9.0 ...sure 0.10.0 is valid too...


Yes that makes it more clear that it is not fully ready...

Kind regards
Karl Heinz Marbaise



Robert

On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise
 wrote:


Hi to all,

cause the missing release of the shared component is currently
blocking other plugins from being released...


I would suggest to make a 1.0.0 release of the maven-artifact-transfer
shared component so we have the chance to release other plugins like:

maven-install-plugin,
maven-deploy-plugin,
maven-dependency-plugin,
maven-assembly-plugin

afterwards...

I have intentially selected an 1.0.0 so we are able to change the
interfaces if we need and can create a release 2.0.0 or 3.0.0 to
reflect those changes simply...

WDYT ?




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



Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-10-29 Thread Gary Gregory
Or 1.0.0-alpha1

Gary

On Oct 29, 2016 7:24 AM, "Robert Scholte"  wrote:

> 1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
> 0.10.0 is a valid version too, still many see 0.9 as "almost final" )
>
> Robert
>
> On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise 
> wrote:
>
> Hi to all,
>>
>> cause the missing release of the shared component is currently blocking
>> other plugins from being released...
>>
>>
>> I would suggest to make a 1.0.0 release of the maven-artifact-transfer
>> shared component so we have the chance to release other plugins like:
>>
>> maven-install-plugin,
>> maven-deploy-plugin,
>> maven-dependency-plugin,
>> maven-assembly-plugin
>>
>> afterwards...
>>
>> I have intentially selected an 1.0.0 so we are able to change the
>> interfaces if we need and can create a release 2.0.0 or 3.0.0 to
>> reflect those changes simply...
>>
>> WDYT ?
>>
>>
>> Kind regards
>> Karl Heinz
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Re: Maven Artifact Transfer Shared Component Release 1.0.0 ?

2016-10-29 Thread Robert Scholte
1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though  
0.10.0 is a valid version too, still many see 0.9 as "almost final" )


Robert

On Sat, 29 Oct 2016 14:03:46 +0200, Karl Heinz Marbaise  
 wrote:



Hi to all,

cause the missing release of the shared component is currently blocking  
other plugins from being released...



I would suggest to make a 1.0.0 release of the maven-artifact-transfer  
shared component so we have the chance to release other plugins like:


maven-install-plugin,
maven-deploy-plugin,
maven-dependency-plugin,
maven-assembly-plugin

afterwards...

I have intentially selected an 1.0.0 so we are able to change the  
interfaces if we need and can create a release 2.0.0 or 3.0.0 to  
reflect those changes simply...


WDYT ?


Kind regards
Karl Heinz

-
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