[
https://issues.apache.org/jira/browse/FELIX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569693#action_12569693
]
Karl Pauls commented on FELIX-486:
----------------------------------
Stuart, if I understand you correctly, you say that starting with parent pom
1.0.2 we do target 1.3 bytecode - In other words, new releases and snapshots
will do the same assuming they use the parent pom in version >= 1.0.2, correct?
If so, lets just update everything to 1.0.2 and publish new snapshots. Next, we
can release the artifacts you name above. Ultimately, the next release of Felix
will then use the correctly compiled artifacts and trunk will use the correct
snapshots for now.
> Felix release conting mixed bytecode: 1.3 and 1.4, we should compile all as
> 1.3
> -------------------------------------------------------------------------------
>
> Key: FELIX-486
> URL: https://issues.apache.org/jira/browse/FELIX-486
> Project: Felix
> Issue Type: Improvement
> Affects Versions: 1.0.1, 1.0.2, 1.0.3
> Reporter: Stefano Lenzi
> Priority: Minor
> Attachments: bytecode.jre13.r620538.patch,
> bytecode.jre13.r620865.patch, bytecode.jre13.vs.SNAPSHOT.r620865.patch,
> bytecode.jre13.vs.SNAPSHOT.r626008.patch
>
>
> I found out that the following released project:
> - shell-1.0.0
> - javax.servlet-1.0.0
> - org.osgi.core-1.0.0
> - shell.tui-1.0.0
> which are used by the felix-1.0.3 release are compiled for JRE 1.4, so we
> ended up with a felix released which is partially compiled for JRE 1.4 and
> for JRE 1.3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
