You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Lee Meador (JIRA)" <ji...@codehaus.org> on 2005/11/29 18:34:06 UTC
[jira] Created: (MNGECLIPSE-8) Jar from remote repo not loaded and causes error in POM
Jar from remote repo not loaded and causes error in POM
-------------------------------------------------------
Key: MNGECLIPSE-8
URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
Project: Maven 2.x Plug-in for Eclipse
Type: Improvement
Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
Reporter: Lee Meador
Assigned to: Eugene Kuleshov
Priority: Minor
It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNGECLIPSE-8) Jar from remote repo not loaded
and causes error in POM
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=comments#action_55364 ]
Eugene Kuleshov commented on MNGECLIPSE-8:
------------------------------------------
I am not sure what is being suggested here. Red X would appear if Maven fail to download selected artefact.
I am about to commit code that will also index local repository, so search dialog will show both, local and central repository.
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNGECLIPSE-8) Jar from remote repo not loaded and
causes error in POM
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=all ]
Eugene Kuleshov closed MNGECLIPSE-8:
------------------------------------
Resolution: Won't Fix
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Versions: 0.0.3
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNGECLIPSE-8) Jar from remote repo not loaded and
causes error in POM
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=all ]
Eugene Kuleshov reopened MNGECLIPSE-8:
--------------------------------------
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Versions: 0.0.3
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNGECLIPSE-8) Jar from remote repo not loaded
and causes error in POM
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=comments#action_55455 ]
Eugene Kuleshov commented on MNGECLIPSE-8:
------------------------------------------
Are you behind proxy or something?
Please also check Errors view (PDE capability should be enabled) or .metadata/.log file if there are any errors and fill in a separate issue if you find any.
It is also possible that you've chosen some dependency that is not actually available in repository but appears in the index (e.g. some sun jars, etc) then red X will be an indication that artifact is not awailable.
This is very basic functionality and it is working fine for me in case if remore repository has selected dependency/artifact. Add dependency dialog is always using local indexes (in current plugin version it is "central" only), so your situation is always the case. Code in svn already has reindexer for local repository, so search results will include both repositories and we are planning to provide tool for indexing other proprietory repositories.
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNGECLIPSE-8) Jar from remote repo not loaded and
causes error in POM
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=all ]
Eugene Kuleshov closed MNGECLIPSE-8:
------------------------------------
Resolution: Won't Fix
I am getting into the conclusion that the summary you've submitted rather describes plugin feature.
Error is being reported if plugin can't find artifact/dependency in local repository or can't download it locally from the default remote repository (central/ibiblio) or alternative repositories specified in pom.xml
Please reopen this issue with more details how to reproduce unexpected behavious.
Please fill a separate issue if plugin can't download artifacts from alternative repositories specified in pom.xml.
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNGECLIPSE-8) Jar from remote repo not loaded and
causes error in POM
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=all ]
Eugene Kuleshov updated MNGECLIPSE-8:
-------------------------------------
Version: 0.0.3
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Versions: 0.0.3
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNGECLIPSE-8) Jar from remote repo not loaded
and causes error in POM
Posted by "Lee Meador (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=comments#action_55452 ]
Lee Meador commented on MNGECLIPSE-8:
-------------------------------------
Let me describe the process a bit better.
1. You select Maven2 > add dependency from the context menu on a project entry in the package explorer view.
2. You pick a jar file that isn't in the local repository but is, instead, in the remote repository where the searcher window is searching.
3. The entry is added to the POM by the plugin.
4. Some part of the plugin is supposed to update the Maven classpath with that newly added jar. It doesn't do that.
5. A red X appears in the POM beside that jar file's name and the error says the jar file cannot be found.
I hope this has been more informative.
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org