You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jack Stanley <Ja...@ironmountain.com> on 2010/07/30 19:25:33 UTC
Adding the JRE + Jar ulitily to the build
Hi folks. I am a Build / Release Engineer just getting familiar with Maven.
I've been tasked with adding the JRE + the Jar utility to our Maven build.
I have done some research, but thought it would be a really good idea to get
advice from the experts. Here are my questions:
* Should we include the JRE in the maven repo? I didn’t see it in
http://repo1.maven.org/, so I
assume this is not a standard approach. Should we just check it into
SVN? Our project lead
did not have any strong opinions on either approach.
* What is the best way to include it in the build? Should I use the
assembly plugin? If so, does this
code snippet make sense:
<filesets>
<fileset>
<directory>checkout directory/java/jre</directory>
<outputDirectory>target/jre</outputDirectory>
</fileset>
</filesets>
Thanks,
Jack
--
View this message in context: http://maven.40175.n5.nabble.com/Adding-the-JRE-Jar-ulitily-to-the-build-tp2259801p2259801.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Adding the JRE + Jar ulitily to the build
Posted by Stephen Connolly <st...@gmail.com>.
IANAL,
The JRE is one thing...
Last time I checked, the JDK required that you display the EULA to the end
user when installing the JDK...
The net result was that we had to split up our one click installer into
four: install the non-java stuff (Apache HTTPD), then the Sun JDK installer,
then the open source java stuff (Apache Tomcat) and then finally our
commercial code installer.
But your legal heads can make their judgement calls as they see fit
-Stephen
On 4 August 2010 01:00, Jack Stanley <Ja...@ironmountain.com> wrote:
>
> Legal reviewed the license agreement:
> http://www.java.com/en/download/license.jsp . We already distribute the
> JRE
> as part of another product. We do not see any problems with distributing
> the whole and complete JRE or the JDK.
>
> There is some wording under section B of the SUPPLEMENTAL LICENSE TERMS
> section. We are not entirely sure if we are "modifying" the software as
> per
> this section. We only want to repackage the JRE to include the JDK. We
> are
> not redistributing the software... it will be installed as a hosted
> solution
> in our own data centers. Based in this information, it is our opinion that
> it is ok to distribute the JRE + jar utility.
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Adding-the-JRE-Jar-ulitily-to-the-build-tp2259801p2263529.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Adding the JRE + Jar ulitily to the build
Posted by Jack Stanley <Ja...@ironmountain.com>.
Legal reviewed the license agreement:
http://www.java.com/en/download/license.jsp . We already distribute the JRE
as part of another product. We do not see any problems with distributing
the whole and complete JRE or the JDK.
There is some wording under section B of the SUPPLEMENTAL LICENSE TERMS
section. We are not entirely sure if we are "modifying" the software as per
this section. We only want to repackage the JRE to include the JDK. We are
not redistributing the software... it will be installed as a hosted solution
in our own data centers. Based in this information, it is our opinion that
it is ok to distribute the JRE + jar utility.
--
View this message in context: http://maven.40175.n5.nabble.com/Adding-the-JRE-Jar-ulitily-to-the-build-tp2259801p2263529.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Adding the JRE + Jar ulitily to the build
Posted by Ron Wheeler <rw...@artifact-software.com>.
Sounds like you are doing things the way it was intended and the way
that most people do it.
I would be interested in hearing what your legal eagles have to say.
Ron
On 02/08/2010 6:18 PM, Jack Stanley wrote:
> Sorry for not being clear. We use Nexus. When I worked at Cisco, we used
> Artifactory. I have not yet worked with this project team long enough yet
> to determine which one is better.
>
> For now, I have jarred up the JRE and uploaded it to our local Nexus
> repository. We will definitely run this by legal to make sure we are in the
> clear.
>
> I found out we're already using the Assembly plugin. I made a few mods to
> the POM files and we are in business... the jar is getting packaged up
> properly in the build.
>
> Jack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Adding the JRE + Jar ulitily to the build
Posted by Jack Stanley <Ja...@ironmountain.com>.
Sorry for not being clear. We use Nexus. When I worked at Cisco, we used
Artifactory. I have not yet worked with this project team long enough yet
to determine which one is better.
For now, I have jarred up the JRE and uploaded it to our local Nexus
repository. We will definitely run this by legal to make sure we are in the
clear.
I found out we're already using the Assembly plugin. I made a few mods to
the POM files and we are in business... the jar is getting packaged up
properly in the build.
Jack
--
View this message in context: http://maven.40175.n5.nabble.com/Adding-the-JRE-Jar-ulitily-to-the-build-tp2259801p2262342.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Adding the JRE + Jar ulitily to the build
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 31/07/2010 10:29 AM, Christoph Kutzinski wrote:
> I second the advice about getting an own repository manager.
> For completeness: Nexus isn't the only repo manager out there :-)
You are right.
I got Nexus as my first repo without very much research and have been
really happy since then with the functionality and the support forum.
It has improved productivity and improved our understanding of the
"Maven way".
I am sure that others have had good success with the other repo choices.
The main point that I would like to make is to get your own repo ASAP if
you want to enjoy working with Maven.
Ron
> I know at least of Artifactory and Apache Archiva.
> I've made good experience with both Nexus and Artifactory. Cannot say
> anything about Archiva.
>
> Am 31.07.2010 15:03, schrieb Ron Wheeler:
>> On 30/07/2010 1:25 PM, Jack Stanley wrote:
>>> Hi folks. I am a Build / Release Engineer just getting familiar with
>>> Maven.
>>> I've been tasked with adding the JRE + the Jar utility to our Maven
>>> build.
>>> I have done some research, but thought it would be a really good idea
>>> to get
>>> advice from the experts. Here are my questions:
>>>
>>> * Should we include the JRE in the maven repo? I didn’t see it in
>>> http://repo1.maven.org/, so I
>>> assume this is not a standard approach. Should we just check it into
>>> SVN? Our project lead
>>> did not have any strong opinions on either approach.
>>>
>>> * What is the best way to include it in the build? Should I use the
>>> assembly plugin? If so, does this
>>> code snippet make sense:
>>>
>>> <filesets>
>>> <fileset>
>>> <directory>checkout directory/java/jre</directory>
>>> <outputDirectory>target/jre</outputDirectory>
>>> </fileset>
>>> </filesets>
>>>
>>> Thanks,
>>> Jack
>>>
>> Others might be able to give you a more definitive answer but my
>> understanding is as follows
>> 1) Sun licensing does not permit some or all of their products to be
>> stored in Maven Central
>> 2) You can download the JRE and upload it into your own Nexus repo. I am
>> not sure if anyone has pom files that you could use but you can put the
>> Java jars in without them.
>>
>>
>> It sounds like you are in a serious development organization. If you are
>> going to use Maven, you need at least the free version of Nexus and may
>> be able to make good use of the professional version.
>> Using Maven without your own Repo is way too hard.
>> We did that for 2 years and it is one of the biggest regrets that we
>> have about how we started the project.
>>
>> Do you want to distribute the JRE with your application or just use it
>> in the build step as a "provided" dependency?
>>
>> I hope that this helps.
>>
>> Ron
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Adding the JRE + Jar ulitily to the build
Posted by Christoph Kutzinski <ku...@gmx.de>.
I second the advice about getting an own repository manager.
For completeness: Nexus isn't the only repo manager out there :-)
I know at least of Artifactory and Apache Archiva.
I've made good experience with both Nexus and Artifactory. Cannot say
anything about Archiva.
Am 31.07.2010 15:03, schrieb Ron Wheeler:
> On 30/07/2010 1:25 PM, Jack Stanley wrote:
>> Hi folks. I am a Build / Release Engineer just getting familiar with
>> Maven.
>> I've been tasked with adding the JRE + the Jar utility to our Maven
>> build.
>> I have done some research, but thought it would be a really good idea
>> to get
>> advice from the experts. Here are my questions:
>>
>> * Should we include the JRE in the maven repo? I didn’t see it in
>> http://repo1.maven.org/, so I
>> assume this is not a standard approach. Should we just check it into
>> SVN? Our project lead
>> did not have any strong opinions on either approach.
>>
>> * What is the best way to include it in the build? Should I use the
>> assembly plugin? If so, does this
>> code snippet make sense:
>>
>> <filesets>
>> <fileset>
>> <directory>checkout directory/java/jre</directory>
>> <outputDirectory>target/jre</outputDirectory>
>> </fileset>
>> </filesets>
>>
>> Thanks,
>> Jack
>>
> Others might be able to give you a more definitive answer but my
> understanding is as follows
> 1) Sun licensing does not permit some or all of their products to be
> stored in Maven Central
> 2) You can download the JRE and upload it into your own Nexus repo. I am
> not sure if anyone has pom files that you could use but you can put the
> Java jars in without them.
>
>
> It sounds like you are in a serious development organization. If you are
> going to use Maven, you need at least the free version of Nexus and may
> be able to make good use of the professional version.
> Using Maven without your own Repo is way too hard.
> We did that for 2 years and it is one of the biggest regrets that we
> have about how we started the project.
>
> Do you want to distribute the JRE with your application or just use it
> in the build step as a "provided" dependency?
>
> I hope that this helps.
>
> Ron
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Adding the JRE + Jar ulitily to the build
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 30/07/2010 1:25 PM, Jack Stanley wrote:
> Hi folks. I am a Build / Release Engineer just getting familiar with Maven.
> I've been tasked with adding the JRE + the Jar utility to our Maven build.
> I have done some research, but thought it would be a really good idea to get
> advice from the experts. Here are my questions:
>
> * Should we include the JRE in the maven repo? I didn’t see it in
> http://repo1.maven.org/, so I
> assume this is not a standard approach. Should we just check it into
> SVN? Our project lead
> did not have any strong opinions on either approach.
>
> * What is the best way to include it in the build? Should I use the
> assembly plugin? If so, does this
> code snippet make sense:
>
> <filesets>
> <fileset>
> <directory>checkout directory/java/jre</directory>
> <outputDirectory>target/jre</outputDirectory>
> </fileset>
> </filesets>
>
> Thanks,
> Jack
>
Others might be able to give you a more definitive answer but my
understanding is as follows
1) Sun licensing does not permit some or all of their products to be
stored in Maven Central
2) You can download the JRE and upload it into your own Nexus repo. I am
not sure if anyone has pom files that you could use but you can put the
Java jars in without them.
It sounds like you are in a serious development organization. If you are
going to use Maven, you need at least the free version of Nexus and may
be able to make good use of the professional version.
Using Maven without your own Repo is way too hard.
We did that for 2 years and it is one of the biggest regrets that we
have about how we started the project.
Do you want to distribute the JRE with your application or just use it
in the build step as a "provided" dependency?
I hope that this helps.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org