[DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Stephen Connolly-2
If you are a hosted plugin owner, please let me know (on this thread) what plugin you own and if I can tweak your plugin's pom.xml to improve the first time build and ensure that common dependecies are used where possible.

Thanks,

-Stephen Connolly.
Reply | Threaded
Open this post in threaded view
|

Re: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Nigel Daley-3
Plot plugin.  By all means be my guest :-)

Thanks Stephen!

Cheers,
Nige

On Jul 25, 2007, at 4:19 PM, Stephen Connolly wrote:

>
> If you are a hosted plugin owner, please let me know (on this  
> thread) what
> plugin you own and if I can tweak your plugin's pom.xml to improve  
> the first
> time build and ensure that common dependecies are used where possible.
>
> Thanks,
>
> -Stephen Connolly.
> --
> View this message in context: http://www.nabble.com/-DEV---VOTE-- 
> Stephen-to-optimize-hosted-plugin-pom.xml-files-
> tf4148535.html#a11801678
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Arnaud LACOUR
In reply to this post by Stephen Connolly-2
gcal. Feel free.
-=arnaud=-

On 7/25/07, Stephen Connolly <[hidden email]> wrote:

>
> If you are a hosted plugin owner, please let me know (on this thread) what
> plugin you own and if I can tweak your plugin's pom.xml to improve the first
> time build and ensure that common dependecies are used where possible.
>
> Thanks,
>
> -Stephen Connolly.
> --
> View this message in context: http://www.nabble.com/-DEV---VOTE--Stephen-to-optimize-hosted-plugin-pom.xml-files-tf4148535.html#a11801678
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Renaud Bruyeron-2
In reply to this post by Stephen Connolly-2
Stephen Connolly wrote:
> If you are a hosted plugin owner, please let me know (on this thread) what
> plugin you own and if I can tweak your plugin's pom.xml to improve the first
> time build and ensure that common dependecies are used where possible.
>  
ircbot plugin - feel free :)

 - Renaud

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Ulli Hafner-2
In reply to this post by Stephen Connolly-2
> From: Stephen Connolly [mailto:[hidden email]]
>
> If you are a hosted plugin owner, please let me know (on this
> thread) what plugin you own and if I can tweak your plugin's
> pom.xml to improve the first time build and ensure that
> common dependecies are used where possible.

Findbugs: feel free to improve!

BTW: it would be really cool to remove the
<url>https://hudson.dev.java.net/source/browse/*checkout*...
dependency, if it is not required anymore. Since maven 2.0.x can't
handle different proxies for HTTP
and HTTPS I always need to run maven twice (one for HTTP repositories,
one for HTTPS).

Thanks, Ulli

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Stephen Connolly-2
In reply to this post by Stephen Connolly-2
Stephen Connolly wrote
If you are a hosted plugin owner, please let me know (on this thread) what plugin you own and if I can tweak your plugin's pom.xml to improve the first time build and ensure that common dependecies are used where possible.

Thanks,

-Stephen Connolly.
1. Just an FYI,

On the originating thread, Jorg Heymans, said he has some tunings on the pom.xml's as well that he will be promoting.

I am going to wait until these changes are promoted so that I can ensure that my optimizations do not break his changes.

Basically, he has moved the extra repository definitions out of the root pom and into only those poms that need those repository definitions.  This reduces the number of repositories that need to be checked.  I don't want to duplicate his effort finding where these definitions need to be moved, so I will hold off making changed until his changes are promoted.

2. For poms that use repositories with the <url>file:.....</url> to bundle binary resources, we need to get poms for all the artifacts in these local repositories as, at present, these missing poms are then searched for among all the known repositories.  If the pom files (even basic ones) were present, that will speed up things.  I'll probably start generating dummy ones.  As I don't know these artifacts, these dummy poms will not contain their dependencies, so if you know your artifacts dependencies, please specify them (in the dummy poms i'll be generating, or generate your own poms ;-) )!

-Stephen Connolly
Reply | Threaded
Open this post in threaded view
|

Re: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Stephen Connolly-2
Kohsuke,

These poms badly need to be fixed to 4.0.0 POM

[WARNING] POM for 'commons-jelly:commons-jelly-tags-define:pom:1.0.1-hudson-20061106:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'commons-jexl:commons-jexl:pom:1.1-hudson-20061106:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'commons-jelly:commons-jelly:pom:1.1-hudson-20061106:provided' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.

As _every_ plugin has to go looking for a 4.0.0 schema pom until a 4.0.0 pom is found... which is never

Could result in quite a bit of speed-up

I don't want to touch them until you give the OK though.

-Stephen Connnolly

P.S.
  I have provided basic dummy poms where poms were missing in codeviation, gcal, and jprt.  If the owners of those plugins can add any dependencies they know into those dummy poms it would make them better poms (but won't affect anything else... just it's nicer to have the correct details in a pom)

Stephen Connolly wrote
Stephen Connolly wrote
If you are a hosted plugin owner, please let me know (on this thread) what plugin you own and if I can tweak your plugin's pom.xml to improve the first time build and ensure that common dependecies are used where possible.

Thanks,

-Stephen Connolly.
1. Just an FYI,

On the originating thread, Jorg Heymans, said he has some tunings on the pom.xml's as well that he will be promoting.

I am going to wait until these changes are promoted so that I can ensure that my optimizations do not break his changes.

Basically, he has moved the extra repository definitions out of the root pom and into only those poms that need those repository definitions.  This reduces the number of repositories that need to be checked.  I don't want to duplicate his effort finding where these definitions need to be moved, so I will hold off making changed until his changes are promoted.

2. For poms that use repositories with the <url>file:.....</url> to bundle binary resources, we need to get poms for all the artifacts in these local repositories as, at present, these missing poms are then searched for among all the known repositories.  If the pom files (even basic ones) were present, that will speed up things.  I'll probably start generating dummy ones.  As I don't know these artifacts, these dummy poms will not contain their dependencies, so if you know your artifacts dependencies, please specify them (in the dummy poms i'll be generating, or generate your own poms ;-) )!

-Stephen Connolly
Reply | Threaded
Open this post in threaded view
|

Re: [DEV] [VOTE] Stephen to optimize hosted plugin pom.xml files

Kohsuke Kawaguchi
Administrator
2007/7/26, Stephen Connolly <[hidden email]>:
>
> Kohsuke,
>
> These poms badly need to be fixed to 4.0.0 POM

Thanks. You are quite right.

>
> [WARNING] POM for
> 'commons-jelly:commons-jelly-tags-define:pom:1.0.1-hudson-20061106:provided'
> is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0
> POM.
> [WARNING] POM for
> 'commons-jexl:commons-jexl:pom:1.1-hudson-20061106:provided' is invalid. It
> will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
> [WARNING] POM for
> 'commons-jelly:commons-jelly:pom:1.1-hudson-20061106:provided' is invalid.
> It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
>
> As _every_ plugin has to go looking for a 4.0.0 schema pom until a 4.0.0 pom
> is found... which is never
>
> Could result in quite a bit of speed-up
>
> I don't want to touch them until you give the OK though.

Please go ahead. Thanks for doing this.

> P.S.
>   I have provided basic dummy poms where poms were missing in codeviation,
> gcal, and jprt.  If the owners of those plugins can add any dependencies
> they know into those dummy poms it would make them better poms (but won't
> affect anything else... just it's nicer to have the correct details in a
> pom)

I don't think jprt plugin owner would mind us making the change, so
feel free to apply that, too.

--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]