m2eclipse and repositories with same repositoryId

[Stevo Slavic]

Hello m2eclipse users,

Unlike CLI maven, and previous m2eclipse versions like 0.9.8, current development m2eclipse 0.9.9.200909092308 seems to refuse to auto build projects with multiple repositories sharing same repositoryId. Repositories were given same repositoryId because they are on same server and same credentials are being used for authentication to the server, so single corresponding server entry is configured in settings.xml.

Why has this constraint, that repositoryId's should be different/unique, been imposed when Maven model doesn't support credentials to be defined in a DRY manner, to allow reuse for several servers/repositories?

Regards,
Stevo.

[jvanzyl]

Please provide concrete test projects and then we can have a  
meaningful discussion. Repositories cannot share the same  
repositoryId. A repository may have unique URL so allowing two  
repositories to have the same id where they may actually differ  
doesn't make sense. Regardless of what was allowed previously. So if  
we have a misunderstanding a test project will help shed some light.

On 2009-10-27, at 8:16 AM, Stevo Slavić wrote:

> Hello m2eclipse users,
>
> Unlike CLI maven, and previous m2eclipse versions like 0.9.8,  
> current development m2eclipse 0.9.9.200909092308 seems to refuse to  
> auto build projects with multiple repositories sharing same  
> repositoryId. Repositories were given same repositoryId because they  
> are on same server and same credentials are being used for  
> authentication to the server, so single corresponding server entry  
> is configured in settings.xml.
>
> Why has this constraint, that repositoryId's should be different/
> unique, been imposed when Maven model doesn't support credentials to  
> be defined in a DRY manner, to allow reuse for several servers/
> repositories?
>
> Regards,
> Stevo.

Thanks,

Jason

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


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Stevo Slavic]

Say in a corporate environment one has a repository manager configured to authenticate users based on their domain credentials; each project has repository (group) for its own private artifacts; some repositories are shared among several projects; for a project in its pom one then defines projects own repository as dependency repository, and some other shared repository as additional dependency repository, both with same id so that single server definition in settings.xml can be reused, but each with its own distinct URL. That worked before, since m2eclipse 0.9.9.200909092308 it doesn't.

Regards,
Stevo.

On Tue, Oct 27, 2009 at 4:23 PM, Jason van Zyl <jason@...> wrote:

Please provide concrete test projects and then we can have a meaningful discussion. Repositories cannot share the same repositoryId. A repository may have unique URL so allowing two repositories to have the same id where they may actually differ doesn't make sense. Regardless of what was allowed previously. So if we have a misunderstanding a test project will help shed some light.

On 2009-10-27, at 8:16 AM, Stevo Slavić wrote:

Hello m2eclipse users,

Unlike CLI maven, and previous m2eclipse versions like 0.9.8, current development m2eclipse 0.9.9.200909092308 seems to refuse to auto build projects with multiple repositories sharing same repositoryId. Repositories were given same repositoryId because they are on same server and same credentials are being used for authentication to the server, so single corresponding server entry is configured in settings.xml.

Why has this constraint, that repositoryId's should be different/unique, been imposed when Maven model doesn't support credentials to be defined in a DRY manner, to allow reuse for several servers/repositories?

Regards,
Stevo.

Thanks,

Jason

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


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email

[Igor Fedorenko-4]

This is how we have it setup internally and all works without problems.
m2e 0.9.9 uses the same repository configuration logic as maven
3.0-SNAPSHOT, so it would be helpful if you could verify if the problem
can be reproduced with maven 3.0 on cli.

--
Regards,
Igor

Stevo Slavić wrote:

> Say in a corporate environment one has a repository manager configured
> to authenticate users based on their domain credentials; each project
> has repository (group) for its own private artifacts; some repositories
> are shared among several projects; for a project in its pom one then
> defines projects own repository as dependency repository, and some other
> shared repository as additional dependency repository, both with same id
> so that single server definition in settings.xml can be reused, but each
> with its own distinct URL. That worked before, since m2eclipse
> 0.9.9.200909092308 it doesn't.
>
> Regards,
> Stevo.
>
> On Tue, Oct 27, 2009 at 4:23 PM, Jason van Zyl <jason@...
> <mailto:jason@...>> wrote:
>
>     Please provide concrete test projects and then we can have a
>     meaningful discussion. Repositories cannot share the same
>     repositoryId. A repository may have unique URL so allowing two
>     repositories to have the same id where they may actually differ
>     doesn't make sense. Regardless of what was allowed previously. So if
>     we have a misunderstanding a test project will help shed some light.
>
>
>     On 2009-10-27, at 8:16 AM, Stevo Slavić wrote:
>
>         Hello m2eclipse users,
>
>         Unlike CLI maven, and previous m2eclipse versions like 0.9.8,
>         current development m2eclipse 0.9.9.200909092308 seems to refuse
>         to auto build projects with multiple repositories sharing same
>         repositoryId. Repositories were given same repositoryId because
>         they are on same server and same credentials are being used for
>         authentication to the server, so single corresponding server
>         entry is configured in settings.xml.
>
>         Why has this constraint, that repositoryId's should be
>         different/unique, been imposed when Maven model doesn't support
>         credentials to be defined in a DRY manner, to allow reuse for
>         several servers/repositories?
>
>         Regards,
>         Stevo.
>
>
>     Thanks,
>
>     Jason
>
>     ----------------------------------------------------------
>     Jason van Zyl
>     Founder,  Apache Maven
>     http://twitter.com/jvanzyl
>     ----------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Stevo Slavic]

Regardless if m2e 0.9.9 is configured to use external Maven 2.2.1 installation or embedded Maven 3.0-SNAPSHOT, errors like [1] and [2] appear in eclipse Maven Console when importing and "Project-->Clean..."-ing multi-module project, respectively, with two repositories that share same repositoryId declared in project aggregator module. All but aggregator module pom end up being marked as with errors because of missing artifacts.

Then I tried with apache-maven-3.0-SNAPSHOT (apache-maven-3.0-20091002.163705-31-bin.zip) from CLI. "mvn clean" was successful but reported several times that reporting section is deprecated and that reports ought to be moved to the configuration section. "mvn package" failed but for a different reason, it first reported warnings that multiple artifacts are missing artifact metadata (I suppose this issue will have to be resolved before central repo can be used in maven3) and then build failed stating that these artifacts with missing metadata are themselves missing, which is consistent with in eclipse behavior.

Regards,
Stevo.

[1] eclipse Maven Console snippet after importing

10/27/09 10:38:59 PM CET: Maven Builder: FULL_BUILD
10/27/09 10:38:59 PM CET: Build errors for foo.bar.module1; org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[ERROR] 'repositories.repository.id' must be unique: acme-repo -> https://repo.acme.com/content/groups/shared-repo vs https://repo.acme.com/content/groups/foo-bar @ foo:bar:0.0.1-SNAPSHOT (C:\eclipse\workspaces\foo\bar\foo.bar\pom.xml)


[2] eclipse Maven Console snippet after cleaning projects with Build Automatically checked

10/27/09 11:01:28 PM CET: Maven Builder: FULL_BUILD requireFullBuild
10/27/09 11:01:28 PM CET: Build errors for foo.bar.module1; org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[ERROR] 'repositories.repository.id' must be unique: acme-repo -> https://repo.acme.com/content/groups/shared-repo vs https://repo.acme.com/content/groups/foo-bar @ foo:bar:0.0.1-SNAPSHOT (C:\eclipse\workspaces\foo\bar\foo.bar\pom.xml)

On Tue, Oct 27, 2009 at 6:12 PM, Igor Fedorenko <igor@...> wrote:

This is how we have it setup internally and all works without problems.
m2e 0.9.9 uses the same repository configuration logic as maven
3.0-SNAPSHOT, so it would be helpful if you could verify if the problem
can be reproduced with maven 3.0 on cli.

--
Regards,
Igor

Stevo Slavić wrote:

Say in a corporate environment one has a repository manager configured to authenticate users based on their domain credentials; each project has repository (group) for its own private artifacts; some repositories are shared among several projects; for a project in its pom one then defines projects own repository as dependency repository, and some other shared repository as additional dependency repository, both with same id so that single server definition in settings.xml can be reused, but each with its own distinct URL. That worked before, since m2eclipse 0.9.9.200909092308 it doesn't.

Regards,
Stevo.

On Tue, Oct 27, 2009 at 4:23 PM, Jason van Zyl <jason@... <mailto:jason@...>> wrote:

   Please provide concrete test projects and then we can have a
   meaningful discussion. Repositories cannot share the same
   repositoryId. A repository may have unique URL so allowing two
   repositories to have the same id where they may actually differ
   doesn't make sense. Regardless of what was allowed previously. So if
   we have a misunderstanding a test project will help shed some light.


   On 2009-10-27, at 8:16 AM, Stevo Slavić wrote:

       Hello m2eclipse users,

       Unlike CLI maven, and previous m2eclipse versions like 0.9.8,
       current development m2eclipse 0.9.9.200909092308 seems to refuse
       to auto build projects with multiple repositories sharing same
       repositoryId. Repositories were given same repositoryId because
       they are on same server and same credentials are being used for
       authentication to the server, so single corresponding server
       entry is configured in settings.xml.

       Why has this constraint, that repositoryId's should be
       different/unique, been imposed when Maven model doesn't support
       credentials to be defined in a DRY manner, to allow reuse for
       several servers/repositories?

       Regards,
       Stevo.


   Thanks,

   Jason

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

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email