You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by "Bleeker, Troy C." <Bl...@mayo.edu> on 2013/02/21 23:53:17 UTC
compile versus package
The command
mvn clean compile package
is now in the doc for command line build however I was wondering if that is really doing two things. If a developer just wants to run code and not package up all the deliverables is this sufficient:
mvn clean compile
Thanks
Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical Statistics and Informatics
Phone: 507-293-1574 * Fax: 507-284-0360 * bleeker.troy@mayo.edu
Mayo Clinic * 200 First Street SW * Rochester, MN 55905 * www.mayoclinic.org
RE: compile versus package
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
Hi Andy,
That's a really good point (there are some dependencies which are actually no longer required).
https://issues.apache.org/jira/browse/CTAKES-168 opened to track this...
Probably worth reviewing and removing those. mvn dependency:tree could help output the full tree.
--Pei
> -----Original Message-----
> From: Andy McMurry [mailto:mcmurry.andy@gmail.com]
> Sent: Friday, February 22, 2013 10:10 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: compile versus package
>
> Suggestion: after cTAKES graduation we should reduce the amount of
> packaging dependancies.
>
> For example, does the Smoking Pipeline depend on the medication NER?
> I swam through the source code and didn't see any reason for the
> dependancy.
> http://svn.apache.org/viewvc/incubator/ctakes/trunk/ctakes-smoking-
> status/pom.xml?view=markup
>
> (post graduation cleanup)
>
> On Feb 22, 2013, at 9:39 AM, "Chen, Pei" <Pe...@childrens.harvard.edu>
> wrote:
>
> > Hi Troy,
> > Yes, you are correct- it really is doing two things.
> > mvn clean compile should be sufficient if using mvn to run and resolve
> dependencies which is nice.
> > (We can update the docs if that makes it simpler) package is
> > convenient in certain situations when it's convenient to have all of the 3rd
> party and transient dependencies downloaded and bundled up such as
> running it outside mvn with custom processes/scripts etc.
> >
> > --Pei
> >
> >> -----Original Message-----
> >> From: Bleeker, Troy C. [mailto:Bleeker.Troy@mayo.edu]
> >> Sent: Thursday, February 21, 2013 5:54 PM
> >> To: ctakes-dev@incubator.apache.org
> >> Subject: compile versus package
> >>
> >> The command
> >> mvn clean compile package
> >> is now in the doc for command line build however I was wondering if
> >> that is really doing two things. If a developer just wants to run
> >> code and not package up all the deliverables is this sufficient:
> >> mvn clean compile
> >>
> >> Thanks
> >> Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical
> >> Statistics and Informatics
> >> Phone: 507-293-1574 * Fax: 507-284-0360 * bleeker.troy@mayo.edu
> Mayo
> >> Clinic * 200 First Street SW * Rochester, MN 55905 *
> >> www.mayoclinic.org
> >
Re: compile versus package
Posted by Andy McMurry <mc...@gmail.com>.
Suggestion: after cTAKES graduation we should reduce the amount of packaging dependancies.
For example, does the Smoking Pipeline depend on the medication NER?
I swam through the source code and didn't see any reason for the dependancy.
http://svn.apache.org/viewvc/incubator/ctakes/trunk/ctakes-smoking-status/pom.xml?view=markup
(post graduation cleanup)
On Feb 22, 2013, at 9:39 AM, "Chen, Pei" <Pe...@childrens.harvard.edu> wrote:
> Hi Troy,
> Yes, you are correct- it really is doing two things.
> mvn clean compile should be sufficient if using mvn to run and resolve dependencies which is nice.
> (We can update the docs if that makes it simpler)
> package is convenient in certain situations when it's convenient to have all of the 3rd party and transient dependencies downloaded and bundled up such as running it outside mvn with custom processes/scripts etc.
>
> --Pei
>
>> -----Original Message-----
>> From: Bleeker, Troy C. [mailto:Bleeker.Troy@mayo.edu]
>> Sent: Thursday, February 21, 2013 5:54 PM
>> To: ctakes-dev@incubator.apache.org
>> Subject: compile versus package
>>
>> The command
>> mvn clean compile package
>> is now in the doc for command line build however I was wondering if that is
>> really doing two things. If a developer just wants to run code and not
>> package up all the deliverables is this sufficient:
>> mvn clean compile
>>
>> Thanks
>> Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical Statistics and
>> Informatics
>> Phone: 507-293-1574 * Fax: 507-284-0360 * bleeker.troy@mayo.edu Mayo
>> Clinic * 200 First Street SW * Rochester, MN 55905 * www.mayoclinic.org
>
RE: compile versus package
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
Hi Troy,
Yes, you are correct- it really is doing two things.
mvn clean compile should be sufficient if using mvn to run and resolve dependencies which is nice.
(We can update the docs if that makes it simpler)
package is convenient in certain situations when it's convenient to have all of the 3rd party and transient dependencies downloaded and bundled up such as running it outside mvn with custom processes/scripts etc.
--Pei
> -----Original Message-----
> From: Bleeker, Troy C. [mailto:Bleeker.Troy@mayo.edu]
> Sent: Thursday, February 21, 2013 5:54 PM
> To: ctakes-dev@incubator.apache.org
> Subject: compile versus package
>
> The command
> mvn clean compile package
> is now in the doc for command line build however I was wondering if that is
> really doing two things. If a developer just wants to run code and not
> package up all the deliverables is this sufficient:
> mvn clean compile
>
> Thanks
> Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical Statistics and
> Informatics
> Phone: 507-293-1574 * Fax: 507-284-0360 * bleeker.troy@mayo.edu Mayo
> Clinic * 200 First Street SW * Rochester, MN 55905 * www.mayoclinic.org
RE: compile versus package
Posted by "Masanz, James J." <Ma...@mayo.edu>.
I was running a pipeline after doing mvn compile without the package
-- James
> -----Original Message-----
> From: ctakes-dev-return-1268-Masanz.James=mayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-1268-
> Masanz.James=mayo.edu@incubator.apache.org] On Behalf Of Bleeker, Troy
> C.
> Sent: Thursday, February 21, 2013 4:53 PM
> To: ctakes-dev@incubator.apache.org
> Subject: compile versus package
>
> The command
> mvn clean compile package
> is now in the doc for command line build however I was wondering if that
> is really doing two things. If a developer just wants to run code and
> not package up all the deliverables is this sufficient:
> mvn clean compile
>
> Thanks
> Troy Bleeker * Senior Business Analyst CBAP(r) * Biomedical Statistics
> and Informatics
> Phone: 507-293-1574 * Fax: 507-284-0360 * bleeker.troy@mayo.edu Mayo
> Clinic * 200 First Street SW * Rochester, MN 55905 * www.mayoclinic.org
Re: compile versus package
Posted by Steven Bethard <st...@Colorado.EDU>.
On Feb 21, 2013, at 11:53 PM, "Bleeker, Troy C." <Bl...@mayo.edu> wrote:
> The command
> mvn clean compile package
> is now in the doc for command line build however I was wondering if that is really doing two things. If a developer just wants to run code and not package up all the deliverables is this sufficient:
> mvn clean compile
That's correct - `mvn compile` should be sufficient if you just want to compile everything.
And in fact, you probably never want to run `mvn compile package` either - `mvn package` will do the compiling as well, so if you run `mvn compile package`, you're actually compiling everything twice.
In general, Maven understands what phases are prerequisites for other phases, so you only need to specify the last phase that you want executed.
Steve