[jira] Updated: (IVYDE-64) Simplify the resolve process
[
https://issues.apache.org/jira/browse/IVYDE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-64:
-
Attachment: IVYDE-64-r600683.patch
So here is a new patch. So as discussed, the {{usePreviousResolveIfExist}}
check is kept. And there is still in the patch the eviction of parsing the
report if we already have the artifacts.
I think I have mostly made the code simpler to understand. The functionnalites
of the code are all here, even some error handling (parsing and IO exception
which is fallbacking to a complete resolve).
I also included in that patch a little part of the patch of IVYDE-43 : use the
IClasspathEntry more than the inner ClasspathItem class.
Then the patch may appear quite big. But I am not sure what the indentation
convention are here. I know there is a migration in progress (IVY-511), but the
convention doesn't specify if we should use spaces or tabs. I personnaly
prefers spaces, so I used them. Editing with eclipse, it did some strange mix,
but I tried to not make the patch appears as a complete diff.
I have tested this patch with some ivy-aware project, it works fine.
Simplify the resolve process
Key: IVYDE-64
URL: https://issues.apache.org/jira/browse/IVYDE-64
Project: IvyDE
Issue Type: Improvement
Components: classpath container
Affects Versions: 1.3.0
Environment: trunk r595956
Reporter: Nicolas Lalevée
Attachments: IVYDE-64-r595956.patch, IVYDE-64-r600683.patch
The current trunk, the resolve job is first checking manually if the artifact
has already been resolved. If not in cache, it let ivy resolve it. And
finally it parses the xml reports in the cache.
So first, as far as I have understood, the manual checking against the cache
is not needed, ivy already does it.
And then ivy produce in Java some resolve report that already contain every
needed information, there is no need to parse the reports in cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-68) IvyDE is using some internal classes of Eclipse
[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-68:
-
Summary: IvyDE is using some internal classes of Eclipse (was: IvyDE is
use-ing some internal classes of Eclipse)
IvyDE is using some internal classes of Eclipse
---
Key: IVYDE-68
URL: https://issues.apache.org/jira/browse/IVYDE-68
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
Some classes in IvyDE use come classes which are in some
{{org.eclipseinternal... }} packages, which should not be used. Compiling
IvyDE with Eclipse 3.3 raise warning like :
{quote}
Discouraged access: The method containerPut(IJavaProject, IPath,
IClasspathContainer) from the type JavaModelManager is not accessible due to
restriction on required library
/Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer
IvyClasspathContainer.java {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-68) IvyDE is use-ing some internal classes of Eclipse
IvyDE is use-ing some internal classes of Eclipse
-
Key: IVYDE-68
URL: https://issues.apache.org/jira/browse/IVYDE-68
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
Some classes in IvyDE use come classes which are in some
{{org.eclipseinternal... }} packages, which should not be used. Compiling
IvyDE with Eclipse 3.3 raise warning like :
{quote}
Discouraged access: The method containerPut(IJavaProject, IPath,
IClasspathContainer) from the type JavaModelManager is not accessible due to
restriction on required library
/Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer
IvyClasspathContainer.java {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-68) IvyDE is using some internal classes of Eclipse
[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-68:
-
Attachment: IVYDE-68-r607532.patch
Here is a patch that fix a part of the bug.
In IvydeContainerPage, the use of TypedElementSelectionValidator has been
replaced by a simple inner implementation of ISelectionStatusValidator
In IvyClasspathUtil, the instanceof check against ClassPathContainer should be
avoided to be replaced by some getAdapter calls. But the internal
implementation does not support them. So the code has been change to use some
getApdapter functions, but the check against ClassPathContainer has been kept
to kept it working. It might need an opening of a bug in eclipse.
IvyClasspathUtil has also been a little refactored so every Actions are getting
the selection the same way.
In IvyClasspathContainer, the instanciation of the ClasspathAttribute is done
with the JavaCore static functions. Some change have aslo been done to be in
sync with the last Ivy API which cache management has changed.
In IvyPlugin : the Java model is now got from JavaCore.
In OpenIvyFileAction : DialogUtil.openError is simple enought to be copied.
The other warnings that have not been fixed in this patch:
* FixedJavaSearchPage : of course, as it is a rewrite of an internal behavior.
* IvyClasspathContainer#notifyUpdateClasspathEntries : there are some use of
JavaModelManager. I don't know what it is used for, so I didn't change it.
* IvyClasspathInitializer#requestClasspathContainerUpdate : it use
JavaDocLocations. It seems there is no other way to accomplish it. As the code
to copy is that trivial, I preferred keep it as is.
There are also included some change in the build.xml and build.properties to
get the last released version of Ivy. I don't know if these changes are still
useful as the dependency is now handled by Eclipse. I have them locally before
the dependency changed, so I provide them here, feel free to revert them if
there are not appropriate.
IvyDE is using some internal classes of Eclipse
---
Key: IVYDE-68
URL: https://issues.apache.org/jira/browse/IVYDE-68
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
Attachments: IVYDE-68-r607532.patch
Some classes in IvyDE use come classes which are in some
{{org.eclipseinternal... }} packages, which should not be used. Compiling
IvyDE with Eclipse 3.3 raise warning like :
{quote}
Discouraged access: The method containerPut(IJavaProject, IPath,
IClasspathContainer) from the type JavaModelManager is not accessible due to
restriction on required library
/Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer
IvyClasspathContainer.java {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-68) IvyDE is using some internal classes of Eclipse
[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556552#action_12556552
]
Nicolas Lalevée commented on IVYDE-68:
--
OK I see the issue, the UI is effectively not very clear. It seems that the
eclipse developer didn't see the real issue here, maybe he didn't read your
last comment ?
About letting the fix into IvyDE, I see no reason to not have this kind of
eclipse internal fix within the plugin. But it seems wrong to have the plugin
only target 3.2. Maybe you could create another plugin
org.apache.ivy.eclipse.javasearchfix that could be downloaded within the IvyDE
update site, with as many version as there are tagetted eclipse version.
IvyDE is using some internal classes of Eclipse
---
Key: IVYDE-68
URL: https://issues.apache.org/jira/browse/IVYDE-68
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
Attachments: IVYDE-68-r607532.patch, ivyde.diff
Some classes in IvyDE use come classes which are in some
{{org.eclipseinternal... }} packages, which should not be used. Compiling
IvyDE with Eclipse 3.3 raise warning like :
{quote}
Discouraged access: The method containerPut(IJavaProject, IPath,
IClasspathContainer) from the type JavaModelManager is not accessible due to
restriction on required library
/Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer
IvyClasspathContainer.java {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-704) In the ResolveReport class, add the possibility to filter the evicted module while getting the list of DownloadArtifact
In the ResolveReport class, add the possibility to filter the evicted module while getting the list of DownloadArtifact --- Key: IVY-704 URL: https://issues.apache.org/jira/browse/IVY-704 Project: Ivy Issue Type: Improvement Components: Core Affects Versions: 2.0.0-beta-2 Reporter: Nicolas Lalevée As disscussed here : http://mail-archives.apache.org/mod_mbox/ant-dev/200801.mbox/[EMAIL PROTECTED] In order to get the list of artifacts which are part of the dependencies of a module, it will be useful to have a function in the ResolveReport class to get the download reports without the ones from the evited modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-704) In the ResolveReport class, add the possibility to filter the evicted module while getting the list of DownloadArtifact
[
https://issues.apache.org/jira/browse/IVY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVY-704:
Attachment: IVY-704-r612799.patch
I have added a generic function {{getArtifactsReports(DownloadStatus
downloadStatus, boolean withEvicted)}} to ResolveReport and
ConfigurationResolveReport.
The one on ConfigurationResolveReport may not be needed. But when I first coded
it, I didn't realized that an artifact in a conf can be evicted in another
conf. Nevertheless this function might be useful, so I let it in the patch.
I also added some minor javadoc improvements.
In the ResolveReport class, add the possibility to filter the evicted module
while getting the list of DownloadArtifact
---
Key: IVY-704
URL: https://issues.apache.org/jira/browse/IVY-704
Project: Ivy
Issue Type: Improvement
Components: Core
Affects Versions: 2.0.0-beta-2
Reporter: Nicolas Lalevée
Attachments: IVY-704-r612799.patch
As disscussed here :
http://mail-archives.apache.org/mod_mbox/ant-dev/200801.mbox/[EMAIL PROTECTED]
In order to get the list of artifacts which are part of the dependencies of a
module, it will be useful to have a function in the ResolveReport class to
get the download reports without the ones from the evited modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-706) The bundle packaging of Ivy is incorrect
[ https://issues.apache.org/jira/browse/IVY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVY-706: Attachment: IVY-706-r612799.patch I have added the jars declaration in the MANIFEST. I have (well Eclipse automatically did it) also added the jars declaration into the build.properties so Eclipse can build it. And I have change the .classpath.default to reflect this change. I didn't change to the .classpath.ivyde as I don't know how to configure eclipse correctly, it seems that using IvyDE within a Eclipse plugin is a bad idea. The bundle packaging of Ivy is incorrect Key: IVY-706 URL: https://issues.apache.org/jira/browse/IVY-706 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Nicolas Lalevée Priority: Minor Attachments: IVY-706-r612799.patch Ivy has recently been packaged as an OSGI bundle by adding a MANIFEST.MF. But it is not correct since the runtime jars are not declared in the manifest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12560410#action_12560410 ] Nicolas Lalevée commented on IVYDE-70: -- In fact we have to deal with it : https://bugs.eclipse.org/bugs/show_bug.cgi?id=139911 The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-706) The bundle packaging of Ivy is incorrect
[
https://issues.apache.org/jira/browse/IVY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12560453#action_12560453
]
Nicolas Lalevée commented on IVY-706:
-
I have no strong opinion about dependencies management with OSGI bundle. I just
know that having the jar embedded evict the library version management issues,
especially with xerces. On the other side we loose the flexibility.
In fact I did this patch to make easier for Eclipse beginner to start playing
with IvyDE with the sources. Probably it is IvyDE that should embed these jars.
So people who wants to build IvyDE trunk can do it directly without
configuration editing. And keep Ivy as a light bundle.
But this bug could not be closed as invalid because the {{Import-Package}}
declarations are need, aren't they ? (I am more an Eclipse player than an
OSGI-spec reader)
The bundle packaging of Ivy is incorrect
Key: IVY-706
URL: https://issues.apache.org/jira/browse/IVY-706
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Reporter: Nicolas Lalevée
Priority: Minor
Attachments: IVY-706-r612799.patch
Ivy has recently been packaged as an OSGI bundle by adding a MANIFEST.MF. But
it is not correct since the runtime jars are not declared in the manifest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-704) In the ResolveReport class, add the possibility to filter the evicted module while getting the list of DownloadArtifact
[
https://issues.apache.org/jira/browse/IVY-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12560533#action_12560533
]
Nicolas Lalevée commented on IVY-704:
-
About the second point, does it means that some evicted modules will still be
returned by {{ResolveReport#getArtifactsReports(DownloadStatus, boolean)}} ?
Because I think there is a use case where an artifact may be retreived by two
different confs, with two different versions; and as far I can see (or debug),
the eviction information is in the conf which contains the not evicted one.
So first, is the evicted info misplaced ?
If correctly placed, then I think either the algorithm should be revert to the
one I posted, or update the javadoc to warn about that use case.
In the ResolveReport class, add the possibility to filter the evicted module
while getting the list of DownloadArtifact
---
Key: IVY-704
URL: https://issues.apache.org/jira/browse/IVY-704
Project: Ivy
Issue Type: Improvement
Components: Core
Affects Versions: 2.0.0-beta-2
Reporter: Nicolas Lalevée
Fix For: 2.0.0-beta-2
Attachments: IVY-704-r612799.patch
As disscussed here :
http://mail-archives.apache.org/mod_mbox/ant-dev/200801.mbox/[EMAIL PROTECTED]
In order to get the list of artifacts which are part of the dependencies of a
module, it will be useful to have a function in the ResolveReport class to
get the download reports without the ones from the evited modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-706) The bundle packaging of Ivy is incorrect
[ https://issues.apache.org/jira/browse/IVY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12560519#action_12560519 ] Nicolas Lalevée commented on IVY-706: - ha, yes ! of course. The bundle packaging of Ivy is incorrect Key: IVY-706 URL: https://issues.apache.org/jira/browse/IVY-706 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Nicolas Lalevée Priority: Minor Attachments: IVY-706-r612799.patch Ivy has recently been packaged as an OSGI bundle by adding a MANIFEST.MF. But it is not correct since the runtime jars are not declared in the manifest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562078#action_12562078 ] Nicolas Lalevée commented on IVYDE-70: -- Still not sucessfull with the former solution. I asked help there : http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.platform/msg71811.html If I have no response I will go forward the second solution. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-69) Order alphabetically the entries in the class path container
[ https://issues.apache.org/jira/browse/IVYDE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-69: - Attachment: IVYDE-69-r614873.patch Here is a patch that will keep the default ordering as Ivy one. To have the alphabetical order the user will have to confiure it in its project preference page. Order alphabetically the entries in the class path container Key: IVYDE-69 URL: https://issues.apache.org/jira/browse/IVYDE-69 Project: IvyDE Issue Type: New Feature Components: classpath container Affects Versions: 1.3.0 Reporter: Nicolas Lalevée Priority: Minor Attachments: IVYDE-69-r614873.patch, IVYDE-69.patch Just a tiny contribution to make entries ordered alphabetically to make easier to parse visually -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-66) IvyDE source artifact not recognised
[
https://issues.apache.org/jira/browse/IVYDE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-66:
-
Attachment: IVYDE-66-r616804.patch
Here is a patch that tries to make sources and jars match even if they don't
have the same name.
It will actually match if there is a -src, or a -sources, or a -source
suffix.
I also forced some match for the javadoc with the -javadoc and -javadocs
suffixes.
IvyDE source artifact not recognised
Key: IVYDE-66
URL: https://issues.apache.org/jira/browse/IVYDE-66
Project: IvyDE
Issue Type: Bug
Components: classpath container
Reporter: Gerard Fernandes
Attachments: IVYDE-66-r616804.patch
IvyDE doesn't recognise source artifacts with a different name than the
binary artifact.
E.g., If I have a JAR called commons-cli-1.1.jar and it's source called
commons-cli-src-1.1.zip, an Ivy configuration with the following will resolve
and the sources are downloaded (can be confirmed by the Ivy report as well as
checking the cache) but will NOT attach sources in Eclipse:
dependency org=jakarta-commons-cli name=commons-cli
rev=1.1 conf=COMPILE,RUNTIME,TEST-default
artifact name=commons-cli type=jar/
artifact name=commons-cli-src type=source
ext=zip conf=COMPILE /
/dependency
Ivy settings are:
filesystem name=externalLibraries
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]/
/filesystem
The only way to make this work is to change Ivy settings to:
filesystem name=externalLibraries
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]-src.[ext]/
/filesystem
And rename
commons-cli-src-1.1.zip
To
commons-cli-1.1-src.zip
And finally change the Ivy configuration to:
dependency org=jakarta-commons-cli name=commons-cli
rev=1.1 conf=COMPILE,RUNTIME,TEST-default
artifact name=commons-cli type=jar/
artifact name=commons-cli type=source ext=zip
conf=COMPILE /
/dependency
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-66) IvyDE source artifact not recognised
[
https://issues.apache.org/jira/browse/IVYDE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-66:
-
Attachment: IVYDE-66-r616804.patch
I have just noticed IVYDE-49 which might be a duplicate of this one.
So as suggested there, I added -doc and -docs to match with the javadocs
IvyDE source artifact not recognised
Key: IVYDE-66
URL: https://issues.apache.org/jira/browse/IVYDE-66
Project: IvyDE
Issue Type: Bug
Components: classpath container
Reporter: Gerard Fernandes
Attachments: IVYDE-66-r616804.patch, IVYDE-66-r616804.patch
IvyDE doesn't recognise source artifacts with a different name than the
binary artifact.
E.g., If I have a JAR called commons-cli-1.1.jar and it's source called
commons-cli-src-1.1.zip, an Ivy configuration with the following will resolve
and the sources are downloaded (can be confirmed by the Ivy report as well as
checking the cache) but will NOT attach sources in Eclipse:
dependency org=jakarta-commons-cli name=commons-cli
rev=1.1 conf=COMPILE,RUNTIME,TEST-default
artifact name=commons-cli type=jar/
artifact name=commons-cli-src type=source
ext=zip conf=COMPILE /
/dependency
Ivy settings are:
filesystem name=externalLibraries
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]/
/filesystem
The only way to make this work is to change Ivy settings to:
filesystem name=externalLibraries
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact].[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-src.[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision].[ext]/
artifact
pattern=${ivy.conf.dir}/[organisation]/[revision]/[artifact]-[revision]-src.[ext]/
/filesystem
And rename
commons-cli-src-1.1.zip
To
commons-cli-1.1-src.zip
And finally change the Ivy configuration to:
dependency org=jakarta-commons-cli name=commons-cli
rev=1.1 conf=COMPILE,RUNTIME,TEST-default
artifact name=commons-cli type=jar/
artifact name=commons-cli type=source ext=zip
conf=COMPILE /
/dependency
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-68) IvyDE is using some internal classes of Eclipse
[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-68:
-
Attachment: IVYDE-68-r617088.patch
Here is a patch that resolve the use of interla eclipse classes in
IvyClasspathContainer. It has been taken from the patch of IVYDE-43 :
{noformat}
-JavaModelManager manager =
JavaModelManager.getJavaModelManager();
-manager.containerPut(_javaProject, _path, null);
+// EG: JavaModelManager manager =
JavaModelManager.getJavaModelManager();
+// EG: manager.containerPut(_javaProject, _path, null);
+// EG: Do not clear the container - let the model manager
compare new container with the old and decide if it's changing
JavaCore.setClasspathContainer(
_path,
new IJavaProject[] {_javaProject},
-new IClasspathContainer[]
{IvyClasspathContainer.this},
+new IClasspathContainer[] {new
IvyClasspathContainer(IvyClasspathContainer.this)},
null);
{noformat}
I tested locally, it works correctly.
IvyDE is using some internal classes of Eclipse
---
Key: IVYDE-68
URL: https://issues.apache.org/jira/browse/IVYDE-68
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
Attachments: IVYDE-68-r607532.patch, IVYDE-68-r617088.patch,
ivyde.diff
Some classes in IvyDE use come classes which are in some
{{org.eclipseinternal... }} packages, which should not be used. Compiling
IvyDE with Eclipse 3.3 raise warning like :
{quote}
Discouraged access: The method containerPut(IJavaProject, IPath,
IClasspathContainer) from the type JavaModelManager is not accessible due to
restriction on required library
/Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer
IvyClasspathContainer.java {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-70: - Attachment: IVYDE-70-preferenceListenerTry.patch I have got no response from the mailing list, so I started implementing the preference-listener solution (see the attached patch). But then I run into too big issues. First we have to mark an IvyDE default configuration as being default rather than not storing a configuration. But the process of creating the classpath container is embedded into the JDT process, IvyDE only implement IvydeContainerPage. So there is no obvious way to control the preferences. And then in my tests, the build is triggered twice. After the refresh, the resolve job is triggered, but also the build one. The build job doesn't wait for the resolve job to be finished, so it is triggered a second time after the resolve job actually updates the classpath. Then rethinking about how the JDT works, it finally seems that having preferences to control a class path container is wrong. And in fact IvyDE has two configuration panes: the one which control the conf to resolve, and the one which control the ivysettings url, the jar, source, javadocs types, etc... Then I browsed the JDT classes and I have found the IClasspathAttribute, which should be used to store extra configuration about the class path entry. So it seems that this Jira issue will be resolved properly if we merge the two confiuration panes, and if we make the current preferences stored as classpath extra attributes (which will finally get stored into the .classpath). So unless there are objections about merging the two confiuration panes, I will do a patch for this last solution. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569836#action_12569836 ] Nicolas Lalevée commented on IVYDE-70: -- Bad news. Whereas the configuration of an existing class path container works well with classpath attributes, the creation doesn't. The JDT doesn't care about the classpath attributes given from the ContainerPage. Again I asked help (now at the right place) http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.tools.jdt/msg22184.html But I got no good answer yet. So finally I think that the configuration should be in the container path. I will try that. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570339#action_12570339 ] Nicolas Lalevée commented on IVYDE-70: -- About the container path. For Eclipse, it is a IPath. So as far as I understand, it is a path as in a URL. So it could be possible to implement what you suggest. In fact here is the scheme I implemented : org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/conf/ivysetting.xml/acceptedTypes/sourceTypes/javadocTypes/sourceSuffixes/javadocSuffixes/doRetrieve/retreivePattern/order knowing that the ivy.xml, ivysettings.xml and the retrieve pattern are URL encoded. Hum.. and in fact I just realized that it should be the case for every configuration entry, the user can broke its config in putting a / in its javadocTypes for instance. So it won't be that different from what you suggested. It will be quite easy to write the serializer, but the parser might be more complicated. I need to check the query string spec. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[
https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570290#action_12570290
]
Nicolas Lalevée commented on IVYDE-70:
--
Phew, finnaly I get it working with the IPath of the container, so the
.classpath will be like :
{noformat}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src path=/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/*/file%3A%2Fhome%2Fnicolasl%2Fdev%2Fivy%2Fivysettings.xml/jar/source,src/javadoc/-source,-sources,-src/-javadoc,-javadocs,-doc,-docs/false/lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5D/alpha/
classpathentry kind=output path=/
/classpath
{noformat}
Cleaning up the code I wrote, I will provide a patch soon.
The project ivy configuration is not taken into account on the first run
Key: IVYDE-70
URL: https://issues.apache.org/jira/browse/IVYDE-70
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2
Reporter: Nicolas Lalevée
Attachments: IVYDE-70-preferenceListenerTry.patch
Starting with an empty workspace, I import a project which already have its
Ivy preferences configured.
After the import the classpath is made of some ibiblio jars, whereas I was
expecting the ones from my internal repository. After a resolve, the
classpath has the proper jars, from my internal repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-70: - Attachment: IVYDE-70.patch Here is a patch. So: * the two configuration panes merged * the configuration pane has a global project specific settings check box * now we can only finish the configuration panes if it is correctly configured (some disabled finish button) A little about the implementation: * the container configuration is defined in the container path. The paths (ivysettings, ivy.xml paths) are URL encoded * the configuration that was managed in the IvyPlugin is now handled in two new beans: the global configuration and the container one. The code is now simpler. I have tested with some tiny projects, it works fine. But due to the big change, the patch should be also tested with bigger project, and also with project having default ivysettings. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-78) Add errors marker to the Ivy container
Add errors marker to the Ivy container -- Key: IVYDE-78 URL: https://issues.apache.org/jira/browse/IVYDE-78 Project: IvyDE Issue Type: Improvement Components: classpath container Affects Versions: 1.3.0 Reporter: Nicolas Lalevée Priority: Minor It should be nice to use Eclipse error markers to show that the last resolution on the Ivy container failed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[
https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-70:
-
Attachment: IVYDE-70-urlish.patch
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least
the ivy.xml and the confs as the other part of the configuration is contain is
the preference which cannot be loaded due to the bug this patch is trying to
fix.
By the way, the result in the .classpath is not exactly what we expected, there
are some {{amp;}} :
{code:xml}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/java/
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/resources/
classpathentry kind=src output=bin path=src/test/java/
classpathentry kind=src output=bin path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xmlamp;confs=*amp;ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xmlamp;acceptedTypes=jaramp;sourceTypes=source%2Csrcamp;javadocTypes=javadocamp;sourceSuffixes=-source%2C-sources%2C-srcamp;javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docsamp;doRetrieve=falseamp;retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5Damp;alphaOrder=true/
classpathentry kind=output path=src/main/webapp/WEB-INF/classes/
/classpath
{code:xml}
The project ivy configuration is not taken into account on the first run
Key: IVYDE-70
URL: https://issues.apache.org/jira/browse/IVYDE-70
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2
Reporter: Nicolas Lalevée
Attachments: IVYDE-70-preferenceListenerTry.patch,
IVYDE-70-urlish.patch, IVYDE-70.patch
Starting with an empty workspace, I import a project which already have its
Ivy preferences configured.
After the import the classpath is made of some ibiblio jars, whereas I was
expecting the ones from my internal repository. After a resolve, the
classpath has the proper jars, from my internal repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[
https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570774#action_12570774
]
hibou edited comment on IVYDE-70 at 2/20/08 9:47 AM:
---
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least
the ivy.xml and the confs as the other part of the configuration is contain is
the preference which cannot be loaded due to the bug this patch is trying to
fix.
By the way, the result in the .classpath is not exactly what we expected, there
are some {{amp;}} :
{code:xml}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/java/
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/resources/
classpathentry kind=src output=bin path=src/test/java/
classpathentry kind=src output=bin path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xmlamp;confs=*amp;ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xmlamp;acceptedTypes=jaramp;sourceTypes=source%2Csrcamp;javadocTypes=javadocamp;sourceSuffixes=-source%2C-sources%2C-srcamp;javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docsamp;doRetrieve=falseamp;retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5Damp;alphaOrder=true/
classpathentry kind=output path=src/main/webapp/WEB-INF/classes/
/classpath
{code}
was (Author: hibou):
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least
the ivy.xml and the confs as the other part of the configuration is contain is
the preference which cannot be loaded due to the bug this patch is trying to
fix.
By the way, the result in the .classpath is not exactly what we expected, there
are some {{amp;}} :
{code:xml}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/java/
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/resources/
classpathentry kind=src output=bin path=src/test/java/
classpathentry kind=src output=bin path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xmlamp;confs=*amp;ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xmlamp;acceptedTypes=jaramp;sourceTypes=source%2Csrcamp;javadocTypes=javadocamp;sourceSuffixes=-source%2C-sources%2C-srcamp;javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docsamp;doRetrieve=falseamp;retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5Damp;alphaOrder=true/
classpathentry kind=output path=src/main/webapp/WEB-INF/classes/
/classpath
{code:xml}
The project ivy configuration is not taken into account on the first run
Key: IVYDE-70
URL: https://issues.apache.org/jira/browse/IVYDE-70
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2
Reporter: Nicolas Lalevée
Attachments: IVYDE-70-preferenceListenerTry.patch,
IVYDE-70-urlish.patch, IVYDE-70.patch
Starting with an empty workspace, I import a project which already have its
Ivy preferences configured.
After the import the classpath is made of some ibiblio jars, whereas I was
expecting the ones from my internal repository. After a resolve, the
classpath has the proper jars, from my internal repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[
https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570774#action_12570774
]
hibou edited comment on IVYDE-70 at 2/20/08 9:49 AM:
---
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least
the ivy.xml and the confs as the other part of the configuration is contain is
the preference which cannot be loaded due to the bug this patch is trying to
fix.
By the way, the result in the .classpath is not exactly what we expected, there
are some amp ; :
{code:xml}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/java/
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/resources/
classpathentry kind=src output=bin path=src/test/java/
classpathentry kind=src output=bin path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xmlamp;confs=*amp;ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xmlamp;acceptedTypes=jaramp;sourceTypes=source%2Csrcamp;javadocTypes=javadocamp;sourceSuffixes=-source%2C-sources%2C-srcamp;javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docsamp;doRetrieve=falseamp;retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5Damp;alphaOrder=true/
classpathentry kind=output path=src/main/webapp/WEB-INF/classes/
/classpath
{code}
was (Author: hibou):
So here is a path with some URLish container path.
I also made the plugin read properly IvyDE-1.3 configurations; well at least
the ivy.xml and the confs as the other part of the configuration is contain is
the preference which cannot be loaded due to the bug this patch is trying to
fix.
By the way, the result in the .classpath is not exactly what we expected, there
are some {{amp;}} :
{code:xml}
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/java/
classpathentry kind=src output=src/main/webapp/WEB-INF/classes
path=src/main/resources/
classpathentry kind=src output=bin path=src/test/java/
classpathentry kind=src output=bin path=src/test/resources/
classpathentry kind=con
path=org.eclipse.jdt.launching.JRE_CONTAINER/
classpathentry kind=con
path=org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?ivyXmlPath=ivy.xmlamp;confs=*amp;ivySettingsPath=file%3A%2Fhome%2Fnicolasl%2Fdev%2Fjoost%2Fsvn%2Fcode%2Fbistro%2Ftools%2F1.0%2Fivyconf-eclipse.xmlamp;acceptedTypes=jaramp;sourceTypes=source%2Csrcamp;javadocTypes=javadocamp;sourceSuffixes=-source%2C-sources%2C-srcamp;javadocSuffixes=-javadoc%2C-javadocs%2C-doc%2C-docsamp;doRetrieve=falseamp;retreivePattern=lib%2F%5Bconf%5D%2F%5Bartifact%5D.%5Bext%5Damp;alphaOrder=true/
classpathentry kind=output path=src/main/webapp/WEB-INF/classes/
/classpath
{code}
The project ivy configuration is not taken into account on the first run
Key: IVYDE-70
URL: https://issues.apache.org/jira/browse/IVYDE-70
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2
Reporter: Nicolas Lalevée
Attachments: IVYDE-70-preferenceListenerTry.patch,
IVYDE-70-urlish.patch, IVYDE-70.patch
Starting with an empty workspace, I import a project which already have its
Ivy preferences configured.
After the import the classpath is made of some ibiblio jars, whereas I was
expecting the ones from my internal repository. After a resolve, the
classpath has the proper jars, from my internal repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-70: - Attachment: IVYDE-70-urlish-r629733.patch Updated path which fix some introduced bugs: * if there were no the project specific conf, the global one was not taken into account * in the container page, if there is no the project specific conf, the grayed values are now the global configuration ones * add some panaoïd check at the .classpath loading. Raising some Exception during to load of the .classpath is making Eclipse completely lost. * container resolve job was not triggered on global configuration change * add a configuration entry for the alphabetical order in the global Ivy config The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish.patch, IVYDE-70.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-70: - Attachment: IVYDE-70-urlish-r629775.patch héhé :) So here is a patch with corrected spell mistake. One will still exist, the one in the global preference properties file, but I think it is better to keep compatibility than correcting an internal spell mistake. I also fixed the link in the ivy container configuration page to the global Ivy configuration one. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish.patch, IVYDE-70.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-80) ant-build triggers cause ivyde build exception
[ https://issues.apache.org/jira/browse/IVYDE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572418#action_12572418 ] Nicolas Lalevée commented on IVYDE-80: -- I don't understand what is the issue here. Why it is different from the IVYDE-79 ? ant-build triggers cause ivyde build exception -- Key: IVYDE-80 URL: https://issues.apache.org/jira/browse/IVYDE-80 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: eclipse 3.3.1.1, openSuse 10.3 Reporter: Jonathan Doklovic If I have an ant-build trigger in my settings file, ivyde causes a parse error and tries to throw an ant BuildException inside of eclipse. If I have an ant-call trigger, the parsing is fine, however it breaks my trigger (needs to use ant-build) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-80) ant-build triggers cause ivyde build exception
[ https://issues.apache.org/jira/browse/IVYDE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572510#action_12572510 ] Nicolas Lalevée commented on IVYDE-80: -- Yep there is a classloader issue which is raised in IVYDE-79. But I don't see the purpose of this second issue. ant-build triggers cause ivyde build exception -- Key: IVYDE-80 URL: https://issues.apache.org/jira/browse/IVYDE-80 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: eclipse 3.3.1.1, openSuse 10.3 Reporter: Jonathan Doklovic If I have an ant-build trigger in my settings file, ivyde causes a parse error and tries to throw an ant BuildException inside of eclipse. If I have an ant-call trigger, the parsing is fine, however it breaks my trigger (needs to use ant-build) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-79) Loading config causes BuildException and eclipse freaks out
[ https://issues.apache.org/jira/browse/IVYDE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572830#action_12572830 ] Nicolas Lalevée commented on IVYDE-79: -- So does IVYDE-80 fixed this one ? Loading config causes BuildException and eclipse freaks out --- Key: IVYDE-79 URL: https://issues.apache.org/jira/browse/IVYDE-79 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.3.0 Environment: eclipse 3.3.1.1, openSuse 10.3 Reporter: Jonathan Doklovic When I set the ivy settings file in preferences, I get an error in eclipse. It seems like ivyde has problems parsing my settings file even though it works fine from ant. Unfortunately, the error in eclipse is: java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException so i can't really get at the real issue. The error occurs anytime ivyde needs to parse the settings. For space sake, here's the stack trace when i try to resolve: !ENTRY org.eclipse.core.jobs 4 2 2008-02-22 13:05:28.439 !MESSAGE An internal error occurred during: Resolve all dependencies. !STACK 0 java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.apache.ivy.util.Configurator.addChild(Configurator.java:548) at org.apache.ivy.util.Configurator.startCreateChild(Configurator.java:477) at org.apache.ivy.core.settings.XmlSettingsParser.startElement(XmlSettingsParser.java:177) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1337) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2740) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at org.apache.ivy.core.settings.XmlSettingsParser.doParse(XmlSettingsParser.java:92) at org.apache.ivy.core.settings.XmlSettingsParser.parse(XmlSettingsParser.java:84) at org.apache.ivy.core.settings.IvySettings.load(IvySettings.java:350) at org.apache.ivy.Ivy.configure(Ivy.java:254) at org.apache.ivyde.eclipse.IvyPlugin.refreshIvyConfiguration(IvyPlugin.java:289) at org.apache.ivyde.eclipse.IvyPlugin.getIvy(IvyPlugin.java:209) at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries(IvyClasspathContainer.java:524) at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.resolve(IvyClasspathContainer.java:548) at org.apache.ivyde.eclipse.ui.actions.ResolveAllAction$1.run(ResolveAllAction.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.ClassNotFoundException: org.apache.tools.ant.BuildException at java.lang.ClassLoader.findClass(ClassLoader.java:358) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:429) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83
[jira] Commented: (IVY-748) Exclude Ant jar from bin-with-deps distribution format
[ https://issues.apache.org/jira/browse/IVY-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572842#action_12572842 ] Jan Matèrne commented on IVY-748: - An installer would be fine: Ivy ;) A bootstrap Ivy download without any dependency and working from commandline and a starter which asks for the dependency to load and then load them. Maybe some profiles: command line - Ant - IvyDE - all ... the starter could also be a WebStart application (just thinking loud ...) Exclude Ant jar from bin-with-deps distribution format -- Key: IVY-748 URL: https://issues.apache.org/jira/browse/IVY-748 Project: Ivy Issue Type: Task Reporter: Xavier Hanin Fix For: 2.0 Currently we package in bin-with-deps distribution all Ivy dependencies, including ant jar. But this doesn't make sense, people who want to use Ivy with Ant will first install Ant, then Ivy. So we should exclude ant jar from our bin-with-deps distributions format. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574535#action_12574535 ] Nicolas Lalevée commented on IVYDE-70: -- I worked on Eclipse 3.2 while creating the patch. I did not see any major issues yet. I tested on Eclipse 3.3 : one annoying bug : if the resolved classpath is empty, the classpath container disapear... I think it will deserve a seperate issue as soon as this one is committed. I have colleague which works with Eclipse 3.4M4 : same as 3.3. The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish.patch, IVYDE-70.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-81) An error occur when closing a project while the ivy editor is open
An error occur when closing a project while the ivy editor is open
--
Key: IVYDE-81
URL: https://issues.apache.org/jira/browse/IVYDE-81
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2, 3.3, 3.4M5
Reporter: Nicolas Lalevée
The project have to hold a ivy.xml, this file being edited by the Ivy editor.
Then close the project. On close the editor should also be closed, but it fails.
Here is the stack trace from the error log view.
{noformat}
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.ClassCastException:
org.apache.ivyde.eclipse.ui.core.IvyFileEditorInput cannot be cast to
org.eclipse.ui.part.FileEditorInput)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
Caused by: java.lang.ClassCastException:
org.apache.ivyde.eclipse.ui.core.IvyFileEditorInput cannot be cast to
org.eclipse.ui.part.FileEditorInput
at
org.apache.ivyde.eclipse.ui.editors.IvyEditor$1.run(IvyEditor.java:198)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
... 23 more
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-81) An error occur when closing a project while the ivy editor is open
[
https://issues.apache.org/jira/browse/IVYDE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-81:
-
Attachment: IVYDE-81-r633150.patch
Here is a simple patch that fix the issue: I think that it was a spelling
mistake.
An error occur when closing a project while the ivy editor is open
--
Key: IVYDE-81
URL: https://issues.apache.org/jira/browse/IVYDE-81
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2, 3.3, 3.4M5
Reporter: Nicolas Lalevée
Attachments: IVYDE-81-r633150.patch
The project have to hold a ivy.xml, this file being edited by the Ivy editor.
Then close the project. On close the editor should also be closed, but it
fails.
Here is the stack trace from the error log view.
{noformat}
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.ClassCastException:
org.apache.ivyde.eclipse.ui.core.IvyFileEditorInput cannot be cast to
org.eclipse.ui.part.FileEditorInput)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
Caused by: java.lang.ClassCastException:
org.apache.ivyde.eclipse.ui.core.IvyFileEditorInput cannot be cast to
org.eclipse.ui.part.FileEditorInput
at
org.apache.ivyde.eclipse.ui.editors.IvyEditor$1.run(IvyEditor.java:198)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
... 23 more
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-761) The m2 parser doesn't recognize sources and javadocs
The m2 parser doesn't recognize sources and javadocs Key: IVY-761 URL: https://issues.apache.org/jira/browse/IVY-761 Project: Ivy Issue Type: Improvement Components: Maven Compatibility Affects Versions: 2.0.0-beta-2 Reporter: Nicolas Lalevée When using the ibibio resolver, the generated ivy.xml doesn't include source and javadoc artifacts declaration. AFAIU the Maven doc, the pom.xml doesn't declare them. They declare themself by being available or not. IvyDE does this check itself, so it works fine in Eclipse. So some code should be ported from IvyDE to Ivy. Then we will be able to get the source also with an ant task. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-764) ssh resolver sets very restrictive file permissions when publishing artifacts
ssh resolver sets very restrictive file permissions when publishing artifacts - Key: IVY-764 URL: https://issues.apache.org/jira/browse/IVY-764 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Tero Hagström When we use the ssh resolver to publish artifacts to a repository on our server, the access permissions of the created files only allow reading by the user that published the artifacts. As a result, no one else can get the artifacts from the repository, which completely defeats it's purpose. File permissions look like this: -rw--- 1 atu dev 875 Mar 10 12:34 core-20080310123411.jar -rw--- 1 atu dev 40 Mar 10 12:34 core-20080310123411.jar.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 core-20080310123411.jar.md5 -rw--- 1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml -rw--- 1 atu dev 40 Mar 10 12:34 ivy-20080310123411.xml.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 ivy-20080310123411.xml.md5 I could not find any way to configure or otherwise affect the file permissions. Is there a way? BTW, with Ivy 1.4.1 the permissions looked like this: -rw-rw-r-- 1 th dev 877 Mar 6 10:08 core-20080306100813.jar -rw-rw-r-- 1 th dev 40 Mar 6 10:08 core-20080306100813.jar.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 core-20080306100813.jar.md5 -rw-rw-r-- 1 th dev 166 Mar 6 10:08 ivy-20080306100813.xml -rw-rw-r-- 1 th dev 40 Mar 6 10:08 ivy-20080306100813.xml.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 ivy-20080306100813.xml.md5 We will now fall back to using Ivy version 1.4.1, for the time being. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-738) Support dynamic revisions with ftp in URLResolver
[
https://issues.apache.org/jira/browse/IVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577525#action_12577525
]
Nicolas Lalevée commented on IVY-738:
-
There is no such IvyDE version.
But I OSGI-fied common-vfs, quite manually thought. You can give a try and
install it into you Eclipse plugins directory:
http://www.hibnet.org/ivyde/updatesite/plugins/
I don't know if it works, neither if it needs another OSGI dependency.
Support dynamic revisions with ftp in URLResolver
-
Key: IVY-738
URL: https://issues.apache.org/jira/browse/IVY-738
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-1
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml,
ivy.xml, test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file permissions when publishing artifacts
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1258#action_1258 ] Tero Hagström commented on IVY-764: --- We added a cron job on the server that chmods all files in our repository, so we currently have a clumsy workaround. How is the Ivy ssh resolver supposed to work with regard to the file permissions set for the published files? ssh resolver sets very restrictive file permissions when publishing artifacts - Key: IVY-764 URL: https://issues.apache.org/jira/browse/IVY-764 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Tero Hagström When we use the ssh resolver to publish artifacts to a repository on our server, the access permissions of the created files only allow reading by the user that published the artifacts. As a result, no one else can get the artifacts from the repository, which completely defeats it's purpose. File permissions look like this: -rw--- 1 atu dev 875 Mar 10 12:34 core-20080310123411.jar -rw--- 1 atu dev 40 Mar 10 12:34 core-20080310123411.jar.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 core-20080310123411.jar.md5 -rw--- 1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml -rw--- 1 atu dev 40 Mar 10 12:34 ivy-20080310123411.xml.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 ivy-20080310123411.xml.md5 I could not find any way to configure or otherwise affect the file permissions. Is there a way? BTW, with Ivy 1.4.1 the permissions looked like this: -rw-rw-r-- 1 th dev 877 Mar 6 10:08 core-20080306100813.jar -rw-rw-r-- 1 th dev 40 Mar 6 10:08 core-20080306100813.jar.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 core-20080306100813.jar.md5 -rw-rw-r-- 1 th dev 166 Mar 6 10:08 ivy-20080306100813.xml -rw-rw-r-- 1 th dev 40 Mar 6 10:08 ivy-20080306100813.xml.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 ivy-20080306100813.xml.md5 We will now fall back to using Ivy version 1.4.1, for the time being. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-84) NPE that break eclipse: the Java project becomes empty
NPE that break eclipse: the Java project becomes empty
--
Key: IVYDE-84
URL: https://issues.apache.org/jira/browse/IVYDE-84
Project: IvyDE
Issue Type: Bug
Environment: IvyDE trunk with IVYDE-70, IVYDE-81 and IVYDE-82 patchs
Reporter: Nicolas Lalevée
here is the stack trace:
{noformat}
java.lang.NullPointerException
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.scheduleRefresh(IvyClasspathContainer.java:714)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathInitializer.initialize(IvyClasspathInitializer.java:76)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2218)
at
org.eclipse.jdt.internal.core.JavaModelManager$9.run(JavaModelManager.java:2148)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2162)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1544)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1571)
at
org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2558)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1848)
at
org.eclipse.jdt.internal.core.DeltaProcessor.createExternalArchiveDelta(DeltaProcessor.java:802)
at
org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1897)
at
org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:368)
at
org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276)
at
org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
at
org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311)
at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-84) NPE that break eclipse: the Java project becomes empty
[
https://issues.apache.org/jira/browse/IVYDE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-84:
-
Affects Version/s: 1.3.0
NPE that break eclipse: the Java project becomes empty
--
Key: IVYDE-84
URL: https://issues.apache.org/jira/browse/IVYDE-84
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: IvyDE trunk with IVYDE-70, IVYDE-81 and IVYDE-82 patchs
Reporter: Nicolas Lalevée
here is the stack trace:
{noformat}
java.lang.NullPointerException
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.scheduleRefresh(IvyClasspathContainer.java:714)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathInitializer.initialize(IvyClasspathInitializer.java:76)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2218)
at
org.eclipse.jdt.internal.core.JavaModelManager$9.run(JavaModelManager.java:2148)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2162)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1544)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1571)
at
org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2558)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1848)
at
org.eclipse.jdt.internal.core.DeltaProcessor.createExternalArchiveDelta(DeltaProcessor.java:802)
at
org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1897)
at
org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:368)
at
org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276)
at
org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
at
org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311)
at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-84) NPE that break eclipse: the Java project becomes empty
[
https://issues.apache.org/jira/browse/IVYDE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577895#action_12577895
]
Nicolas Lalevée commented on IVYDE-84:
--
The NPE is in fact raised because the ivysettings.xml specified in the
configuration doesn't exist.
Bug found thanks to Philippe Gassmann.
NPE that break eclipse: the Java project becomes empty
--
Key: IVYDE-84
URL: https://issues.apache.org/jira/browse/IVYDE-84
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: IvyDE trunk with IVYDE-70, IVYDE-81 and IVYDE-82 patchs
Reporter: Nicolas Lalevée
here is the stack trace:
{noformat}
java.lang.NullPointerException
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.scheduleRefresh(IvyClasspathContainer.java:714)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathInitializer.initialize(IvyClasspathInitializer.java:76)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2218)
at
org.eclipse.jdt.internal.core.JavaModelManager$9.run(JavaModelManager.java:2148)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2162)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1544)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1571)
at
org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2558)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1848)
at
org.eclipse.jdt.internal.core.DeltaProcessor.createExternalArchiveDelta(DeltaProcessor.java:802)
at
org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1897)
at
org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:368)
at
org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276)
at
org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
at
org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311)
at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-85) On classpath issues the user is not notified
On classpath issues the user is not notified
Key: IVYDE-85
URL: https://issues.apache.org/jira/browse/IVYDE-85
Project: IvyDE
Issue Type: Improvement
Affects Versions: 1.3.0
Reporter: Nicolas Lalevée
The classpath issues from IVY-738 generate an entry in the error log, but
nothing popup to notify the user that the resolve fails.
Here is the stack trace:
{noformat}
java.lang.reflect.InvocationTargetException
at
org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:383)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at
org.eclipse.jdt.internal.ui.wizards.buildpaths.newsourcepage.AddLibraryToBuildpathAction$1.performFinish(AddLibraryToBuildpathAction.java:126)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.jdt.internal.ui.wizards.buildpaths.newsourcepage.AddLibraryToBuildpathAction.run(AddLibraryToBuildpathAction.java:185)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Caused by: java.lang.NoClassDefFoundError:
org/apache/commons/vfs/FileSystemException
at org.apache.ivy.plugins.resolver.VfsResolver.init(VfsResolver.java:34)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.apache.ivy.util.Configurator.addChild(Configurator.java:560)
at org.apache.ivy.util.Configurator.startCreateChild(Configurator.java:482)
at
org.apache.ivy.core.settings.XmlSettingsParser.startElement(XmlSettingsParser.java:186)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:878
[jira] Commented: (IVY-738) Support dynamic revisions with ftp in URLResolver
[
https://issues.apache.org/jira/browse/IVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578204#action_12578204
]
Nicolas Lalevée commented on IVY-738:
-
ah forgot to set the magic Elclipse {{-clean}} argument. Next bundle to find,
commons-loggin:
{noformat}
Exception in thread Thread-3 java.lang.NoClassDefFoundError:
org/apache/commons/logging/LogFactory
{noformat}
Support dynamic revisions with ftp in URLResolver
-
Key: IVY-738
URL: https://issues.apache.org/jira/browse/IVY-738
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-1
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml,
ivy.xml, test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM
[jira] Commented: (IVY-738) Support dynamic revisions with ftp in URLResolver
[
https://issues.apache.org/jira/browse/IVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578669#action_12578669
]
Nicolas Lalevée commented on IVY-738:
-
Did you started your Eclipse with the {{-clean}} option ?
If you want to have debug info about the classloader, start Eclipse with:
{{./eclipse -clean -debug /somewhere/option.debug}}
option.debug being a file containing the line:
{{org.eclipse.osgi/debug/loader=true}}
Support dynamic revisions with ftp in URLResolver
-
Key: IVY-738
URL: https://issues.apache.org/jira/browse/IVY-738
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-1
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: IVY-738.patch, ivy-settings-ivyde1_2.xml,
ivy-settings-ivyde1_3.xml, ivy.xml, test_ant.txt, test_ant_debug.txt,
test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http
[jira] Commented: (IVY-738) Support dynamic revisions with ftp in URLResolver
[
https://issues.apache.org/jira/browse/IVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578731#action_12578731
]
Nicolas Lalevée commented on IVY-738:
-
I have build an Ivy with the patched MANIFEST.MF, but I didn't integrated into
the update site. You can download it manually from there:
http://www.hibnet.org/ivyde/updatesite/plugins/org.apache.ivy_2.0.0.20080313.jar
Support dynamic revisions with ftp in URLResolver
-
Key: IVY-738
URL: https://issues.apache.org/jira/browse/IVY-738
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-1
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: IVY-738.patch, ivy-settings-ivyde1_2.xml,
ivy-settings-ivyde1_3.xml, ivy.xml, ivy_console_log.txt, test_ant.txt,
test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla
[jira] Commented: (IVYDE-86) Classpath handling not works in IvyDE with eclipse 3.3
[ https://issues.apache.org/jira/browse/IVYDE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579441#action_12579441 ] Nicolas Lalevée commented on IVYDE-86: -- I tried to address this kind of issue with: IVYDE-68. Most of them are fixed. The fix are targetted against the current trunk, which use Ivy2. You can give a try of the unoffical patched trunk build from there : http://www.hibnet.org/ivyde/updatesite/ Classpath handling not works in IvyDE with eclipse 3.3 -- Key: IVYDE-86 URL: https://issues.apache.org/jira/browse/IVYDE-86 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.2.0 Environment: Eclipse 3.3 Reporter: Zsombor Gegesy When I try to add 'IvyDE Managed Library' in eclipse, after I've clicked on Ok, the following exception shows in the log file - and nothing else happens: java.lang.IllegalAccessError: tried to access method org.eclipse.jdt.internal.corext.buildpath.ClasspathModifier.init()V from class org.jayasoft.ivyde.eclipse.cpcontainer.core.AddClasspathContainer at org.jayasoft.ivyde.eclipse.cpcontainer.core.AddClasspathContainer.init(AddClasspathContainer.java:15) at org.jayasoft.ivyde.eclipse.cpcontainer.IvyClasspathUtil.clinit(IvyClasspathUtil.java:17) at org.jayasoft.ivyde.eclipse.ui.actions.CreateContainerAction.addCPContainer(CreateContainerAction.java:61) at org.jayasoft.ivyde.eclipse.ui.actions.CreateContainerAction.run(CreateContainerAction.java:55) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source) at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) And java.lang.NoClassDefFoundError: Could not initialize class org.jayasoft.ivyde.eclipse.cpcontainer.IvyClasspathUtil at org.jayasoft.ivyde.eclipse.ui.actions.CreateContainerAction.addCPContainer(CreateContainerAction.java:61) at org.jayasoft.ivyde.eclipse.ui.actions.CreateContainerAction.run(CreateContainerAction.java:55) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source
[jira] Commented: (IVY-738) Support dynamic revisions with ftp in URLResolver
[
https://issues.apache.org/jira/browse/IVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579445#action_12579445
]
Nicolas Lalevée commented on IVY-738:
-
Ivy does log in debug in the Ivy Console, doesn't it ?
Support dynamic revisions with ftp in URLResolver
-
Key: IVY-738
URL: https://issues.apache.org/jira/browse/IVY-738
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-1
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: IVY-738.patch, ivy-settings-ivyde1_2.xml,
ivy-settings-ivyde1_3.xml, ivy.xml, ivy_console_log.txt, test_ant.txt,
test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
[jira] Commented: (IVY-738) Support dynamic revisions with ftp in URLResolver
[
https://issues.apache.org/jira/browse/IVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579490#action_12579490
]
Nicolas Lalevée commented on IVY-738:
-
yep, the message is confusing, Ivy log this no matter what log level is
filtered.
So you should have every information in the Ivy console. You could attach the
logs so we could try to find the origin of the failure.
Support dynamic revisions with ftp in URLResolver
-
Key: IVY-738
URL: https://issues.apache.org/jira/browse/IVY-738
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-1
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: IVY-738.patch, ivy-settings-ivyde1_2.xml,
ivy-settings-ivyde1_3.xml, ivy.xml, ivy_console_log.txt, test_ant.txt,
test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla
[jira] Commented: (IVYDE-87) Problem with vfs ftp and dynamic revisions
[
https://issues.apache.org/jira/browse/IVYDE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580465#action_12580465
]
Nicolas Lalevée commented on IVYDE-87:
--
About the Bundle-Version, I didn't mean to change it in the patch. I forgot to
revert it before creating the patch. I just change it locally so I can generate
an update site easily.
And about the patch, I am confused by the OSGI spec:
{quote}
If the class or resource is in a package that is imported using Import-
Package or was imported dynamically in a previous load, then the
request is delegated to the exporting bundle's class loader.
{quote}
The failure initially comes from Ivy code, calling commons-vfs code loading
some common-vfs class.
AFAIU these common-vfs classes
(org.apache.commons.vfs.impl.StandardFileSystemManager for instance),
Package-Imported from Ivy, should be loaded by the bundle common-vfs.
The code loading the classes of common-vfs is something like:
getClass().getClassLoader().loadClass(className);
So the class loader returned by the above code should be the common-vfs one,
not the Ivy one.
So the import package I introduced should not be needed:
org.apache.commons.vfs.provider.local,
org.apache.commons.vfs.provider.sftp,
org.apache.commons.vfs.provider.url
I should have missed something there.
And Guillaume, I am not sure you put your ivy console ouput in your comment
(the one at 14/Mar/08 07:14 AM). Could you retry cleaning the console, do a
resolve and copy paste every thing you have in there ?
Note also that the container that disapear is mainly a UI bug. You should be
able to do a resolve by doing a work around: edit your ivy library in the build
path editor and click Finish.
Problem with vfs ftp and dynamic revisions
--
Key: IVYDE-87
URL: https://issues.apache.org/jira/browse/IVYDE-87
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo
[jira] Assigned: (IVYDE-70) The project ivy configuration is not taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée reassigned IVYDE-70: Assignee: Nicolas Lalevée The project ivy configuration is not taken into account on the first run Key: IVYDE-70 URL: https://issues.apache.org/jira/browse/IVYDE-70 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: Eclipse 3.2 Reporter: Nicolas Lalevée Assignee: Nicolas Lalevée Attachments: IVYDE-70-preferenceListenerTry.patch, IVYDE-70-urlish-r629733.patch, IVYDE-70-urlish-r629775.patch, IVYDE-70-urlish-r633421.patch, IVYDE-70-urlish.patch, IVYDE-70.patch Starting with an empty workspace, I import a project which already have its Ivy preferences configured. After the import the classpath is made of some ibiblio jars, whereas I was expecting the ones from my internal repository. After a resolve, the classpath has the proper jars, from my internal repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVYDE-81) An error occur when closing a project while the ivy editor is open
[
https://issues.apache.org/jira/browse/IVYDE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée reassigned IVYDE-81:
Assignee: Nicolas Lalevée
An error occur when closing a project while the ivy editor is open
--
Key: IVYDE-81
URL: https://issues.apache.org/jira/browse/IVYDE-81
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2, 3.3, 3.4M5
Reporter: Nicolas Lalevée
Assignee: Nicolas Lalevée
Fix For: 1.3.0
Attachments: IVYDE-81-r633150.patch
The project have to hold a ivy.xml, this file being edited by the Ivy editor.
Then close the project. On close the editor should also be closed, but it
fails.
Here is the stack trace from the error log view.
{noformat}
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.ClassCastException:
org.apache.ivyde.eclipse.ui.core.IvyFileEditorInput cannot be cast to
org.eclipse.ui.part.FileEditorInput)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
Caused by: java.lang.ClassCastException:
org.apache.ivyde.eclipse.ui.core.IvyFileEditorInput cannot be cast to
org.eclipse.ui.part.FileEditorInput
at
org.apache.ivyde.eclipse.ui.editors.IvyEditor$1.run(IvyEditor.java:198)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
... 23 more
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-58) Compilation fails on Europa due to API change
[
https://issues.apache.org/jira/browse/IVYDE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-58.
--
Resolution: Fixed
Fix Version/s: 1.3.0
Assignee: Xavier Hanin
Xavier fixed it by removing the class FixedJavaSearchPage: r633797
Compilation fails on Europa due to API change
-
Key: IVYDE-58
URL: https://issues.apache.org/jira/browse/IVYDE-58
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Stephane Bailliez
Assignee: Xavier Hanin
Fix For: 1.3.0
I was being stupid and checked out Europa, so after downloading several GB of
data, I tried to compile IvyDE and the Eclipse API seems to have changed.
Patch to make it compile is below. (there might be something more obvious
though, I'm not overly familiar with the api)
Index:
D:/work/oss/apache-ivy/ivyde/trunk/src/java/org/apache/ivyde/eclipse/ui/search/FixedJavaSearchPage.java
===
---
D:/work/oss/apache-ivy/ivyde/trunk/src/java/org/apache/ivyde/eclipse/ui/search/FixedJavaSearchPage.java
(revision 557007)
+++
D:/work/oss/apache-ivy/ivyde/trunk/src/java/org/apache/ivyde/eclipse/ui/search/FixedJavaSearchPage.java
(working copy)
@@ -289,7 +289,7 @@
case ISearchPageContainer.SELECTED_PROJECTS_SCOPE: {
String[] projectNames=
getContainer().getSelectedProjectNames();
scope=
factory.createJavaProjectSearchScope(projectNames, includeJRE);
- scopeDescription=
factory.getProjectScopeDescription(projectNames, includeJRE);
+ scopeDescription=
factory.getProjectScopeDescription(projectNames, includeJRE ?
JavaSearchScopeFactory.JRE : JavaSearchScopeFactory.NO_JRE);
break;
}
case ISearchPageContainer.WORKING_SET_SCOPE: {
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-47) IvyDE needs a manual Resolve after Eclipse Startup to work
[ https://issues.apache.org/jira/browse/IVYDE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-47. -- Resolution: Duplicate Assignee: Nicolas Lalevée I fixed the startup issue in IVYDE-70 IvyDE needs a manual Resolve after Eclipse Startup to work -- Key: IVYDE-47 URL: https://issues.apache.org/jira/browse/IVYDE-47 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.2.0 Environment: I am working under Linux and MacOSX Reporter: Andreas Sahlbach Assignee: Nicolas Lalevée I have several IvyDE classpath containers in different projects in my eclipse workspace. After starting up the IDE, I get several errors reported, because the IvyDE Classpath Container couldn't resolve the dependencies. Sometimes some dependencies magically appear outside of the classpath container. When I iterate through my projects and calling a manual Resolve on the different Classpath Containers, the resolve works and after the automatic project rebuild, all errors vanish. Smells like a startup race condition or something. Nevertheless it's annoying, because of my large workspace and the several ivy based builds that I have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-29) exception with ivy editor
[ https://issues.apache.org/jira/browse/IVYDE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-29. -- Resolution: Duplicate Assignee: (was: Xavier Hanin) I should have seen this issue before opening IVYDE-81. As I committed a fix that refers to IVYDE-81, I make this bug duplicate of IVYDE-81. exception with ivy editor - Key: IVYDE-29 URL: https://issues.apache.org/jira/browse/IVYDE-29 Project: IvyDE Issue Type: Bug Reporter: Xavier Hanin Priority: Minor I didn't see any consequence of this exception, but the error log show the following exception: org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: org.jayasoft.ivyde.eclipse.ui.core.IvyFileEditorInput) at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) Caused by: java.lang.ClassCastException: org.jayasoft.ivyde.eclipse.ui.core.IvyFileEditorInput at org.jayasoft.ivyde.eclipse.ui.editors.IvyEditor$1.run(IvyEditor.java:169) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) ... 20 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-39) No debug info in console.
[ https://issues.apache.org/jira/browse/IVYDE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-39. -- Resolution: Fixed There were no complain since a while, so I assume it is fixed. No debug info in console. - Key: IVYDE-39 URL: https://issues.apache.org/jira/browse/IVYDE-39 Project: IvyDE Issue Type: Bug Affects Versions: 1.1.0 Environment: Eclipse 3.2 WinXP Java 5 Reporter: easyproglife Assignee: Xavier Hanin Priority: Minor Fix For: 1.3.0 Attachments: IVYDE-39-r595956.patch, IVYDE-39.patch I can't find the debug information in the IvyConsole. I need it to investigate why Ivy doesn't find my stuff on my local repo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-33) error not displayed on IvyConsole
[ https://issues.apache.org/jira/browse/IVYDE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-33. -- Resolution: Duplicate It should been fixed within IVYDE-39 error not displayed on IvyConsole - Key: IVYDE-33 URL: https://issues.apache.org/jira/browse/IVYDE-33 Project: IvyDE Issue Type: Bug Components: classpath container Reporter: Maarten Coene Assignee: Xavier Hanin Hi, I received an error while resolving my dependencies. I got an dialog window saying: An internal error occured while resolving dependencies of C:\working\vhs\scontra_vhscontract\ant\ivy.xml Please see eclipse error log and IvyConsole for details However, when I looked at the IvyConsole, there was no error message or other details about the error. When I looked at the eclipse error log, there was this exception: fr.jayasoft.ivy.conflict.StrictConflictException: [ OTHER | jconnect | 2.0A ] (needed by [ LCMB | salloca | 2.0.0M4 ]) conflicts with [ OTHER | jconnect | 2.0A20 ] (needed by [ LCMT | openutm | 3.3.0 ]) at fr.jayasoft.ivy.conflict.StrictConflictManager.resolveConflicts(StrictConflictManager.java:34) at be.cm.ivy.LcmConflictManager.resolveConflicts(LcmConflictManager.java:102) at fr.jayasoft.ivy.Ivy.resolveConflict(Ivy.java:1537) at fr.jayasoft.ivy.Ivy.resolveConflict(Ivy.java:1567) at fr.jayasoft.ivy.Ivy.resolveConflict(Ivy.java:1567) at fr.jayasoft.ivy.Ivy.resolveConflict(Ivy.java:1519) at fr.jayasoft.ivy.Ivy.fetchDependencies(Ivy.java:1404) at fr.jayasoft.ivy.Ivy.doFetchDependencies(Ivy.java:1481) at fr.jayasoft.ivy.Ivy.fetchDependencies(Ivy.java:1413) at fr.jayasoft.ivy.Ivy.doFetchDependencies(Ivy.java:1465) at fr.jayasoft.ivy.Ivy.fetchDependencies(Ivy.java:1413) at fr.jayasoft.ivy.Ivy.doFetchDependencies(Ivy.java:1481) at fr.jayasoft.ivy.Ivy.fetchDependencies(Ivy.java:1413) at fr.jayasoft.ivy.Ivy.doFetchDependencies(Ivy.java:1481) at fr.jayasoft.ivy.Ivy.fetchDependencies(Ivy.java:1413) at fr.jayasoft.ivy.Ivy.getDependencies(Ivy.java:1332) at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1125) at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1082) at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1060) at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1057) at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1014) at fr.jayasoft.ivy.Ivy.resolve(Ivy.java:1011) at org.jayasoft.ivyde.eclipse.cpcontainer.IvyClasspathContainer$2.run(IvyClasspathContainer.java:187) regards, Maarten -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-87) Problem with vfs ftp and dynamic revisions
[
https://issues.apache.org/jira/browse/IVYDE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582234#action_12582234
]
Nicolas Lalevée commented on IVYDE-87:
--
I think you are facing IVYDE-34, as sometimes I did too.
Problem with vfs ftp and dynamic revisions
--
Key: IVYDE-87
URL: https://issues.apache.org/jira/browse/IVYDE-87
Project: IvyDE
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000766) 2/18/2008 15:05
[jira] Moved: (IVY-785) Problem with vfs ftp and dynamic revisions
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée moved IVYDE-87 to IVY-785:
--
Affects Version/s: (was: 1.3.0)
2.0.0-beta-2
Key: IVY-785 (was: IVYDE-87)
Project: Ivy (was: IvyDE)
Problem with vfs ftp and dynamic revisions
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM
[jira] Commented: (IVY-785) Problem with vfs ftp and dynamic revisions
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582236#action_12582236
]
Nicolas Lalevée commented on IVY-785:
-
I moved back the issue in Ivy as it is an OSGI packaging issue of Ivy.
Problem with vfs ftp and dynamic revisions
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000766) 2/18/2008
[jira] Commented: (IVYDE-32) IvyDE 1.0.3 Run configuration problem with Eclipse 3.x
[
https://issues.apache.org/jira/browse/IVYDE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582276#action_12582276
]
Nicolas Lalevée commented on IVYDE-32:
--
I tested with Eclipse 3.3 and I got the non working buttons.
I fact there is an NPE. Here is the stack trace from the error log:
{noformat}
java.lang.NullPointerException
at
org.apache.ivyde.eclipse.cpcontainer.IvydeContainerPage$3.widgetSelected(IvydeContainerPage.java:256)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.jdt.internal.ui.wizards.buildpaths.ClasspathContainerWizard.openWizard(ClasspathContainerWizard.java:226)
at
org.eclipse.jdt.ui.wizards.BuildPathDialogAccess.chooseContainerEntries(BuildPathDialogAccess.java:272)
at
org.eclipse.jdt.internal.debug.ui.actions.AddLibraryAction.run(AddLibraryAction.java:39)
at
org.eclipse.jdt.internal.debug.ui.launcher.RuntimeClasspathAdvancedDialog.okPressed(RuntimeClasspathAdvancedDialog.java:156)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:464)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.jdt.internal.debug.ui.actions.AddAdvancedAction.run(AddAdvancedAction.java:39)
at
org.eclipse.jdt.internal.debug.ui.actions.RuntimeClasspathAction$1.widgetSelected(RuntimeClasspathAction.java:137)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1133)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:387)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at
org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:391)
at
org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:333)
at
org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:82)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176
[jira] Updated: (IVYDE-65) IvyDE has not yet been released within the Apache Software Foundation
[ https://issues.apache.org/jira/browse/IVYDE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-65: - Fix Version/s: 1.3.0 IvyDE has not yet been released within the Apache Software Foundation - Key: IVYDE-65 URL: https://issues.apache.org/jira/browse/IVYDE-65 Project: IvyDE Issue Type: New Feature Components: ivy editor Environment: ANY Reporter: spkatana Priority: Trivial Fix For: 1.3.0 Is IvyIDE is full compliance with the last version of Ant Apache Ivy 2.0 ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-32) IvyDE 1.0.3 Run configuration problem with Eclipse 3.x
[ https://issues.apache.org/jira/browse/IVYDE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-32: - Affects Version/s: 1.1.0 1.2.0 Fix Version/s: 1.3.0 Assignee: Nicolas Lalevée (was: Xavier Hanin) IvyDE 1.0.3 Run configuration problem with Eclipse 3.x Key: IVYDE-32 URL: https://issues.apache.org/jira/browse/IVYDE-32 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.1.0, 1.2.0 Environment: Windows XP, Eclipse 3.2.0, IvyDE 1.0.3 Reporter: Emmanuel Cordente Assignee: Nicolas Lalevée Fix For: 1.3.0 I'm having an UI problem using IvyDE with Eclipse 3.1 et 3.2. When I add the IvyDE Managed Dependencies in my Eclipse project everything work fine, I have the little windows the indicate where is my ivy.xml file and a list of configuration when I select my ivy file. But when a try to do the same thing inside the Run Configuration to configure a runtime dependencies, I can see the same little windows but the BROWSE button doesn't work and it's impossible to find the ivy.xml file. I Tryed to put the ivy.xml path explicitely but I can't see the configuration list below the browse button. The solution I found for now is to open the .launch file and to choose my configuration directly inside but it's a bit tricky to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[ https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582278#action_12582278 ] Nicolas Lalevée commented on IVYDE-88: -- I know that to build an Eclipse plugin from ant, we can use Eclipse ant tasks. But it needs a complete Eclipse install somewhere. Will it be possible to have installed an Eclipse on the gump machine ? Add new target to build.xml to build the plugin with Ant Key: IVYDE-88 URL: https://issues.apache.org/jira/browse/IVYDE-88 Project: IvyDE Issue Type: Improvement Reporter: Maarten Coene In order to add IvyDE to gump, we need an Ant target to create the plugin. In addition, this target could be very usefull for people wanting to build the plugin theirself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-61) Eclipse hangs on startup
[ https://issues.apache.org/jira/browse/IVYDE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-61. -- Resolution: Duplicate The startup freeze has been fixed there: IVYDE-63 You could try an unofficial trunk build : http://www.hibnet.org/ivyde/updatesite/ Eclipse hangs on startup Key: IVYDE-61 URL: https://issues.apache.org/jira/browse/IVYDE-61 Project: IvyDE Issue Type: Bug Affects Versions: 1.2.0 Environment: Sun Java 1.6.0-b105, Eclipse 3.3, Ubuntu 7.04 32 bit, AMD Sempron 2800+ Reporter: Nigel Charman Attachments: .options, build.out, debug.sh I've been using IvyDE on my project for around a month, and have had no problems with it up till now. Eclipse hangs at startup on the splash screen with the progress bar about 2/3 full. This only occurs with one of my workspaces; Eclipse starts OK with the other workspaces. After removing the IvyDE plugin and features folder Eclipse starts OK. Reinstate the IvyDE plugin and features folders and Eclipse hangs. The following actions had no effect and Eclipse still hung on startup: - rebooting - leaving Eclipse for an hour to start up - invoking Ivy retrieve from the ant script of the affected project - deleting the Ivy cache The eventual workaround was to delete the ivy.xml. After this Eclipse started OK. I then reinstated the ivy.xml file and everything now works OK, including restarting Eclipse. At the time of error the Eclipse .log file contains: !SESSION 2007-08-01 22:54:12.565 --- eclipse.buildId=I20070625-1500 java.version=1.6.0 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_NZ Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-08-01 22:54:25.592 !MESSAGE starting IvyDE plugin !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-08-01 22:54:25.626 !MESSAGE IvyDE plugin started !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-08-01 22:54:26.471 !MESSAGE resolved dependencies of /home/nigel/jibx/jibxws/build/ivy.xml = On successful startup the Eclipse .log file shows: --- eclipse.buildId=I20070625-1500 java.version=1.6.0 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_NZ Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-07-29 20:19:47.736 !MESSAGE starting IvyDE plugin !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-07-29 20:19:47.887 !MESSAGE IvyDE plugin started !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-07-29 20:19:59.523 !MESSAGE resolved dependencies of /home/nigel/jibx/jibxws/build/ivy.xml !ENTRY org.jayasoft.ivyde.eclipse 1 0 2007-07-29 20:20:01.112 !MESSAGE resolved dependencies of /home/nigel/jibx/jibxws/build/ivy.xml = Note the resolved dependencies message is duplicated here on successful startup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-43) [PATCH] New resolver allows project linking within the workspace
[ https://issues.apache.org/jira/browse/IVYDE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-43: - Attachment: IVYDE-43-r641334.patch In order to not loose Eugene code, here is an updated version of the patch. I didn't tested thought. But I fear some classpath issues in the suggested solution since Ivy and IvyDE are two seperated bundles. Ivy would instanciate the WorkspaceResolver whereas it actually is in IvyDE. [PATCH] New resolver allows project linking within the workspace Key: IVYDE-43 URL: https://issues.apache.org/jira/browse/IVYDE-43 Project: IvyDE Issue Type: New Feature Components: classpath container Reporter: Eugene Goldfarb Assignee: Xavier Hanin Attachments: IVYDE-43-r641334.patch, ivyde-43.patch, ivyde-example-censored.JPG, ivyde-example-censored.JPG I've been dreaming and tinkering with this idea for a while, and it finally evolved into these changes. This introduces a new plugin - called WorkspaceResolver. DISCLAIMER: These changes should NOT change how IVYDE works unless the new resolver is set up in the Ivy configuration file. Therefore, it should be safe to use with any existing Ivy configuration. The only potential issue would occur if you are using artifacts of type project, since I'm treating those differently. When used with my custom IvyClasspathContainer changes, the WorkspaceResolver will link dependent projects when they are open in the same workspace, allowing full-fledged linked project functionality Eclipse provides, such as incremental compilation, debugging, mouseover javadoc pop-ups, and source browsing across projects. The resolver will not work until it is properly configured, see instructions below. I attached the patch against IvyDE 1.2 rev. 605. It also includes the minor console logging changes I submitted with IVYDE-39. Please let me know what you think and if there are any major issues or suggestions. How it works: During a resolve, if the WorkspaceResolver is in the resolve chain (see below how to set it up), it looks at all open projects in the workspace that have Ivy containers. The first project that publishes the module on which the project being resolved depends, will be picked and returned as a special type of artifact called project. The IvyClasspathContainer will recognize the artifact as a project and put the eclipse project as a dependent project within the classpath container of the parent. I will attach the screenshot to show this. If you do not want a project to be linked as a dependency, close it or delete from the workspace. As soon as you do that, any projects that were linked to it will automatically re-resolve (using WorkspaceResourceChangeListener) (if that preference is enabled) and use the standard Ivy means of finding the dependency. I am also planning to have the WorkspaceResourceChangeListener auto-resolve when a new project is added or opened, so opening a project will automatically link it into the currently open projects where necessary. This has been problematic, since I cannot seem to catch the right event when a project is open. Some limitations and potential issues: 1) Since the resolver is not aware which module revision an eclipse project is publishing (we never put the version inside the info tag of a project's ivy.xml), it optimistically matches any revision of the module. 2) Since the resolver stops after finding the first open project which matches the module, having multiple open versions of the same project in the workspace (for example, different branches) may set the wrong version as a dependency. You are advised to only open the version of the project which you want other projects in the workspace to depend on. 3) NOTE: Transitive dependencies are not passed from the dependent project to the parent when projects are linked. If you find you are missing some transitive dependencies, just set your dependent eclipse project to export its ivy dependencies. (Project-Properties-Java Build Path-Order and Export- check the ivy container) This will only export the configuration(s) that project is using and not what a dependent project may ask for when it's being resolved. To do that, this resolver will need to be modified to pass transitive dependencies along. How to set it up Set up a custom resolver in the resolve chain (see example below), Usage Example: Suppose you have a main ivyconf.xml which sets up all your resolvers to be executed at command-line. 1) Create a new file which includes your main ivyconf.xml file 2) Define the custom eclipse resolver type. 3) Create a simple chain
[jira] Commented: (IVY-785) Problem with vfs ftp and dynamic revisions
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582321#action_12582321
]
Nicolas Lalevée commented on IVY-785:
-
Yep, every required bundle is on Orbit, except common-vfs. See the URLs I
posted ;)
There is also the OSGI repository :
http://www.osgi.org/Repository/HomePage?cmd=browsekeywords=commonssubmit=search
Problem with vfs ftp and dynamic revisions
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http
[jira] Updated: (IVY-785) Classpath issues with vfs ftp while being used as a bundle
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVY-785:
Summary: Classpath issues with vfs ftp while being used as a bundle (was:
Problem with vfs ftp and dynamic revisions)
Classpath issues with vfs ftp while being used as a bundle
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
[jira] Commented: (IVY-785) Classpath issues with vfs ftp while being used as a bundle
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583603#action_12583603
]
Nicolas Lalevée commented on IVY-785:
-
I don't understand your last comment. Do you actually have issues ?
Classpath issues with vfs ftp while being used as a bundle
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo
[jira] Assigned: (IVY-785) Classpath issues with vfs ftp while being used as a bundle
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée reassigned IVY-785:
---
Assignee: Nicolas Lalevée
Classpath issues with vfs ftp while being used as a bundle
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Assignee: Nicolas Lalevée
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000766) 2/18/2008 15:05:34 PM
[jira] Commented: (IVYDE-32) IvyDE 1.0.3 Run configuration problem with Eclipse 3.x
[ https://issues.apache.org/jira/browse/IVYDE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583660#action_12583660 ] Nicolas Lalevée commented on IVYDE-32: -- After looked closely, it seems that IvyDE wasn't designed to be used in a run context. The run context doesn't assume to be executed in a specific project, which IvyDE assumes. First I would say that it is not a bug but a missing feature. But the Eclipse API doesn't seperate the two concepts. Implementing the by project configuration also mean implementing the project independant one. So it is actually a bug. IvyDE 1.0.3 Run configuration problem with Eclipse 3.x Key: IVYDE-32 URL: https://issues.apache.org/jira/browse/IVYDE-32 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.1.0, 1.2.0 Environment: Windows XP, Eclipse 3.2.0, IvyDE 1.0.3 Reporter: Emmanuel Cordente Assignee: Nicolas Lalevée Fix For: 1.3.0 I'm having an UI problem using IvyDE with Eclipse 3.1 et 3.2. When I add the IvyDE Managed Dependencies in my Eclipse project everything work fine, I have the little windows the indicate where is my ivy.xml file and a list of configuration when I select my ivy file. But when a try to do the same thing inside the Run Configuration to configure a runtime dependencies, I can see the same little windows but the BROWSE button doesn't work and it's impossible to find the ivy.xml file. I Tryed to put the ivy.xml path explicitely but I can't see the configuration list below the browse button. The solution I found for now is to open the .launch file and to choose my configuration directly inside but it's a bit tricky to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-75) Possible endless loop while computing the classpath entries
[
https://issues.apache.org/jira/browse/IVYDE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-75.
--
Resolution: Cannot Reproduce
Not sure it has been fix even if it was really a bug, but I wasn't able to
reproduce it with the trunk version.
Possible endless loop while computing the classpath entries
---
Key: IVYDE-75
URL: https://issues.apache.org/jira/browse/IVYDE-75
Project: IvyDE
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Eclipse 3.2
Reporter: Nicolas Lalevée
Priority: Minor
While trying to debug IVYDE-70, having a break point make the resolving
process loop indefinitely. I cannot say if there is really a bug or not,
because running while having break points is not the standard way the thread
runs. But it shows there is a possibility that the resolve process may run
sevral times, which should not happend.
And after I remove the breakpoint, there is no StackOverflowError, so I
assume this bug might not appear in normal cases.
Here is the stack trace copied from Eclipse :
{noformat}
IvyClasspathContainer.computeClasspathEntries(boolean, boolean, boolean)
line: 617
IvyClasspathContainer.refresh(boolean) line: 644
IvyClasspathInitializer.initialize(IPath, IJavaProject) line: 61
JavaModelManager.initializeContainer(IJavaProject, IPath) line: 1924
JavaModelManager.getClasspathContainer(IPath, IJavaProject) line: 1267
JavaCore.getClasspathContainer(IPath, IJavaProject) line: 1470
JavaProject.getResolvedClasspath(IClasspathEntry[], IPath, boolean, boolean,
Map) line: 2169
JavaProject.getResolvedClasspath(boolean, boolean, boolean) line: 2073
JavaCore.setClasspathContainer(IPath, IJavaProject[], IClasspathContainer[],
IProgressMonitor) line: 4189
IvyClasspathContainer.notifyUpdateClasspathEntries() line: 682
IvyClasspathContainer.access$7(IvyClasspathContainer) line: 678
IvyClasspathContainer$4.run() line: 672
RunnableLock.run() line: 35
UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 123
Display.runAsyncMessages(boolean) line: 3157
Display.readAndDispatch() line: 2859
EventLoopProgressMonitor.runEventLoop() line: 123
EventLoopProgressMonitor.isCanceled() line: 97
ThreadJob.isCanceled(IProgressMonitor) line: 126
ThreadJob.joinRun(IProgressMonitor) line: 161
ImplicitJobs.begin(ISchedulingRule, IProgressMonitor, boolean) line: 87
JobManager.beginRule(ISchedulingRule, IProgressMonitor) line: 219
WorkManager.checkIn(ISchedulingRule, IProgressMonitor) line: 96
Workspace.prepareOperation(ISchedulingRule, IProgressMonitor) line: 1684
Project.touch(IProgressMonitor) line: 1035
SetClasspathOperation.executeOperation() line: 288
SetClasspathOperation(JavaModelOperation).run(IProgressMonitor) line: 720
Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor)
line: 1737
SetClasspathOperation(JavaModelOperation).runOperation(IProgressMonitor)
line: 784
JavaProject.setRawClasspath(IClasspathEntry[], IPath, IProgressMonitor,
boolean, IClasspathEntry[], boolean, boolean) line: 3016
JavaCore$5.run(IProgressMonitor) line: 4215
BatchOperation.executeOperation() line: 39
BatchOperation(JavaModelOperation).run(IProgressMonitor) line: 720
Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor)
line: 1737
JavaCore.run(IWorkspaceRunnable, ISchedulingRule, IProgressMonitor) line:
4024
JavaCore.setClasspathContainer(IPath, IJavaProject[], IClasspathContainer[],
IProgressMonitor) line: 4198
IvyClasspathContainer.notifyUpdateClasspathEntries() line: 682
IvyClasspathContainer.access$7(IvyClasspathContainer) line: 678
IvyClasspathContainer$4.run() line: 672
RunnableLock.run() line: 35
UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 123
Display.runAsyncMessages(boolean) line: 3157
Display.readAndDispatch() line: 2859
EventLoopProgressMonitor.runEventLoop() line: 123
EventLoopProgressMonitor.isCanceled() line: 97
ThreadJob.isCanceled(IProgressMonitor) line: 126
ThreadJob.joinRun(IProgressMonitor) line: 161
ImplicitJobs.begin(ISchedulingRule, IProgressMonitor, boolean) line: 87
JobManager.beginRule(ISchedulingRule, IProgressMonitor) line: 219
WorkManager.checkIn(ISchedulingRule, IProgressMonitor) line: 96
Workspace.prepareOperation(ISchedulingRule, IProgressMonitor) line: 1684
Project.touch(IProgressMonitor) line: 1035
SetClasspathOperation.executeOperation() line: 288
SetClasspathOperation(JavaModelOperation).run(IProgressMonitor) line: 720
Workspace.run
[jira] Resolved: (IVY-785) Classpath issues with vfs ftp while being used as a bundle
[
https://issues.apache.org/jira/browse/IVY-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVY-785.
-
Resolution: Fixed
Fix Version/s: 2.0-RC1
OK, so for me this issue is fixed.
But you are still facing with a bug in IvyDE: see IVYDE-34.
Classpath issues with vfs ftp while being used as a bundle
--
Key: IVY-785
URL: https://issues.apache.org/jira/browse/IVY-785
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Environment: Eclipse 3.2 and IvyDE 1.2
Eclipse 3.3 (MyEclipse 6.0.1) and IvyDE 1.3
(org.apache.ivyde.eclipse_1.3.0.2007120912.jar)
Reporter: Guillaume
Assignee: Nicolas Lalevée
Fix For: 2.0-RC1
Attachments: FileZilla Server.log, IVY-738.patch,
ivy-settings-ivyde1_2.xml, ivy-settings-ivyde1_3.xml, ivy.xml,
ivy_console_log.txt, ivy_console_log2.txt, IVYDE-87-r639596.patch,
test_ant.txt, test_ant_debug.txt, test_ivyde.txt
Configuration (attachments follow)
The repository structure is a simple filesystem (on the same machine than
Eclipse and Ant for the test) :
The folder ftpuser_home\external-lib\junit\junit exists and has two
subfolders named after version numbers :
3.8.1 which contains ivy-3.8.1.xml, jars and so on
3.8.2 which contains ivy-3.8.2.xml, jars and so on
User has proper rights to list directory contents which proves to be ok with
ant task.
Using Eclipse 3.3 and IvyDE 1.3 (snapshot build -
org.apache.ivyde.eclipse_1.3.0.2007120912.jar) :
JUnit 3.8.+ gets resolved to the latest 3.8.x version available on my
repository (3.8.2 in this test) with an ant resolve task. But it isn't
resolved at all with IvyDE.
In ant, the related logs are pretty simple (ant ivy settings are pointing to
the same ivy settings file than ivyde) :
[ivy:retrieve] found junit#junit;3.8.2 in ftp
[ivy:retrieve] [3.8.2] junit#junit;3.8.+
Ivy Console summary :
{code}
WARNINGS
module not found: junit#junit;3.8.+
ftp: tried
ftp://:[EMAIL PROTECTED]/external-lib/junit/junit/3.8.+/ivy-3.8.+.xml
ftp://:[EMAIL
PROTECTED]/external-lib/junit/junit/[revision]/ivy-[revision].xml
::
:: UNRESOLVED DEPENDENCIES ::
::
:: junit#junit;3.8.+: not found
::
{code}
FTP logs :
{code}
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http://sourceforge.net/projects/filezilla/
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) USER
repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 331 Password
required for repo-central
(000765) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) PASS
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 230 Logged on
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) TYPE I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 200 Type set to I
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD junit
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 250 CWD
successful. /external-lib/junit/junit is current directory.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD 3.8.+
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/3.8.+: directory not found.
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) CWD external-lib
(000765) 2/18/2008 15:05:34 PM - repo-central (127.0.0.1) 550 CWD failed.
/external-lib/junit/junit/external-lib: directory not found.
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) Connected,
sending welcome message...
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-FileZilla
Server version 0.9.24 beta
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220-written by
Tim Kosse ([EMAIL PROTECTED])
(000766) 2/18/2008 15:05:34 PM - (not logged in) (127.0.0.1) 220 Please
visit http
[jira] Updated: (IVY-325) declare source and javadoc artifacts in maven2 modules
[ https://issues.apache.org/jira/browse/IVY-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVY-325: Component/s: Maven Compatibility declare source and javadoc artifacts in maven2 modules -- Key: IVY-325 URL: https://issues.apache.org/jira/browse/IVY-325 Project: Ivy Issue Type: Improvement Components: Maven Compatibility Affects Versions: 1.4 Reporter: Xavier Hanin Maven2 modules created when Ivy parses poms do not declare any source or javadoc artifact, while they sometimes offer one on ibiblio. Declaring such artifact could ease the integration of maven2 modules with source and javadoc attachments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-82) Empty containers disappear with Eclipse 3.3
[ https://issues.apache.org/jira/browse/IVYDE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584088#action_12584088 ] Nicolas Lalevée commented on IVYDE-82: -- After looking deeply into Eclipse, it seems to be the normal behaviour. The same happens with the maven classpath container. Knowing that the only way to trigger the resolve is to configure the container, it is problematic when the container doesn't show up. So I think we should let the container disappear, but add an entry in the context menu on the project to allow the user to trigger a resolve. Empty containers disappear with Eclipse 3.3 --- Key: IVYDE-82 URL: https://issues.apache.org/jira/browse/IVYDE-82 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: with the IVYDE-70 patch Eclipse 3.3, Eclipse 3.4M4 Reporter: Nicolas Lalevée If the resolved dependencies are empty, due to an empty dependency tree or some dependencies errors, then the class path container disappears. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-34) internal error when doing resolve
[ https://issues.apache.org/jira/browse/IVYDE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée updated IVYDE-34: - Fix Version/s: 1.3.0 internal error when doing resolve - Key: IVYDE-34 URL: https://issues.apache.org/jira/browse/IVYDE-34 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.1.0 Reporter: Maarten Coene Assignee: Nicolas Lalevée Fix For: 1.3.0 I receive an error with Eclipse 3.2.0. When I do a resolve, I receive an internal error! (no popup-dialog from Ivy and no error on IvyConsole). The following appears in my Eclipse log: !ENTRY org.eclipse.core.jobs 4 2 2006-10-10 12:20: 34.202 !MESSAGE An internal error occurred during: Resolve salloca/ant/ivy.xml dependencies. !STACK 0 java.lang.NullPointerException at org.eclipse.core.internal.jobs.Worker.run(Worker.java:73) The above error occurs everytime I do a resolve. No further stacktrace is available :-( Also, if I use Eclipse 3.2.1 the resolves works without a problem... If I do a resolve in Ant of the same Ivy file (and same config file and same configurations), I don't get an error regards, Maarten -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVYDE-34) internal error when doing resolve
[ https://issues.apache.org/jira/browse/IVYDE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée reassigned IVYDE-34: Assignee: Nicolas Lalevée (was: Xavier Hanin) internal error when doing resolve - Key: IVYDE-34 URL: https://issues.apache.org/jira/browse/IVYDE-34 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.1.0 Reporter: Maarten Coene Assignee: Nicolas Lalevée I receive an error with Eclipse 3.2.0. When I do a resolve, I receive an internal error! (no popup-dialog from Ivy and no error on IvyConsole). The following appears in my Eclipse log: !ENTRY org.eclipse.core.jobs 4 2 2006-10-10 12:20: 34.202 !MESSAGE An internal error occurred during: Resolve salloca/ant/ivy.xml dependencies. !STACK 0 java.lang.NullPointerException at org.eclipse.core.internal.jobs.Worker.run(Worker.java:73) The above error occurs everytime I do a resolve. No further stacktrace is available :-( Also, if I use Eclipse 3.2.1 the resolves works without a problem... If I do a resolve in Ant of the same Ivy file (and same config file and same configurations), I don't get an error regards, Maarten -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-82) Empty containers disappear with Eclipse 3.3
[ https://issues.apache.org/jira/browse/IVYDE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584145#action_12584145 ] Nicolas Lalevée commented on IVYDE-82: -- I thought of that one, but it seems so dirty. And note also that the current context menu on the classpath container is in fact bind on every classpath container. For instance, if I have a maven classpath container and an ivy one, I can right-click on the maven container, choose Edit, and then I get the editor of the ivy.xml, which is quite confusing (well, we could consider it as a feature to do some Ivy envangelism ;)) So it might be a good idea to refactor the ivy context menus too. But I am not sure how. For the record, here is the Eclipse bugzilla entry about empty containers: https://bugs.eclipse.org/bugs/show_bug.cgi?id=167682 Empty containers disappear with Eclipse 3.3 --- Key: IVYDE-82 URL: https://issues.apache.org/jira/browse/IVYDE-82 Project: IvyDE Issue Type: Bug Affects Versions: 1.3.0 Environment: with the IVYDE-70 patch Eclipse 3.3, Eclipse 3.4M4 Reporter: Nicolas Lalevée If the resolved dependencies are empty, due to an empty dependency tree or some dependencies errors, then the class path container disappears. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file permissions when publishing artifacts
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584468#action_12584468 ] Tero Hagström commented on IVY-764: --- Ping? How is the Ivy ssh resolver supposed to work with regard to the file permissions set for the published files? ssh resolver sets very restrictive file permissions when publishing artifacts - Key: IVY-764 URL: https://issues.apache.org/jira/browse/IVY-764 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Tero Hagström When we use the ssh resolver to publish artifacts to a repository on our server, the access permissions of the created files only allow reading by the user that published the artifacts. As a result, no one else can get the artifacts from the repository, which completely defeats it's purpose. File permissions look like this: -rw--- 1 atu dev 875 Mar 10 12:34 core-20080310123411.jar -rw--- 1 atu dev 40 Mar 10 12:34 core-20080310123411.jar.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 core-20080310123411.jar.md5 -rw--- 1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml -rw--- 1 atu dev 40 Mar 10 12:34 ivy-20080310123411.xml.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 ivy-20080310123411.xml.md5 I could not find any way to configure or otherwise affect the file permissions. Is there a way? BTW, with Ivy 1.4.1 the permissions looked like this: -rw-rw-r-- 1 th dev 877 Mar 6 10:08 core-20080306100813.jar -rw-rw-r-- 1 th dev 40 Mar 6 10:08 core-20080306100813.jar.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 core-20080306100813.jar.md5 -rw-rw-r-- 1 th dev 166 Mar 6 10:08 ivy-20080306100813.xml -rw-rw-r-- 1 th dev 40 Mar 6 10:08 ivy-20080306100813.xml.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 ivy-20080306100813.xml.md5 We will now fall back to using Ivy version 1.4.1, for the time being. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[
https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-88:
-
Attachment: build.patch
Here is a patch that does the build of IvyDE.
The build depends on a eclipse install. In the eclipse plugins directory have
to be installed the ivy bundle.
Then to launch the build:
{noformat}
ant -DbaseLocation=.../eclipse
{noformat}
Note also that this patch should be apply on the directory ivyde and not the
ivyde/trunk. The build system expect the plugin to be alone in its directory.
After being patched, here is the layout:
{noformat}
ivyde/
build.xml
builder/
org.apache.ivyde.feature/
tunk/
{noformat}
So if there is no objection against this build system, the layout to be
committed should be:
{noformat}
ivyde/
tunk/
build.xml
builder/
org.apache.ivyde.feature/
org.apache.ivyde.eclipse/ (source which were in trunk)
{noformat}
Add new target to build.xml to build the plugin with Ant
Key: IVYDE-88
URL: https://issues.apache.org/jira/browse/IVYDE-88
Project: IvyDE
Issue Type: Improvement
Reporter: Maarten Coene
Attachments: build.patch
In order to add IvyDE to gump, we need an Ant target to create the plugin.
In addition, this target could be very usefull for people wanting to build
the plugin theirself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[ https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589524#action_12589524 ] Nicolas Lalevée commented on IVYDE-88: -- ok, thanks for reviewing, let's discuss about IvyDE version number. Add new target to build.xml to build the plugin with Ant Key: IVYDE-88 URL: https://issues.apache.org/jira/browse/IVYDE-88 Project: IvyDE Issue Type: Improvement Reporter: Maarten Coene Attachments: build.patch In order to add IvyDE to gump, we need an Ant target to create the plugin. In addition, this target could be very usefull for people wanting to build the plugin theirself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[ https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée reassigned IVYDE-88: Assignee: Nicolas Lalevée Add new target to build.xml to build the plugin with Ant Key: IVYDE-88 URL: https://issues.apache.org/jira/browse/IVYDE-88 Project: IvyDE Issue Type: Improvement Reporter: Maarten Coene Assignee: Nicolas Lalevée Fix For: 1.3.0 Attachments: build.patch In order to add IvyDE to gump, we need an Ant target to create the plugin. In addition, this target could be very usefull for people wanting to build the plugin theirself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[ https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-88. -- Resolution: Fixed Fix Version/s: 1.3.0 Add new target to build.xml to build the plugin with Ant Key: IVYDE-88 URL: https://issues.apache.org/jira/browse/IVYDE-88 Project: IvyDE Issue Type: Improvement Reporter: Maarten Coene Assignee: Nicolas Lalevée Fix For: 1.3.0 Attachments: build.patch In order to add IvyDE to gump, we need an Ant target to create the plugin. In addition, this target could be very usefull for people wanting to build the plugin theirself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[ https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590046#action_12590046 ] Nicolas Lalevée commented on IVYDE-88: -- Layout changed and build committed. I will make a mail on the dev list to introduce it. Add new target to build.xml to build the plugin with Ant Key: IVYDE-88 URL: https://issues.apache.org/jira/browse/IVYDE-88 Project: IvyDE Issue Type: Improvement Reporter: Maarten Coene Assignee: Nicolas Lalevée Fix For: 1.3.0 Attachments: build.patch In order to add IvyDE to gump, we need an Ant target to create the plugin. In addition, this target could be very usefull for people wanting to build the plugin theirself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-88) Add new target to build.xml to build the plugin with Ant
[ https://issues.apache.org/jira/browse/IVYDE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590342#action_12590342 ] Nicolas Lalevée commented on IVYDE-88: -- The generated path where incorrects for Windows. I have fixed it in the trunk. I have then tested it with Eclipse 3.4M5 under Linux: it works fine. I aslo tested with Windows and Eclipse 3.2 thanks to a colleague, the build now launch correctly. But he only has IvyDE 1.2 in its plugins (blame on him ! :p), so I don't really know it is really successul (due to the requirment to have Ivy 2 bundle in the plugins). Could you confirm that it is working for your configuration ? Add new target to build.xml to build the plugin with Ant Key: IVYDE-88 URL: https://issues.apache.org/jira/browse/IVYDE-88 Project: IvyDE Issue Type: Improvement Reporter: Maarten Coene Assignee: Nicolas Lalevée Fix For: 1.3.0 Attachments: build.patch In order to add IvyDE to gump, we need an Ant target to create the plugin. In addition, this target could be very usefull for people wanting to build the plugin theirself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVY-802) The Bundle-Version is 0.0.0 is the build artifacts
The Bundle-Version is 0.0.0 is the build artifacts -- Key: IVY-802 URL: https://issues.apache.org/jira/browse/IVY-802 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Nicolas Lalevée Assignee: Nicolas Lalevée Priority: Minor Fix For: 2.0-RC1 The regexep introduced in IVY-687 is not matching any line, so the Bundle-Version is not replaced. Unfortunately the beta-2 release contains the 0.0.0 version number, so it cannot be included in an OSGi environment without modifying it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-802) The Bundle-Version is 0.0.0 is the build artifacts
[ https://issues.apache.org/jira/browse/IVY-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVY-802. - Resolution: Fixed fixed by using replaceregexp filter which is simpler and is still compatible with Ant 1.6 The Bundle-Version is 0.0.0 is the build artifacts -- Key: IVY-802 URL: https://issues.apache.org/jira/browse/IVY-802 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: Nicolas Lalevée Assignee: Nicolas Lalevée Priority: Minor Fix For: 2.0-RC1 The regexep introduced in IVY-687 is not matching any line, so the Bundle-Version is not replaced. Unfortunately the beta-2 release contains the 0.0.0 version number, so it cannot be included in an OSGi environment without modifying it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (IVY-764) make it possible to specify permissions of published files for the SSH resolver
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tero Hagström reopened IVY-764: --- Not quite there yet, I still cannot publish artifacts so that they would be readable by other users. I would have expected the publishPermissions attribute to work the same way as umask, but it seems to be the negative. Alone, this would be acceptable, if properly documented, but if I set the publishPermissions attribute to a value that produces the file permissions that I want, the publishing of the ivy files, sha1 and md5 files fails! Case 1: Used value for publishPermissions: 0222 resulting file permissions: --w--- 1 th dev 1263 Apr 24 15:07 upon-20080424150713.jar expected permissions: -r--r--r-- Case 2: Used value for publishPermissions: 0022 resulting file permissions: -- 1 th dev 1263 Apr 24 14:59 upon-20080424145932.jar Only jar file published, sha1, md5, and xml files not: /g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts for com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException: /tmp/ivytemp49772sha1 (Permission denied) expected permissions: -rw-r--r-- all files should have been published Case 3: Used value for publishPermissions: 0666 resulting file permissions: -rw-r--r-- 1 th dev 1263 Apr 24 15:16 upon-20080424151611.jar Only jar file published, sha1, md5, and xml files not: /g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts for com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException: /tmp/ivytemp17387sha1 (Permission denied) expected permissions: -- all files should have been published make it possible to specify permissions of published files for the SSH resolver --- Key: IVY-764 URL: https://issues.apache.org/jira/browse/IVY-764 Project: Ivy Issue Type: Improvement Affects Versions: 2.0.0-beta-2 Reporter: Tero Hagström Assignee: Maarten Coene Fix For: 2.0-RC1 When we use the ssh resolver to publish artifacts to a repository on our server, the access permissions of the created files only allow reading by the user that published the artifacts. As a result, no one else can get the artifacts from the repository, which completely defeats it's purpose. File permissions look like this: -rw--- 1 atu dev 875 Mar 10 12:34 core-20080310123411.jar -rw--- 1 atu dev 40 Mar 10 12:34 core-20080310123411.jar.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 core-20080310123411.jar.md5 -rw--- 1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml -rw--- 1 atu dev 40 Mar 10 12:34 ivy-20080310123411.xml.sha1 -rw--- 1 atu dev 32 Mar 10 12:34 ivy-20080310123411.xml.md5 I could not find any way to configure or otherwise affect the file permissions. Is there a way? BTW, with Ivy 1.4.1 the permissions looked like this: -rw-rw-r-- 1 th dev 877 Mar 6 10:08 core-20080306100813.jar -rw-rw-r-- 1 th dev 40 Mar 6 10:08 core-20080306100813.jar.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 core-20080306100813.jar.md5 -rw-rw-r-- 1 th dev 166 Mar 6 10:08 ivy-20080306100813.xml -rw-rw-r-- 1 th dev 40 Mar 6 10:08 ivy-20080306100813.xml.sha1 -rw-rw-r-- 1 th dev 32 Mar 6 10:08 ivy-20080306100813.xml.md5 We will now fall back to using Ivy version 1.4.1, for the time being. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (IVY-764) make it possible to specify permissions of published files for the SSH resolver
[
https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12592023#action_12592023
]
hagis edited comment on IVY-764 at 4/24/08 5:31 AM:
Not quite there yet, I still cannot publish artifacts so that they would be
readable by other users.
I would have expected the publishPermissions attribute to work the same way as
umask, but it seems to be the negative. Alone, this would be acceptable, if
properly documented, but if I set the publishPermissions attribute to a value
that produces the file permissions that I want, the publishing of the ivy
files, sha1 and md5 files fails!
Case 1:
Used value for publishPermissions: 0222
resulting file permissions:
{code}--w--- 1 th dev 1263 Apr 24 15:07 upon-20080424150713.jar{code}
expected permissions:
{code}-r--r--r--{code}
Case 2:
Used value for publishPermissions: 0022
resulting file permissions:
{code}-- 1 th dev 1263 Apr 24 14:59 upon-20080424145932.jar{code}
Only jar file published, sha1, md5, and xml files not:
{code}/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts
for com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp49772sha1 (Permission denied){code}
expected permissions:
{code}-rw-r--r--{code}
all files should have been published
Case 3:
Used value for publishPermissions: 0666
resulting file permissions:
{code} -rw-r--r-- 1 th dev 1263 Apr 24 15:16 upon-20080424151611.jar{code}
Only jar file published, sha1, md5, and xml files not:
{code}/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts
for com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp17387sha1 (Permission denied){code}
expected permissions:
{code}--{code}
all files should have been published
was (Author: hagis):
Not quite there yet, I still cannot publish artifacts so that they would be
readable by other users.
I would have expected the publishPermissions attribute to work the same way as
umask, but it seems to be the negative. Alone, this would be acceptable, if
properly documented, but if I set the publishPermissions attribute to a value
that produces the file permissions that I want, the publishing of the ivy
files, sha1 and md5 files fails!
Case 1:
Used value for publishPermissions: 0222
resulting file permissions:
--w--- 1 th dev 1263 Apr 24 15:07 upon-20080424150713.jar
expected permissions:
-r--r--r--
Case 2:
Used value for publishPermissions: 0022
resulting file permissions:
-- 1 th dev 1263 Apr 24 14:59 upon-20080424145932.jar
Only jar file published, sha1, md5, and xml files not:
/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts for
com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp49772sha1 (Permission denied)
expected permissions:
-rw-r--r--
all files should have been published
Case 3:
Used value for publishPermissions: 0666
resulting file permissions:
-rw-r--r-- 1 th dev 1263 Apr 24 15:16 upon-20080424151611.jar
Only jar file published, sha1, md5, and xml files not:
/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts for
com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp17387sha1 (Permission denied)
expected permissions:
--
all files should have been published
make it possible to specify permissions of published files for the SSH
resolver
---
Key: IVY-764
URL: https://issues.apache.org/jira/browse/IVY-764
Project: Ivy
Issue Type: Improvement
Affects Versions: 2.0.0-beta-2
Reporter: Tero Hagström
Assignee: Maarten Coene
Fix For: 2.0-RC1
When we use the ssh resolver to publish artifacts to a repository on our
server, the access permissions of the created files only allow reading by the
user that published the artifacts. As a result, no one else can get the
artifacts from the repository, which completely defeats it's purpose.
File permissions look like this:
-rw--- 1 atu dev 875 Mar 10 12:34 core-20080310123411.jar
-rw--- 1 atu dev 40 Mar 10 12:34 core-20080310123411.jar.sha1
-rw--- 1 atu dev 32 Mar 10 12:34 core-20080310123411.jar.md5
-rw--- 1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml
-rw--- 1 atu dev 40 Mar 10 12:34 ivy-20080310123411.xml.sha1
-rw--- 1 atu dev 32 Mar 10 12:34 ivy-20080310123411.xml.md5
I could not find any way to configure or otherwise affect the file
permissions. Is there a way?
BTW, with Ivy 1.4.1 the permissions looked like this:
-rw-rw-r-- 1 th dev 877 Mar 6 10:08 core-20080306100813.jar
-rw-rw-r-- 1 th dev 40 Mar 6 10:08 core-20080306100813.jar.sha1
[jira] Commented: (IVY-810) Duplidate entries after a resolve.
[ https://issues.apache.org/jira/browse/IVY-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12592558#action_12592558 ] Nicolas Lalevée commented on IVY-810: - The warning you get is about a module which you are trying to get in two different configurations. Ivy does the resolve and evict conflits for only one configuration at a time. The resolve process is one by one configuration. If you have a use case where you have to build a classpath with a lot of different configuration, then you should consider having a new configuration that extends the other ones. Although in most case I think the configurations themselves should be fixed. For instance in Eclipse you might want to resolve 3 kind of configurations: compile, test, and runtime. And then you get the warning, because test and runtime conflicts on one dependency. So this means that the ant target that will run the tests (after doing a resolve only on the test configuration) will actually use a different version of a dependency from the one used at runtime, from the one use by the ant target which build the jar. So tests are not running in the same environment as the runtime one. Then you should fix the dependencies by having a direct dependency on the module that generated the conflict. Actually you might want to introduce a private core configuration, which will resolve the problematic dependency, and then make runtime and test extends that core configuration. The topic has been also discussed here : http://mail-archives.apache.org/mod_mbox/ant-dev/200801.mbox/[EMAIL PROTECTED] Duplidate entries after a resolve. -- Key: IVY-810 URL: https://issues.apache.org/jira/browse/IVY-810 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: James Rosko I'm getting this error in the ivy console: There are some duplicates entries due to conflicts between the resolved configurations (*): and one dependent module is being picked up twice, two versions of the same project. I'm using the latest-revision conflict-manager. Project A has two dependencies that depend on different versions of a 4th project. A is getting both versions. A depends on B and B depends on version 1 of D. A also depends on C and C depends on version 2 of D. In this case A does not directly depend on D. D is not listed as a dependency of projects A's ivy.xml file. A-B-D1 and A-C-D2 The problem does not occur when A directly depends on D A-D What could be causing this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-810) Duplidate entries after a resolve.
[ https://issues.apache.org/jira/browse/IVY-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVY-810. - Resolution: Invalid So there is no bug here. Thought I will bookmark this bug, it would be interesting to add it to an FAQ. Duplidate entries after a resolve. -- Key: IVY-810 URL: https://issues.apache.org/jira/browse/IVY-810 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-beta-2 Reporter: James Rosko I'm getting this error in the ivy console: There are some duplicates entries due to conflicts between the resolved configurations (*): and one dependent module is being picked up twice, two versions of the same project. I'm using the latest-revision conflict-manager. Project A has two dependencies that depend on different versions of a 4th project. A is getting both versions. A depends on B and B depends on version 1 of D. A also depends on C and C depends on version 2 of D. In this case A does not directly depend on D. D is not listed as a dependency of projects A's ivy.xml file. A-B-D1 and A-C-D2 The problem does not occur when A directly depends on D A-D What could be causing this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-815) SFTPRepository incorrectly calculates last modified time for resources
[
https://issues.apache.org/jira/browse/IVY-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVY-815.
-
Resolution: Fixed
Assignee: Nicolas Lalevée
Good catch David, and thanks for contributing !
SFTPRepository incorrectly calculates last modified time for resources
--
Key: IVY-815
URL: https://issues.apache.org/jira/browse/IVY-815
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0-beta-2
Environment: Pretty sure this is irrelevant but anyway...
Ivy client running on Windows XP
SFTP repository running on OpenSuse Linux
Reporter: David Maplesden
Assignee: Nicolas Lalevée
Fix For: 2.0-RC1
Attachments: SFTPRepository.diff
Original Estimate: 0.02h
Remaining Estimate: 0.02h
When the {{org.apache.ivy.plugins.repository.sftp.SFTPRepository}}
implementation calculates the last modified time for the resources it returns
it uses an {{int}} constant {{MILLIS_PER_SECOND}} to multiply the {{int}}
value returned by {{attrs.getMTime()}}.
This means the calculation is done using integer arithmetic but the result is
virtually always too big for an {{int}} value and so it overflows, returning
a negative number.
This can easily be fixed by changing the {{MILLIS_PER_SECOND}} constant to
{{long}}, the multiplication is then done using longs and the result does not
overflow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-633) Packaging Data Parsed Incorrectly in Maven 2 POM
[
https://issues.apache.org/jira/browse/IVY-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595317#action_12595317
]
Nicolas Lalevée commented on IVY-633:
-
Jose Noheda found a workaround
(http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200805.mbox/[EMAIL
PROTECTED]).
The dependency that has a bundle packaging, make a direct dependency to it in
your module. And add an artifact tag specifying you want the type jar. And
do exclude it in any other dependancy that transitively depends on it.
For instance, this does work:
{code:xml}
ivy-module version=1.3
info organisation=myorg module=mymodule /
dependencies
dependency org=org.springframework.security
name=spring-security-acl rev=2.0.1
artifact name=spring-security-acl type=jar /
exclude module=spring-security-core /
/dependency
dependency org=org.springframework.security
name=spring-security-taglibs rev=2.0.1
artifact name=spring-security-taglibs type=jar /
exclude module=spring-security-acl /
exclude module=spring-security-core /
/dependency
dependency org=org.springframework.security
name=spring-security-core rev=2.0.1
artifact name=spring-security-core type=jar /
/dependency
/dependencies
/ivy-module
{code}
Packaging Data Parsed Incorrectly in Maven 2 POM
Key: IVY-633
URL: https://issues.apache.org/jira/browse/IVY-633
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.0.0-alpha-2
Reporter: Luke Majewski
Fix For: 2.0
There is still an issue with some dependencies whose extension is not
specified in the default manner. The example case is when trying to fetch
some camel JARs.
When trying to get the camel-script-1.2.0 JAR, you see:
[ivy:retrieve] public: tried
[ivy:retrieve]
http://repo1.maven.org/maven2/org/apache/camel/camel-script/1.2.0/camel-script-1.2.0.bundle
Ivy is trying to use the extension bundle and not JAR. This is due to the
code fetching the extension from the packaging element of the POM. The
relevant portion of the POM is here:
parent
groupIdorg.apache.camel/groupId
artifactIdcamel-parent/artifactId
version1.2.0/version
/parent
artifactIdcamel-script/artifactId
packagingbundle/packaging
nameCamel :: Script/name
descriptionCamel Script support/description
Notice the packagingbundle/packaging. Looking at the POM XSD it seems
like this is a valid POM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-19) no support of organization spelling
[ https://issues.apache.org/jira/browse/IVYDE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595814#action_12595814 ] Nicolas Lalevée commented on IVYDE-19: -- As far as I can read the doc and the code, the IVY-55 is not supported anymore ? The only reference to an organization spelling is in pattern matching, which are only used in the ivy settings files. no support of organization spelling --- Key: IVYDE-19 URL: https://issues.apache.org/jira/browse/IVYDE-19 Project: IvyDE Issue Type: Bug Reporter: Xavier Hanin Assignee: Xavier Hanin zhen using organization spelling (american spelling), you lose the benefit of code completion in IvyDE editor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-91) NPE when setting a bad file for the ivy setting path in the global configuration panel
NPE when setting a bad file for the ivy setting path in the global
configuration panel
--
Key: IVYDE-91
URL: https://issues.apache.org/jira/browse/IVYDE-91
Project: IvyDE
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Nicolas Lalevée
Here is the stack trace:
{noformat}
java.lang.NullPointerException
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.getMetaArtifactPath(Unknown
Source)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.getSourcesArtifactPath(Unknown
Source)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.artifacts2ClasspathEntries(Unknown
Source)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.access$5(Unknown
Source)
at org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$2.run(Unknown
Source)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-83) Error while trying to edit an ivy.xml without a configured container
[
https://issues.apache.org/jira/browse/IVYDE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-83.
--
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Nicolas Lalevée
Error while trying to edit an ivy.xml without a configured container
Key: IVYDE-83
URL: https://issues.apache.org/jira/browse/IVYDE-83
Project: IvyDE
Issue Type: Bug
Components: ivy editor
Affects Versions: 2.0.0
Environment: with IVYDE-70 patch
Reporter: Nicolas Lalevée
Assignee: Nicolas Lalevée
Fix For: 2.0.0
In a project containing an ivy.xml, but with no Ivy classpath container
configured, the editor fail to open.
Here is the stack trace:
{noformat}
java.lang.NullPointerException
at org.apache.ivyde.eclipse.ui.core.model.IvyModel.init(IvyModel.java:524)
at
org.apache.ivyde.eclipse.ui.editors.xml.IvyContentAssistProcessor.setFile(IvyContentAssistProcessor.java:255)
at
org.apache.ivyde.eclipse.ui.editors.xml.XMLConfiguration.getContentAssistant(XMLConfiguration.java:101)
at org.eclipse.jface.text.source.SourceViewer.configure(SourceViewer.java:363)
at
org.eclipse.ui.texteditor.AbstractTextEditor.createPartControl(AbstractTextEditor.java:3201)
at
org.eclipse.ui.texteditor.StatusTextEditor.createPartControl(StatusTextEditor.java:53)
at
org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.createPartControl(AbstractDecoratedTextEditor.java:378)
at
org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:190)
at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:343)
at
org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:160)
at org.eclipse.ui.forms.editor.FormEditor.addPage(FormEditor.java:326)
at
org.apache.ivyde.eclipse.ui.editors.IvyEditor.createPageXML(IvyEditor.java:86)
at org.apache.ivyde.eclipse.ui.editors.IvyEditor.addPages(IvyEditor.java:117)
at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:146)
at
org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2739)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:190)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
[jira] Commented: (IVYDE-19) no support of organization spelling
[ https://issues.apache.org/jira/browse/IVYDE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595902#action_12595902 ] Nicolas Lalevée commented on IVYDE-19: -- Does IvyDE support special editing of Ivy settings files ? Or you mean that having a pattern with organization in the settings file makes the completion in the editor of the ivy.xml not work ? no support of organization spelling --- Key: IVYDE-19 URL: https://issues.apache.org/jira/browse/IVYDE-19 Project: IvyDE Issue Type: Bug Reporter: Xavier Hanin Assignee: Xavier Hanin zhen using organization spelling (american spelling), you lose the benefit of code completion in IvyDE editor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVYDE-32) IvyDE 1.0.3 Run configuration problem with Eclipse 3.x
[ https://issues.apache.org/jira/browse/IVYDE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lalevée resolved IVYDE-32. -- Resolution: Fixed IvyDE 1.0.3 Run configuration problem with Eclipse 3.x Key: IVYDE-32 URL: https://issues.apache.org/jira/browse/IVYDE-32 Project: IvyDE Issue Type: Bug Components: classpath container Affects Versions: 1.1.0, 1.2.0 Environment: Windows XP, Eclipse 3.2.0, IvyDE 1.0.3 Reporter: Emmanuel Cordente Assignee: Nicolas Lalevée Fix For: 2.0.0 I'm having an UI problem using IvyDE with Eclipse 3.1 et 3.2. When I add the IvyDE Managed Dependencies in my Eclipse project everything work fine, I have the little windows the indicate where is my ivy.xml file and a list of configuration when I select my ivy file. But when a try to do the same thing inside the Run Configuration to configure a runtime dependencies, I can see the same little windows but the BROWSE button doesn't work and it's impossible to find the ivy.xml file. I Tryed to put the ivy.xml path explicitely but I can't see the configuration list below the browse button. The solution I found for now is to open the .launch file and to choose my configuration directly inside but it's a bit tricky to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-92) Built-in ivyconf include produce an error
Built-in ivyconf include produce an error
-
Key: IVYDE-92
URL: https://issues.apache.org/jira/browse/IVYDE-92
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.0.0
Environment: Linux Ubuntu 8.04 LTS
Eclipse 3.2.2
Reporter: François Guerry
When including a built-in ivyconf file in a custom ivyconf file, for example :
include url=${ivy.default.conf.dir}/ivyconf-public.xml/
it produces an error at resolve time, and make the global resolve process fail.
This inclusion feature was working fine in IvyDe version 1.2.0
Error copy :
Problem occured while using file:/[...]/ivyconf.xml to configure Ivy
java.text.ParseException: failed to load settings from file:/[...]/ivyconf.xml:
io problem while parsing config file:
/org/apache/ivy/core/settings/ivyconf-public.xml
at
org.apache.ivy.core.settings.XmlSettingsParser.doParse(XmlSettingsParser.java:107)
at
org.apache.ivy.core.settings.XmlSettingsParser.parse(XmlSettingsParser.java:93)
at org.apache.ivy.core.settings.IvySettings.load(IvySettings.java:367)
at org.apache.ivy.Ivy.configure(Ivy.java:413)
at org.apache.ivyde.eclipse.IvyPlugin.getIvy(IvyPlugin.java:368)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.init(IvyClasspathContainer.java:115)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries(IvyClasspathContainer.java:688)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.scheduleResolve(IvyClasspathContainer.java:710)
at org.apache.ivyde.eclipse.ui.actions.ResolveAction.run(ResolveAction.java:37)
Visibly, the problem is that the inclusion instruction is translated in a wrong
path, for my case I obtained :
file: /org/apache/ivy/core/settings/ivyconf-public.xml
instead of something like :
jar:file://[.../ivy.jar]!/org/apache/ivy/core/settings/ivyconf-public.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-92) Built-in ivyconf include produce an error
[
https://issues.apache.org/jira/browse/IVYDE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François Guerry updated IVYDE-92:
-
Description:
When including a built-in ivyconf file in a custom ivyconf file, for example :
include url=${ivy.default.conf.dir}/ivyconf-public.xml/
it produces an error at resolve time, and make the global resolve process fail.
This inclusion feature was working fine in IvyDe version 1.2.0
Error copy :
Problem occured while using fil{color}e{color}:/[...]/ivyconf.xml to configure
Ivy
java.text.ParseException: failed to load settings from
fil{color}e{color}:/[...]/ivyconf.xml: io problem while parsing config file:
/org/apache/ivy/core/settings/ivyconf-public.xml
at
org.apache.ivy.core.settings.XmlSettingsParser.doParse(XmlSettingsParser.java:107)
at
org.apache.ivy.core.settings.XmlSettingsParser.parse(XmlSettingsParser.java:93)
at org.apache.ivy.core.settings.IvySettings.load(IvySettings.java:367)
at org.apache.ivy.Ivy.configure(Ivy.java:413)
at org.apache.ivyde.eclipse.IvyPlugin.getIvy(IvyPlugin.java:368)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.init(IvyClasspathContainer.java:115)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries(IvyClasspathContainer.java:688)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.scheduleResolve(IvyClasspathContainer.java:710)
at org.apache.ivyde.eclipse.ui.actions.ResolveAction.run(ResolveAction.java:37)
Visibly, the problem is that the inclusion instruction is translated in a wrong
path, for my case I obtained :
file: /org/apache/ivy/core/settings/ivyconf-public.xml
instead of something like :
jar:fil{color}e{color}://[...]/ivy.jar!/org/apache/ivy/core/settings/ivyconf-public.xml
was:
When including a built-in ivyconf file in a custom ivyconf file, for example :
include url=${ivy.default.conf.dir}/ivyconf-public.xml/
it produces an error at resolve time, and make the global resolve process fail.
This inclusion feature was working fine in IvyDe version 1.2.0
Error copy :
Problem occured while using file:/[...]/ivyconf.xml to configure Ivy
java.text.ParseException: failed to load settings from file:/[...]/ivyconf.xml:
io problem while parsing config file:
/org/apache/ivy/core/settings/ivyconf-public.xml
at
org.apache.ivy.core.settings.XmlSettingsParser.doParse(XmlSettingsParser.java:107)
at
org.apache.ivy.core.settings.XmlSettingsParser.parse(XmlSettingsParser.java:93)
at org.apache.ivy.core.settings.IvySettings.load(IvySettings.java:367)
at org.apache.ivy.Ivy.configure(Ivy.java:413)
at org.apache.ivyde.eclipse.IvyPlugin.getIvy(IvyPlugin.java:368)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.init(IvyClasspathContainer.java:115)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries(IvyClasspathContainer.java:688)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.scheduleResolve(IvyClasspathContainer.java:710)
at org.apache.ivyde.eclipse.ui.actions.ResolveAction.run(ResolveAction.java:37)
Visibly, the problem is that the inclusion instruction is translated in a wrong
path, for my case I obtained :
file: /org/apache/ivy/core/settings/ivyconf-public.xml
instead of something like :
jar:file://[.../ivy.jar]!/org/apache/ivy/core/settings/ivyconf-public.xml
Built-in ivyconf include produce an error
-
Key: IVYDE-92
URL: https://issues.apache.org/jira/browse/IVYDE-92
Project: IvyDE
Issue Type: Bug
Components: classpath container
Affects Versions: 2.0.0
Environment: Linux Ubuntu 8.04 LTS
Eclipse 3.2.2
Reporter: François Guerry
When including a built-in ivyconf file in a custom ivyconf file, for example :
include url=${ivy.default.conf.dir}/ivyconf-public.xml/
it produces an error at resolve time, and make the global resolve process
fail.
This inclusion feature was working fine in IvyDe version 1.2.0
Error copy :
Problem occured while using fil{color}e{color}:/[...]/ivyconf.xml to
configure Ivy
java.text.ParseException: failed to load settings from
fil{color}e{color}:/[...]/ivyconf.xml: io problem while parsing config file:
/org/apache/ivy/core/settings/ivyconf-public.xml
at
org.apache.ivy.core.settings.XmlSettingsParser.doParse(XmlSettingsParser.java:107)
at
org.apache.ivy.core.settings.XmlSettingsParser.parse(XmlSettingsParser.java:93)
at org.apache.ivy.core.settings.IvySettings.load(IvySettings.java:367)
at org.apache.ivy.Ivy.configure(Ivy.java:413)
at org.apache.ivyde.eclipse.IvyPlugin.getIvy(IvyPlugin.java:368)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer$IvyResolveJob.init(IvyClasspathContainer.java:115)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries
