[jira] Created: (IVYDE-143) Conversion from "file:" to "project:" fails
Conversion from "file:" to "project:" fails
---
Key: IVYDE-143
URL: https://issues.apache.org/jira/browse/IVYDE-143
Project: IvyDE
Issue Type: Bug
Affects Versions: 2.0.0.final
Environment: ubuntu, eclipse 3.4.0, ivyde trunk 12/24/2008
Reporter: Will Gorman
I have been using the alpha version of IvyDE, and attempted to use a trunk
build and encountered the following error when I load my existing ivyde eclipse
based project:
The project name '.' from 'project://./ivysettings.xml' was not found (project
'pentaho-xul-gwt' and ivy file 'ivy.xml')
According to IVYDE-94, my "file://./ivysettings.xml" should automatically
converted. Our problem is that we used "file:./ivysettings.xml". Here is my
suggested fix in
IvyClasspathContainerConfiguration.java:readOldIvySettings():
replace:
return PROJECT_SCHEME_PREFIX + url.getPath();
with:
String urlpath = url.getPath();
if (urlpath != null && urlpath.length() > 1 && urlpath.startsWith("."))
{
urlpath = urlpath.substring(1);
}
return PROJECT_SCHEME_PREFIX + urlpath;
Thanks!
Will
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-13) Support variables in ivyconf.xml
[ https://issues.apache.org/jira/browse/IVYDE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Gorman updated IVYDE-13: - Attachment: ivyde-13-patch.txt Hello, I've attached an SVN patch, based on the trunk as of 12/24/2008, that implements this feature. The patch includes a new advanced property called "build property files". I had previously posted an older version of this patch to IVYDE-90, not realizing the subtle differences between the two issues. We use ivy parameterization in our build environment, which is resolved using our ant build files and properties. Because IvyDE works outside of that environment, we needed a way to provide IvyDE with the build.properties file. Thanks, Will > Support variables in ivyconf.xml > > > Key: IVYDE-13 > URL: https://issues.apache.org/jira/browse/IVYDE-13 > Project: IvyDE > Issue Type: Improvement >Reporter: Andreas Schildbach >Assignee: Xavier Hanin > Fix For: 2.0.0.final > > Attachments: ivyde-13-patch.txt > > > It is common practise to use variables like in ivyconf.xml in order to not > hardcode the repository path. > Unfortunately, it is not possible to set these variables with IvyDE. I'd like > to propose setting of such variables directly or maybe by a properties file > in the IvyDE preferences and project configuration pages. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (IVYDE-159) Explicit ordering of configurations
Explicit ordering of configurations --- Key: IVYDE-159 URL: https://issues.apache.org/jira/browse/IVYDE-159 Project: IvyDE Issue Type: Improvement Reporter: Will Gorman In IvyDE, I can select which configurations are used in the eclipse environment, but I can't specify in which order the jar files are listed in the classpath. This is important in our JUnit environment, because we have mock jars that override the default jars for testing. In our Ant environment, the test configuration appears in the classpath before the default configuration, but I can't specify that in IvyDE. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-90) IvyDE does not do property value expansion
[
https://issues.apache.org/jira/browse/IVYDE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Gorman updated IVYDE-90:
-
Attachment: IVYDE-90_patch.zip
We ran into the same issue at Pentaho. I made a minor change to the
initialization of the ivy object, with a new property called Build Property
Files. It simply loads the specified properties files and populates the
IvySettings object with those properties. Feel free to use the code.
> IvyDE does not do property value expansion
> --
>
> Key: IVYDE-90
> URL: https://issues.apache.org/jira/browse/IVYDE-90
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
>Affects Versions: 2.0.0.alpha1
> Environment: Eclipse 3.3.1
> MyEclipse 6.0.1
> Aptana 1.1.6
> Ivy/IvyDE plugins from xoocode
>Reporter: Michael Laccetti
> Attachments: IVYDE-90_patch.zip
>
>
> If I create an Ivy properties file with the variables defined in them, and
> then reference those variables in the built script, Ivy via Ant will pick
> them up, and inject the correct information. However, the same does not go
> for IvyDE; it conks out trying to retrieve
> --${lala}.
> Sample ivy.roperties
> {noformat}
> spring.version=2.5.3
> {noformat}
> Sample ivysettings.xml
> {code:xml}
>
>
>
> {code}
> Sample ivy.xml
> {code:xml}
>
>
>
>
>rev="${spring.version}" />
>
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-90) IvyDE does not do property value expansion
[
https://issues.apache.org/jira/browse/IVYDE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627656#action_12627656
]
Will Gorman commented on IVYDE-90:
--
Hi Nicolas,
First, thanks for reviewing the patch. I implemented this very quickly to get
past our issues, so it most definitely needs reviewed and tested before
acceptance. I apologize for not submitting diff files. I was unable to locate
your SVN path for the project, it does not seem to be referenced here:
http://ant.apache.org/ivy/ivyde/ . I should have mentioned the source version I
used to make the changes, again I apologize. In our environment, we use ant
properties to resolve parameters defined in our ivy.xml files. Because we use
ivy within ant, and IvyDE does not, I needed a way to resolve the ant property
files I use.
Hope that clears things up!
Will
> IvyDE does not do property value expansion
> --
>
> Key: IVYDE-90
> URL: https://issues.apache.org/jira/browse/IVYDE-90
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
>Affects Versions: 2.0.0.alpha1
> Environment: Eclipse 3.3.1
> MyEclipse 6.0.1
> Aptana 1.1.6
> Ivy/IvyDE plugins from xoocode
>Reporter: Michael Laccetti
> Attachments: IVYDE-90_patch.zip
>
>
> If I create an Ivy properties file with the variables defined in them, and
> then reference those variables in the built script, Ivy via Ant will pick
> them up, and inject the correct information. However, the same does not go
> for IvyDE; it conks out trying to retrieve
> --${lala}.
> Sample ivy.roperties
> {noformat}
> spring.version=2.5.3
> {noformat}
> Sample ivysettings.xml
> {code:xml}
>
>
>
> {code}
> Sample ivy.xml
> {code:xml}
>
>
>
>
>rev="${spring.version}" />
>
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-90) IvyDE does not do property value expansion
[
https://issues.apache.org/jira/browse/IVYDE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632791#action_12632791
]
Will Gorman commented on IVYDE-90:
--
Hi Nicolas, should I create another case for the scenario where the properties
are coming from ant vs. an ivysettings file? In our scenario, we parameterize
from ant build.properties files which aren't explicitly referenced in the
ivysettings.xml.
Thanks!
Will
> IvyDE does not do property value expansion
> --
>
> Key: IVYDE-90
> URL: https://issues.apache.org/jira/browse/IVYDE-90
> Project: IvyDE
> Issue Type: Bug
> Components: classpath container
>Affects Versions: 2.0.0.alpha1
> Environment: Eclipse 3.3.1
> MyEclipse 6.0.1
> Aptana 1.1.6
> Ivy/IvyDE plugins from xoocode
>Reporter: Michael Laccetti
>Assignee: Nicolas Lalevée
> Fix For: 2.0
>
> Attachments: IVYDE-90_patch.zip
>
>
> If I create an Ivy properties file with the variables defined in them, and
> then reference those variables in the built script, Ivy via Ant will pick
> them up, and inject the correct information. However, the same does not go
> for IvyDE; it conks out trying to retrieve
> --${lala}.
> Sample ivy.roperties
> {noformat}
> spring.version=2.5.3
> {noformat}
> Sample ivysettings.xml
> {code:xml}
>
>
>
> {code}
> Sample ivy.xml
> {code:xml}
>
>
>
>
>rev="${spring.version}" />
>
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
