Provide option to have symbolic link for kamel local build --integration-directory <folder> #2179
Labels
Comments
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 13, 2021
provide command to add dependencies on classpath. todo: - continue to handle 1.3- - report error of the command downloading dependencies - rename or change flow to allow cleaning the internal folder - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh - use an API to refresh the classpath to avoid workaround of changing back and forth the settings - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 14, 2021
provide command to add dependencies on classpath. todo: - write test to handle 1.3- - rename or change flow to allow cleaning the internal folder - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh - use an API to refresh the classpath to avoid workaround of changing back and forth the settings - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 15, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use an API to refresh the classpath to avoid workaround of changing back and forth the settings - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 15, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use an API to refresh the classpath to avoid workaround of changing back and forth the settings - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 15, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 27, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 27, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 27, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 27, 2021
provide command to add dependencies on classpath. todo: - wait for 1.4.0 release and remove the maven snapshot repository used for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh - write test to handle 1.3- (or not and consider it as no more supported and keep code for now as best-effort) limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 27, 2021
provide command to add dependencies on classpath. no test to handle 1.3- as this use case is considered as best effort only. for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 27, 2021
provide command to add dependencies on classpath. no test to handle 1.3- as this use case is considered as best effort only. for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 28, 2021
provide command to add dependencies on classpath. no test to handle 1.3- as this use case is considered as best effort only. for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 28, 2021
provide command to add dependencies on classpath. no test to handle 1.3- as this use case is considered as best effort only. for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to apupier/vscode-camelk
that referenced
this issue
Apr 28, 2021
provide command to add dependencies on classpath. no test to handle 1.3- as this use case is considered as best effort only. for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
added a commit
to camel-tooling/vscode-camelk
that referenced
this issue
Apr 29, 2021
provide command to add dependencies on classpath. no test to handle 1.3- as this use case is considered as best effort only. for next iterations: - automatically call refresh when needed (to be determined when it is needed) - use a specific folder per file - find a way to support two files opened at same time in different window which are not sharing the same dependencies - allow to configure parameters to provide to the call (like a maven repository) - provide progress report of refresh limitations due to upstream: - some notations not supported apache/camel-k#2213 - a lot of place is taken in internal folders as jars are duplicated instead of simply pointing to local .m2 apache/camel-k#2179 - use an API to refresh the classpath to avoid workaround of changing back and forth the settings redhat-developer/vscode-java#1874 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
|
This issue has been automatically marked as stale due to 90 days of inactivity. |
|
still relevant |
|
This issue has been automatically marked as stale due to 90 days of inactivity. |
|
still relevant |
|
This issue has been automatically marked as stale due to 90 days of inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
having all artefacts copied in the destination folder is taking time and a lot of space. Locally, it can be useful to have just a link created to gain time and space. A link to the local .m2/repository artefacts for instance (maybe jitpack also have a cache?)
The text was updated successfully, but these errors were encountered: