You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/02/17 18:30:12 UTC
[jira] [Commented] (REEF-115) Harmonize the versions of REEF Java
and REEF .NET
[ https://issues.apache.org/jira/browse/REEF-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324511#comment-14324511 ]
Markus Weimer commented on REEF-115:
------------------------------------
I did some googling on bing for this. It seems tricky to coerce Maven into fetching the version number of a project from a file. Can we coerce the msbuild scripts to pick it up from the maven version? Maybe by having maven generate a build properties file for msbuild?
> Harmonize the versions of REEF Java and REEF .NET
> -------------------------------------------------
>
> Key: REEF-115
> URL: https://issues.apache.org/jira/browse/REEF-115
> Project: REEF
> Issue Type: Improvement
> Components: REEF, REEF.NET
> Reporter: Markus Weimer
> Assignee: Tony Majestro
>
> Currently, REEF.NET and REEF Java do not share a common version. This should be remedied such that all artifacts carry the version of the next release (e.g. {{0.11-incubating}}). This requires changes mostly on the .NET side.
> Given this, we might want to move the actual version string out of the POMs and reference it from these as well as the .NET build files, if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)