[
https://issues.apache.org/jira/browse/ARIES-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194272#comment-13194272
]
David Jencks commented on ARIES-798:
------------------------------------
I've been working on upgrading asm to version 4.0 for java 7 compatibility, and
although the packages are all unchanged and binary compatible with their
predecessors, the change in dependencies generally means that the only versions
that will work are the up to date snapshots versions. I'm wondering if trying
to maintain two sets of versions is worth anything. At the moment I'm updating
the "normal" versions to be the needed snapshots. (nothing yet committed, this
is just a comment)
> Provide a profile to switch between stable (released) and snapshot aries
> dependencies
> -------------------------------------------------------------------------------------
>
> Key: ARIES-798
> URL: https://issues.apache.org/jira/browse/ARIES-798
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: blueprint.annotation.api-0.3.2,
> blueprint.annotation.impl-0.3.2, blueprint.cm-0.3.2,
> blueprint.jex.evaluator-0.1.0, blueprint-core-0.4.1
> Reporter: David Jencks
> Assignee: David Jencks
>
> Following some discussion on the dev list about what to build against, I
> thought I'd try profiles so you can choose. Apparently you can't put both
> sets of versions in profiles, one has to be in plain properties. I chose to
> put the snapshots in a "dev" profile.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
