repository.apache.org <-> repo1.maven.org

[Gabriele Columbro]

Dear Mavens,
cross-posting this to the Chemistry [1] Dev list, as I would like ask  
for a probably simple suggestion as we approach the first OpenCMIS  
0.1.0-incubating release [2] - *horray* :)


We successfully configured SNAPSHOT deployment to [4], and we're ready  
and set for following the RC and staging process as per [5].


AFAIU the staging process will surely make artifacts available on the  
public Nexus group of repository.apache.org, but how about  
repo1.maven.org?


I believe it's still worth to deploy artifacts there, so I was  
wondering if  there's any sync in place or I should just follow the  
standard Maven central upload procedure [6].


Sorry if this the question has been already answered (I guess so :)

Thanks in advance for the help,
Gabriele


[1] http://incubator.apache.org/chemistry/
[2] 
http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201006.mbox/%3c28097cae-5f1b-47f2-8ed6-7bcf6de96...@gmail.com%3e
[3] http://www.apache.org/dev/mirrors.html
[4] https://repository.apache.org/index.html#nexus- 
search;gav~org.apache.chemistry.opencmis~~0.1.0-incubating-SNAPSHOT

[5] http://maven.apache.org/developers/release/apache-release.html
[6] http://maven.apache.org/guides/mini/guide-central-repository-upload.html
--

Gabriele Columbro
Alfresco Software, Ltd.

http://www.mindthegab.com
http://twitter.com/mindthegabz

" Keyboard not found. Press F1 to continue. "




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

Re: Maven 2.x bugs -> 3.0?

[Brett Porter]

The 2.2.2 stuff is what eventually could/should be released to round out that 
series whether 3.0 is out or not.

The (< 20) bugs in 2.2.x still need to be reviewed for whether they apply to 
either version or not.

I'm more concerned about the 300 bugs split between the "3.x to be reviewed" 
(older ones) and "unscheduled" (bugs filed in the last year). These need to be 
reviewed for validity against the 3.0 beta and either put into the "3.x / 
backlog", or closed out.

- Brett

On 19/06/2010, at 5:09 AM, Paul Benedict wrote:

> I presume that Maven 2.2 is on life-support with the heavy emphasis on
> the future of Maven 3. Is that a correct understanding? If so, I
> wonder if the tagged 2.2/2.x unresolved issues are particular to that
> branch, or are they bugs also in the trunk?
> 
> Paul
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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

Re: [MDEP-269] please review

[Tamás Cservenák]

Well, we had an issue:

https://issues.sonatype.org/browse/NEXUS-644

but it was fixed more then a year ago... maybe he suffered from that one?

But index downloaded from central was never suffering from this issue (it is
not a Nexus instance, and Central would not be a group anyway). Use the
latest release of Nexus Indexer and please test it. If you find hashes
usable, please close the issue.

Note: In issue above MD5 hashes are mentioned, but MD5 is not supported
anymore, not on index. Only SHA1 hashes are.

Thanks,
~t~

On Fri, Jun 18, 2010 at 10:35 PM, nicolas de loof
wrote:

> I discussed with the author of alf-maven-osecm (that suggested me this
> feature) and he reported me he first tried to use the repo index but didn't
> find the hash in it. I've not tried by myslef. If hash is included, please
> close my Jira issue on Nexus and I'll double check this.
>
> 2010/6/18 Tamás Cservenák 
>
> > I don't get it, what do you mean by "repository index generated by Nexus
> > ...
> > doesn't include the artifact hash"?
> >
> > What makes you think hash is not on the index?
> >
> > Thanks,
> > ~t~
> >
> > On Fri, Jun 18, 2010 at 11:52 AM, nicolas de loof
> > wrote:
> >
> > > Hi folks,
> > >
> > > I'm working on MDEP-269  -
> > > convert
> > > a legacy lib/*.jar to maven 
> > > I've attached a patch to Jira as I'd like your opinion on the way to
> > > support
> > > this use case.
> > >
> > > My patch uses Nexus REST API to query the repository manager for
> > artifacts
> > > based on local files SHA1 hash.
> > > The query URL is configurable, and the Xpath expression to extract data
> > > should also, so that a non-nexus repository manager that provides
> > > comparable
> > > feature may be user.
> > >
> > > Maybe there is more performant/portable way to do this,
> > > for example using repository index generated by Nexus (not sure if
> other
> > > repository manager do the same) but this one doesn't include the
> > artifacts
> > > hash yet (NEXUS-3596 )
> > >
> > > WDYT ?
> > >
> > > Nicolas
> > >
> >
>

Re: [MDEP-269] please review

[nicolas de loof]

I discussed with the author of alf-maven-osecm (that suggested me this
feature) and he reported me he first tried to use the repo index but didn't
find the hash in it. I've not tried by myslef. If hash is included, please
close my Jira issue on Nexus and I'll double check this.

2010/6/18 Tamás Cservenák 

> I don't get it, what do you mean by "repository index generated by Nexus
> ...
> doesn't include the artifact hash"?
>
> What makes you think hash is not on the index?
>
> Thanks,
> ~t~
>
> On Fri, Jun 18, 2010 at 11:52 AM, nicolas de loof
> wrote:
>
> > Hi folks,
> >
> > I'm working on MDEP-269  -
> > convert
> > a legacy lib/*.jar to maven 
> > I've attached a patch to Jira as I'd like your opinion on the way to
> > support
> > this use case.
> >
> > My patch uses Nexus REST API to query the repository manager for
> artifacts
> > based on local files SHA1 hash.
> > The query URL is configurable, and the Xpath expression to extract data
> > should also, so that a non-nexus repository manager that provides
> > comparable
> > feature may be user.
> >
> > Maybe there is more performant/portable way to do this,
> > for example using repository index generated by Nexus (not sure if other
> > repository manager do the same) but this one doesn't include the
> artifacts
> > hash yet (NEXUS-3596 )
> >
> > WDYT ?
> >
> > Nicolas
> >
>

Re: [MDEP-269] please review

[Tamás Cservenák]

I don't get it, what do you mean by "repository index generated by Nexus ...
doesn't include the artifact hash"?

What makes you think hash is not on the index?

Thanks,
~t~

On Fri, Jun 18, 2010 at 11:52 AM, nicolas de loof
wrote:

> Hi folks,
>
> I'm working on MDEP-269  -
> convert
> a legacy lib/*.jar to maven 
> I've attached a patch to Jira as I'd like your opinion on the way to
> support
> this use case.
>
> My patch uses Nexus REST API to query the repository manager for artifacts
> based on local files SHA1 hash.
> The query URL is configurable, and the Xpath expression to extract data
> should also, so that a non-nexus repository manager that provides
> comparable
> feature may be user.
>
> Maybe there is more performant/portable way to do this,
> for example using repository index generated by Nexus (not sure if other
> repository manager do the same) but this one doesn't include the artifacts
> hash yet (NEXUS-3596 )
>
> WDYT ?
>
> Nicolas
>

Re: Maven 2.x bugs -> 3.0?

[Paul Benedict]

Have you tried goal dependency:tree ?

On Fri, Jun 18, 2010 at 2:29 PM, Martin Gainty  wrote:
>
> my understanding is that 2.2.1 is stable..3.0 seems to be alpha currently
>
>
> on a side note I would really like to see a plugin that displays transitive 
> dependencies..i just spent some time winding thru about 12 layers until I 
> found a small bug in surefire
>
> it seems the plugin.xml for surefire supports help with 
> org.apache.maven.plugin.surefire.HelpMojo and test goal with 
> org.apache.maven.plugin.surefire.SurefirePlugin (correct behavior)
>
> http://mvnrepository.com/artifact/org.apache.maven.plugins/maven-surefire-plugin
>
>
>
> the plugin.xml from source ONLY supports test goal and gacks the package 
> operation for creating maven-surefire-plugin (2.5)
>
> http://maven.apache.org/plugins/maven-surefire-plugin/source-repository.html
>
>
>
> can someone copy the good plugin.xml from source repository to the plugin.xml 
> in maven-surefire-plugin-2.5.jar binary?
>
>
>
> thanks,
> Martin
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
> sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
> oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich 
> dem Austausch von Informationen und entfaltet keine rechtliche 
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen 
> wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci 
> est interdite. Ce message sert à l'information seulement et n'aura pas 
> n'importe quel effet légalement obligatoire. Étant donné que les email 
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter 
> aucune responsabilité pour le contenu fourni.
>
>
>
>
>
>> Date: Fri, 18 Jun 2010 14:09:26 -0500
>> Subject: Maven 2.x bugs -> 3.0?
>> From: pbened...@apache.org
>> To: dev@maven.apache.org
>>
>> I presume that Maven 2.2 is on life-support with the heavy emphasis on
>> the future of Maven 3. Is that a correct understanding? If so, I
>> wonder if the tagged 2.2/2.x unresolved issues are particular to that
>> branch, or are they bugs also in the trunk?
>>
>> Paul
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> _
> The New Busy is not the too busy. Combine all your e-mail accounts with 
> Hotmail.
> http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4

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

RE: Maven 2.x bugs -> 3.0?

[Martin Gainty]

my understanding is that 2.2.1 is stable..3.0 seems to be alpha currently


on a side note I would really like to see a plugin that displays transitive 
dependencies..i just spent some time winding thru about 12 layers until I found 
a small bug in surefire 

it seems the plugin.xml for surefire supports help with 
org.apache.maven.plugin.surefire.HelpMojo and test goal with 
org.apache.maven.plugin.surefire.SurefirePlugin (correct behavior)

http://mvnrepository.com/artifact/org.apache.maven.plugins/maven-surefire-plugin

 

the plugin.xml from source ONLY supports test goal and gacks the package 
operation for creating maven-surefire-plugin (2.5)

http://maven.apache.org/plugins/maven-surefire-plugin/source-repository.html

 

can someone copy the good plugin.xml from source repository to the plugin.xml 
in maven-surefire-plugin-2.5.jar binary?

 

thanks,
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.



 

> Date: Fri, 18 Jun 2010 14:09:26 -0500
> Subject: Maven 2.x bugs -> 3.0?
> From: pbened...@apache.org
> To: dev@maven.apache.org
> 
> I presume that Maven 2.2 is on life-support with the heavy emphasis on
> the future of Maven 3. Is that a correct understanding? If so, I
> wonder if the tagged 2.2/2.x unresolved issues are particular to that
> branch, or are they bugs also in the trunk?
> 
> Paul
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
  
_
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4

Maven 2.x bugs -> 3.0?

[Paul Benedict]

I presume that Maven 2.2 is on life-support with the heavy emphasis on
the future of Maven 3. Is that a correct understanding? If so, I
wonder if the tagged 2.2/2.x unresolved issues are particular to that
branch, or are they bugs also in the trunk?

Paul

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

[MDEP-269] please review

[nicolas de loof]

Hi folks,

I'm working on MDEP-269  - convert
a legacy lib/*.jar to maven 
I've attached a patch to Jira as I'd like your opinion on the way to support
this use case.

My patch uses Nexus REST API to query the repository manager for artifacts
based on local files SHA1 hash.
The query URL is configurable, and the Xpath expression to extract data
should also, so that a non-nexus repository manager that provides comparable
feature may be user.

Maybe there is more performant/portable way to do this,
for example using repository index generated by Nexus (not sure if other
repository manager do the same) but this one doesn't include the artifacts
hash yet (NEXUS-3596 )

WDYT ?

Nicolas

RE: Base Abstract Mojo

[Giuseppe.Greco]

YES it was a typo... and now it works! I'm sorry but yesterday after 12
hours at my desk I was a little bit burned out.

Thanks a lot!
Jeff

> -Original Message-
> From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu] 
> Sent: Thursday, June 17, 2010 9:59 PM
> To: Maven Developers List
> Subject: Re: Base Abstract Mojo
> 
> 
> Giuseppe Greco wrote:
> 
> 
> >   * @parameter expression="${outputDirectory}"
> > default-value"${project.build.directory}"
> 
> This misses the equal sign '=' after "default-value". Is this 
> a typo in 
> your source?
> 
> 
> Benjamin
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

IMPORTANT:
This e-mail transmission is intended for the named
addressee(s)only.
Its contents are private, confidential and protected
from disclosure and should not be read, copied or
disclosed by any other person.
If you are not the intended recipient, we kindly ask
you to notify the sender immediately by telephone
(+41 (0)58 806 50 00), to redirect the message to the
account "i...@b-source.ch" and to delete this e-mail.
E-mail transmissions may be intercepted, altered or
read by unauthorized persons and may contain viruses.
Therefore, it is recommended that you use regular mail
or courier services for any information intended to be
confidential. However, by sending us messages through
e-mail, you authorize and instruct us to correspond by
e-mail in the relevant matter.
Thank you.


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