Use Advanced Search to search the entire archive.
[jsr363-experts] Re: EDR doc
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: EDR doc
- Date: Tue, 16 Dec 2014 11:36:35 +0100
Why would you need them in a POM? Do you plan to compile the API based on
the ME SDK?
As soon as say a proper Maven plugin exists, I guess we could do that.
Similar for RI, we should build the RI on a CI server, too.
Planning a JIRA task for that soon.
Werner
On Tue, Dec 16, 2014 at 11:30 AM, Leonardo Lima
<
>
wrote:
>
>
The CLDC would be the first choice for the "smallest" API implementation.
>
Then, for optional packages, optional parts would be used (like Liblets or
>
Service Pattern) for the RI.
>
>
I'll try what you said later and see if works well on the ME SDK and
>
outside of it.
>
>
On Tue, Dec 16, 2014 at 2:36 AM, Martin Desruisseaux <
>
>
>
wrote:
>
>
>
> Hello Leonardo
>
>
>
> Thanks for the tip. There is many JAR, I'm not sure which one in this
>
> list need to be selected. If there is a volunteer for configuring the
>
> pom.xml file, I could help by the mailing list. The step would be:
>
>
>
> - Choose the name of an optional Maven property which would contains
>
> the path to the CLDC installation directory.
>
> - In the pom.xml, define a profile which would be automatically
>
> enabled if and only if the above-cited Maven property is defined.
>
> - In the above-cited profile, set the "bootstrap class path" option
>
> for the "maven-compiler" plugin. The option value would use the
>
> above-cited
>
> property for defining the paths to the JAR files.
>
>
>
> Martin
>
>
>
>