[
https://issues.apache.org/jira/browse/IVY-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713741#action_12713741
]
Maarten Coene commented on IVY-1074:
------------------------------------
If I remember correctly, the current trunk version doesn't throw an error any
longer if a properties file is missing.
Would this solve your problem?
> Provide a 'required' attribute to ivy settings/properties element to control
> reaction to missing properties file
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IVY-1074
> URL: https://issues.apache.org/jira/browse/IVY-1074
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Reporter: Jeff Glatz
> Priority: Critical
>
> we use ivy in our company and have our repository under version control which
> is checked out alongside our projects. our setup is designed to work when run
> from builds on an integration server, on developer's machines, and from under
> IDE plugins for IDEA and eclipse.
> because the repository checkout will vary based on environment, we expect
> that a property called 'libraries.root' is defined and points to the
> individual repository location. when run from ant, this value is provided as
> a build property. the issue arises when ivy is run from the plugins because
> 'libraries.root' is never set.
> to facilitate this, we use a single ivysettings.xml file which does the
> following:
> {code:xml|title=ivysettings.xml}
> <ivysettings>
> ...
> <properties file="${ivy.settings.dir}/${user.name}.properties"/>
> ...
> </ivysettings>
> {code}
> to load a properties file for the user where 'libraries.root' is defined.
> the problem is that there are cases, such as when run under the integration
> server, where the user will not have a properties file. in this case, the
> configuration blows up. i propose adding a 'required' attribute to control
> the reaction to a missing file:
> {code:xml|title=ivysettings.xml}
> <ivysettings>
> ...
> <properties file="${ivy.settings.dir}/${user.name}.properties"
> required="false"/>
> ...
> </ivysettings>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
