Difference between pom.xml and pom-installed.xml

[chandresh pancholi]

Hi,

It might sound silly but why are we using pom-installed.xml in every module?
I never saw and used other than pom.xml.This is first time i am seeing two
pom in single module.



Thanks



--
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:[hidden email]
Contact:08951803660

[Raul Kripalani]

I asked myself the same question. It's actually generated by
the flatten-maven-plugin defined in ignite-parent.

I guess it's used for debugging purposes? Although I'm not sure why you
would want this permanently in the build. Someone will likely clarify.

Moreover, in my opinion it should be generated inside the target/ directory.

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Aug 6, 2015 at 1:48 PM, chandresh pancholi <
[hidden email]> wrote:

> Hi,
>
> It might sound silly but why are we using pom-installed.xml in every
> module?
> I never saw and used other than pom.xml.This is first time i am seeing two
> pom in single module.
>
>
>
> Thanks
>
>
>
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:[hidden email]
> Contact:08951803660
>

[Anton Vinogradov]

Hello,

It used to generate pom files that will be uploaded to maven repository.

Plugins configuration can be changed to

  <configuration>
                    <flattenMode>minimum</flattenMode>

<flattenedPomFilename>pom-installed.xml</flattenedPomFilename>

<outputDirectory>${project.basedir}/target/</outputDirectory>
                </configuration>

in this case pom-installed.xml will be generated at target directory. But
we have to check this improvement brings no issues with deploy to maven
repository.

On Thu, Aug 6, 2015 at 3:55 PM, Raul Kripalani <[hidden email]> wrote:

> I asked myself the same question. It's actually generated by
> the flatten-maven-plugin defined in ignite-parent.
>
> I guess it's used for debugging purposes? Although I'm not sure why you
> would want this permanently in the build. Someone will likely clarify.
>
> Moreover, in my opinion it should be generated inside the target/
> directory.
>
> Regards,
>
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Thu, Aug 6, 2015 at 1:48 PM, chandresh pancholi <
> [hidden email]> wrote:
>
> > Hi,
> >
> > It might sound silly but why are we using pom-installed.xml in every
> > module?
> > I never saw and used other than pom.xml.This is first time i am seeing
> two
> > pom in single module.
> >
> >
> >
> > Thanks
> >
> >
> >
> > --
> > Chandresh Pancholi
> > Senior Software Engineer
> > Flipkart.com
> > Email-id:[hidden email]
> > Contact:08951803660
> >
>

[Raul Kripalani]

Sounds good. Since this plugin is only required to accompany the deploy
plugin and not in normal (local) builds, you could also put it inside a
profile.

BTW - you can also try using the flatten:clean goal to remove this file
rather than the pattern in the standard clean plugin config, but in reality
it should make no difference.

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Aug 6, 2015 at 2:19 PM, Anton Vinogradov <[hidden email]>
wrote:

> Hello,
>
> It used to generate pom files that will be uploaded to maven repository.
>
> Plugins configuration can be changed to
>
>   <configuration>
>                     <flattenMode>minimum</flattenMode>
>
> <flattenedPomFilename>pom-installed.xml</flattenedPomFilename>
>
> <outputDirectory>${project.basedir}/target/</outputDirectory>
>                 </configuration>
>
> in this case pom-installed.xml will be generated at target directory. But
> we have to check this improvement brings no issues with deploy to maven
> repository.
>
> On Thu, Aug 6, 2015 at 3:55 PM, Raul Kripalani <[hidden email]> wrote:
>
> > I asked myself the same question. It's actually generated by
> > the flatten-maven-plugin defined in ignite-parent.
> >
> > I guess it's used for debugging purposes? Although I'm not sure why you
> > would want this permanently in the build. Someone will likely clarify.
> >
> > Moreover, in my opinion it should be generated inside the target/
> > directory.
> >
> > Regards,
> >
> > *Raúl Kripalani*
> > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> > Integration specialist
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Thu, Aug 6, 2015 at 1:48 PM, chandresh pancholi <
> > [hidden email]> wrote:
> >
> > > Hi,
> > >
> > > It might sound silly but why are we using pom-installed.xml in every
> > > module?
> > > I never saw and used other than pom.xml.This is first time i am seeing
> > two
> > > pom in single module.
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > > --
> > > Chandresh Pancholi
> > > Senior Software Engineer
> > > Flipkart.com
> > > Email-id:[hidden email]
> > > Contact:08951803660
> > >
> >
>