[jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
[
http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173980#action_173980
]
Niels Bo Andersen commented on MPIR-137:
This issue also affects the use of Artifactory version 2.0.5, and possibly
older. I've recently upgraded from v. 1.2.5, and I am now getting this error.
The reason for this is, that the plugin seems to request the base URL of the
repository, i.e. {{http://artifactoryserver/artifactory/repo}}, without a
trailing slash.
Artifactory version 1.2.5 returned a valid response to this request, but the
new version returns a 404. Everything below the base URL is OK, and the rest of
the build uses the Artifactory server without any problems.
If there is a requirement, that a repository should reply to the base URL, then
this is of course a bug in Artifactory, but if there is no such requirement,
this issue should be marked as a bug, not an improvement.
> Dependency Locations should work with an intranet repository and restricted
> internet access
> ---
>
> Key: MPIR-137
> URL: http://jira.codehaus.org/browse/MPIR-137
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies
>Affects Versions: 2.1
> Environment: All environments, no internet access allowed, no
> internet proxy configuration, intranet repository configured (Artifactory,
> but it seems to happen with Archiva)
>Reporter: Diego Parrilla
>Priority: Minor
>
> We use Maven and Artifactory, and the PCs does not have direct internet
> access allowed. Maven is configured to mirror the Artifactory repository. So,
> all the users have to download their artifacts from the intranet repository.
> When launching the 'site' goal (mvn site), when generating the 'Dependencies'
> report, it hangs for a long time until we get this error:
> [WARNING] The repository url '' is invalid - Repository 'XXX' will be
> blacklisted.
> It's possible to work around this problem disabling the parameter
> 'dependencyLocationEnabled' in the maven-project-info-reports-plugin:
>
> ...
>
> org.apache.maven.plugins
> maven-project-info-reports-plugin
> 2.1
>
> false
>
>
> ...
>
> But I think the dependency locations should be solved using the information
> stored in the intranet repository (in my case Artifactory). At this moment
> the reports generated do not include the Dependency Location information.
> You can read this thread for a further description:
> http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
[
http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167291#action_167291
]
Vincent Siveton commented on MPIR-137:
--
The report uses the repositories defined in the pom dependencies. For instance,
you could have the following
{noformat}
[WARNING] The repository url 'http://snapshots.maven.codehaus.org/maven2' is
invalid - Repository 'snapshots' will be blacklisted.
{noformat}
It is due because this repo is defined in an old version of Plexus's pom.
Using an intranet repository will produce the same error I guess.
> Dependency Locations should work with an intranet repository and restricted
> internet access
> ---
>
> Key: MPIR-137
> URL: http://jira.codehaus.org/browse/MPIR-137
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies
>Affects Versions: 2.1
> Environment: All environments, no internet access allowed, no
> internet proxy configuration, intranet repository configured (Artifactory,
> but it seems to happen with Archiva)
>Reporter: Diego Parrilla
>Priority: Minor
>
> We use Maven and Artifactory, and the PCs does not have direct internet
> access allowed. Maven is configured to mirror the Artifactory repository. So,
> all the users have to download their artifacts from the intranet repository.
> When launching the 'site' goal (mvn site), when generating the 'Dependencies'
> report, it hangs for a long time until we get this error:
> [WARNING] The repository url '' is invalid - Repository 'XXX' will be
> blacklisted.
> It's possible to work around this problem disabling the parameter
> 'dependencyLocationEnabled' in the maven-project-info-reports-plugin:
>
> ...
>
> org.apache.maven.plugins
> maven-project-info-reports-plugin
> 2.1
>
> false
>
>
> ...
>
> But I think the dependency locations should be solved using the information
> stored in the intranet repository (in my case Artifactory). At this moment
> the reports generated do not include the Dependency Location information.
> You can read this thread for a further description:
> http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
[ http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158454#action_158454 ] Adrian commented on MPIR-137: - FYI there's an error on the first post : element 'dependencyLocationEnabled' should be renamed 'dependencyLocationsEnabled' (missing s). I was having the same pb during Generating "Dependencies" report. I've added both dependencyLocationsEnabled and dependencyDetailsEnabled and it worked. No more freezing. Here's my config snippet : org.apache.maven.plugins maven-project-info-reports-plugin false false > Dependency Locations should work with an intranet repository and restricted > internet access > --- > > Key: MPIR-137 > URL: http://jira.codehaus.org/browse/MPIR-137 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 > Environment: All environments, no internet access allowed, no > internet proxy configuration, intranet repository configured (Artifactory, > but it seems to happen with Archiva) >Reporter: Diego Parrilla >Priority: Minor > > We use Maven and Artifactory, and the PCs does not have direct internet > access allowed. Maven is configured to mirror the Artifactory repository. So, > all the users have to download their artifacts from the intranet repository. > When launching the 'site' goal (mvn site), when generating the 'Dependencies' > report, it hangs for a long time until we get this error: > [WARNING] The repository url '' is invalid - Repository 'XXX' will be > blacklisted. > It's possible to work around this problem disabling the parameter > 'dependencyLocationEnabled' in the maven-project-info-reports-plugin: > > ... > > org.apache.maven.plugins > maven-project-info-reports-plugin > 2.1 > > false > > > ... > > But I think the dependency locations should be solved using the information > stored in the intranet repository (in my case Artifactory). At this moment > the reports generated do not include the Dependency Location information. > You can read this thread for a further description: > http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
[ http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149111#action_149111 ] Pablo Graña commented on MPIR-137: -- About my post I just did mvn clean -> mvn site (instead of mvn clean site) and, it does not throw the stack trace. But still freezes for a long time Generating "Dependencies" report. I guess I'll have to go to 2.0.1 > Dependency Locations should work with an intranet repository and restricted > internet access > --- > > Key: MPIR-137 > URL: http://jira.codehaus.org/browse/MPIR-137 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 > Environment: All environments, no internet access allowed, no > internet proxy configuration, intranet repository configured (Artifactory, > but it seems to happen with Archiva) >Reporter: Diego Parrilla >Priority: Minor > > We use Maven and Artifactory, and the PCs does not have direct internet > access allowed. Maven is configured to mirror the Artifactory repository. So, > all the users have to download their artifacts from the intranet repository. > When launching the 'site' goal (mvn site), when generating the 'Dependencies' > report, it hangs for a long time until we get this error: > [WARNING] The repository url '' is invalid - Repository 'XXX' will be > blacklisted. > It's possible to work around this problem disabling the parameter > 'dependencyLocationEnabled' in the maven-project-info-reports-plugin: > > ... > > org.apache.maven.plugins > maven-project-info-reports-plugin > 2.1 > > false > > > ... > > But I think the dependency locations should be solved using the information > stored in the intranet repository (in my case Artifactory). At this moment > the reports generated do not include the Dependency Location information. > You can read this thread for a further description: > http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
[ http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149109#action_149109 ] Pablo Graña commented on MPIR-137: -- The workaround does not work for me either. As an additional note, I added: false (I figured it had something to do with this because the doc says that this param is ignored in offilne mode). But build failed with: [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Error on line -1 of document : Premature end of file. Nested exception: Premature end of file. [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) . . . > Dependency Locations should work with an intranet repository and restricted > internet access > --- > > Key: MPIR-137 > URL: http://jira.codehaus.org/browse/MPIR-137 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 > Environment: All environments, no internet access allowed, no > internet proxy configuration, intranet repository configured (Artifactory, > but it seems to happen with Archiva) >Reporter: Diego Parrilla >Priority: Minor > > We use Maven and Artifactory, and the PCs does not have direct internet > access allowed. Maven is configured to mirror the Artifactory repository. So, > all the users have to download their artifacts from the intranet repository. > When launching the 'site' goal (mvn site), when generating the 'Dependencies' > report, it hangs for a long time until we get this error: > [WARNING] The repository url '' is invalid - Repository 'XXX' will be > blacklisted. > It's possible to work around this problem disabling the parameter > 'dependencyLocationEnabled' in the maven-project-info-reports-plugin: > > ... > > org.apache.maven.plugins > maven-project-info-reports-plugin > 2.1 > > false > > > ... > > But I think the dependency locations should be solved using the information > stored in the intranet repository (in my case Artifactory). At this moment > the reports generated do not include the Dependency Location information. > You can read this thread for a further description: > http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
[ http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146805#action_146805 ] Allor Dev commented on MPIR-137: The workaround does not work for me. I had to change maven-project-info-reports-plugin version to 2.0. > Dependency Locations should work with an intranet repository and restricted > internet access > --- > > Key: MPIR-137 > URL: http://jira.codehaus.org/browse/MPIR-137 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 > Environment: All environments, no internet access allowed, no > internet proxy configuration, intranet repository configured (Artifactory, > but it seems to happen with Archiva) >Reporter: Diego Parrilla >Priority: Minor > > We use Maven and Artifactory, and the PCs does not have direct internet > access allowed. Maven is configured to mirror the Artifactory repository. So, > all the users have to download their artifacts from the intranet repository. > When launching the 'site' goal (mvn site), when generating the 'Dependencies' > report, it hangs for a long time until we get this error: > [WARNING] The repository url '' is invalid - Repository 'XXX' will be > blacklisted. > It's possible to work around this problem disabling the parameter > 'dependencyLocationEnabled' in the maven-project-info-reports-plugin: > > ... > > org.apache.maven.plugins > maven-project-info-reports-plugin > 2.1 > > false > > > ... > > But I think the dependency locations should be solved using the information > stored in the intranet repository (in my case Artifactory). At this moment > the reports generated do not include the Dependency Location information. > You can read this thread for a further description: > http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
