Re: Configure default execution phase

[Manfred Moser]

well... with using the profile you can add more plugins and all sorts of other 
stuff and the command will stay that long 

Manfre

Stanimir Stamenkov wrote on 2019-12-23 09:50 (GMT -08:00):

> Mon, 23 Dec 2019 18:16:13 +0100 (CET), /Manfred Moser/:
> 
>> Just make a profile and add it all in there.
> 
> Are you suggesting adding something like:
> 
> 
> 
> liquibase-update
> 
> 
> 
> org.liquibase
> liquibase-maven-plugin
> 
> 
> process-resources
> 
> update
> 
> 
> 
> 
> 
> 
> 
> 
> 
> then using command like:
> 
> mvn process-resources -P liquibase-update
> 
> ?
> 
> It doesn't appear shorter than:
> 
> mvn process-resources liquibase:update
> 
> and I guess I'll have to replicate the profile for all possible 
> liquibase goals (possibly 5-10 of them).  All in all, it doesn't appear 
> feasible unless I'm missing something with your suggestion?
> 
> 
>> Stanimir Stamenkov wrote on 2019-12-22 09:04 (GMT -08:00):
>> 
>>> I'm having a POM like:
>>>
>>>  
>>>  
>>>  
>>>  
>>>  org.liquibase
>>>  liquibase-maven-plugin
>>>  3.8.3
>>>  
>>>  ...
>>>  
>>>  
>>>  
>>>  
>>>  
>>>
>>> I don't want the plugin executed as part of the build but I want to be 
>>> able to execute its goals [1] explicitly.  The goals get executed 
>>> directly (no build phases get triggered), f.e.:
>>>
>>>  mvn liquibase:update
>>>
>>> but then it usually (while not necessarily, depending on project 
>>> configuration) require "process-resources" to be completed, so I have to:
>>>
>>>  mvn process-resources liquibase:update
>>>
>>> Is it possible to trigger "process-resources" automatically via plugin 
>>> configuration in POM (a`la Gradle's dependsOn [2]), or this is just 
>>> hard-coded in the plugin itself?
>>>
>>> [1] https://www.liquibase.org/documentation/maven/index.html
>>> [2] https://docs.gradle.org/current/userguide/more_about_tasks.html
> 
> -- 
> Stanimir
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Configure default execution phase

[Stanimir Stamenkov]

Mon, 23 Dec 2019 18:16:13 +0100 (CET), /Manfred Moser/:


Just make a profile and add it all in there.


Are you suggesting adding something like:



liquibase-update



org.liquibase
liquibase-maven-plugin


process-resources

update









then using command like:

mvn process-resources -P liquibase-update

?

It doesn't appear shorter than:

mvn process-resources liquibase:update

and I guess I'll have to replicate the profile for all possible 
liquibase goals (possibly 5-10 of them).  All in all, it doesn't appear 
feasible unless I'm missing something with your suggestion?




Stanimir Stamenkov wrote on 2019-12-22 09:04 (GMT -08:00):


I'm having a POM like:

 
 
 
 
 org.liquibase
 liquibase-maven-plugin
 3.8.3
 
 ...
 
 
 
 
 

I don't want the plugin executed as part of the build but I want to be 
able to execute its goals [1] explicitly.  The goals get executed 
directly (no build phases get triggered), f.e.:


 mvn liquibase:update

but then it usually (while not necessarily, depending on project 
configuration) require "process-resources" to be completed, so I have to:


 mvn process-resources liquibase:update

Is it possible to trigger "process-resources" automatically via plugin 
configuration in POM (a`la Gradle's dependsOn [2]), or this is just 
hard-coded in the plugin itself?


[1] https://www.liquibase.org/documentation/maven/index.html
[2] https://docs.gradle.org/current/userguide/more_about_tasks.html


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Configure default execution phase

[Manfred Moser]

Just make a profile and add it all in there.

Stanimir Stamenkov wrote on 2019-12-22 09:04 (GMT -08:00):

> I'm having a POM like:
> 
> 
> 
> 
> 
> org.liquibase
> liquibase-maven-plugin
> 3.8.3
> 
> ...
> 
> 
> 
> 
> 
> 
> I don't want the plugin executed as part of the build but I want to be 
> able to execute its goals [1] explicitly.  The goals get executed 
> directly (no build phases get triggered), f.e.:
> 
> mvn liquibase:update
> 
> but then it usually (while not necessarily, depending on project 
> configuration) require "process-resources" to be completed, so I have to:
> 
> mvn process-resources liquibase:update
> 
> Is it possible to trigger "process-resources" automatically via plugin 
> configuration in POM (a`la Gradle's dependsOn [2]), or this is just 
> hard-coded in the plugin itself?
> 
> [1] https://www.liquibase.org/documentation/maven/index.html
> [2] https://docs.gradle.org/current/userguide/more_about_tasks.html
> 
> -- 
> Stanimir
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Publishing Maven site as an docker image

[Manfred Moser]

Maven sites are just static HTML. Why would you publish that as a Docker image? 

You can of course ... just run nginx or apache httpd and put the files in the 
root web server folder.. 

Manfred

Nick Stolwijk wrote on 2019-12-23 00:58 (GMT -08:00):

> Hi folks,
> 
> Has anyone tried to publish the site generated by Maven as a docker image?
> Are there examples of such a setup?
> 
> With regards,
> 
> Nick Stolwijk
> 
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
> 
> Lord Baden-Powell
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Configure default execution phase

[Stanimir Stamenkov]

Mon, 23 Dec 2019 11:37:19 +0100, /Thomas Broyer/:


It's hardcoded in the plugin (and this is why you have things like
sources:jar and sources:jar-no-fork depending on how you need/want to
invoke it)


I see now – thanks for clarifying.  I've always wondered what those 
*-no-fork goals are for – I've thought it has to do something with 
forking the JVM process but seems I've been completely wrong. :-)  In 
any case, I think dynamic "executePhase" configuration would be really 
nice to have, the same way one could dynamically bind a goal to a 
specific phase.




Le dim. 22 déc. 2019 à 18:04, Stanimir Stamenkov a écrit :


I'm having a POM like:

  
  
  
  
  org.liquibase
  liquibase-maven-plugin
  3.8.3
  
  ...
  
  
  
  
  

I don't want the plugin executed as part of the build but I want to be
able to execute its goals [1] explicitly.  The goals get executed
directly (no build phases get triggered), f.e.:

  mvn liquibase:update

but then it usually (while not necessarily, depending on project
configuration) require "process-resources" to be completed, so I have to:

  mvn process-resources liquibase:update

Is it possible to trigger "process-resources" automatically via plugin
configuration in POM (a`la Gradle's dependsOn [2]), or this is just
hard-coded in the plugin itself?

[1] https://www.liquibase.org/documentation/maven/index.html
[2] https://docs.gradle.org/current/userguide/more_about_tasks.html


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Building multi-module project using -pl

[Kypros Chrysanthou]

Hello,

I'm trying to build a multi-module project (along with its submodules)
using the -pl option.
When passing the aggregate module to -pl the submodules are not picked up.

If I use the -amd option, the submodules that are also child modules (i.e.
they define the aggregate module as parent) are picked up.

I would expect that -am would "also make" the submodules but it seems that
they are not identified as dependencies.

I have created a dummy project for this:
https://github.com/chkypros/aggregation

Any advice/thought on why this is so would be greatly appreciated.
Also, if this behaviour is expected, how should I go about doing this?

Kind regards,
Kypros Chrysanthou

Re: Configure default execution phase

[Thomas Broyer]

That would reconfigure which phase the mojo is bound to (if any, which is
not the case if the Liquibase plugin) when executed as part of the build
lifecycle; it won't allow you to fork a lifecycle when calling the goal
directly.

Le lun. 23 déc. 2019 à 15:02, Mark Prins  a écrit :

> You should be able to change the default execution phase of a plugin (as
> well as bind a goal to any other phase) by configuring explicit
> executions bound to a phase
>
> see: https://maven.apache.org/guides/mini/guide-default-execution-ids.html
>
> You would need to use an id of "default-update" to override the update
> goal.
>
> -M
>
>
> On 22-12-19 18:04, Stanimir Stamenkov wrote:
> > I'm having a POM like:
> >
> >  
> >  
> >  
> >  
> >  org.liquibase
> >  liquibase-maven-plugin
> >  3.8.3
> >  
> >  ...
> >  
> >  
> >  
> >  
> >  
> >
> > I don't want the plugin executed as part of the build but I want to be
> > able to execute its goals [1] explicitly.  The goals get executed
> > directly (no build phases get triggered), f.e.:
> >
> >  mvn liquibase:update
> >
> > but then it usually (while not necessarily, depending on project
> > configuration) require "process-resources" to be completed, so I have to:
> >
> >  mvn process-resources liquibase:update
> >
> > Is it possible to trigger "process-resources" automatically via plugin
> > configuration in POM (a`la Gradle's dependsOn [2]), or this is just
> > hard-coded in the plugin itself?
> >
> > [1] https://www.liquibase.org/documentation/maven/index.html
> > [2] https://docs.gradle.org/current/userguide/more_about_tasks.html
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Configure default execution phase

[Mark Prins]

You should be able to change the default execution phase of a plugin (as 
well as bind a goal to any other phase) by configuring explicit 
executions bound to a phase


see: https://maven.apache.org/guides/mini/guide-default-execution-ids.html

You would need to use an id of "default-update" to override the update goal.

-M


On 22-12-19 18:04, Stanimir Stamenkov wrote:

I'm having a POM like:

     
     
     
     
     org.liquibase
     liquibase-maven-plugin
     3.8.3
     
     ...
     
     
     
     
     

I don't want the plugin executed as part of the build but I want to be 
able to execute its goals [1] explicitly.  The goals get executed 
directly (no build phases get triggered), f.e.:


     mvn liquibase:update

but then it usually (while not necessarily, depending on project 
configuration) require "process-resources" to be completed, so I have to:


     mvn process-resources liquibase:update

Is it possible to trigger "process-resources" automatically via plugin 
configuration in POM (a`la Gradle's dependsOn [2]), or this is just 
hard-coded in the plugin itself?


[1] https://www.liquibase.org/documentation/maven/index.html
[2] https://docs.gradle.org/current/userguide/more_about_tasks.html




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: is there a maven plugin to identify ancient pom dependencies

[Maarten Mulders]

Good catch, Mark. I wouldn't have guessed from the README or the 
announcement [1].
Indeed, this implementation seems based on some assumption about central 
repository behaviour.
If your repository manager would set that header to the date the 
artifact was released, it might be of help. But I, for one, wouldn't 
trust on that assumption alone.


Cheers,

Maarten

[1] https://twitter.com/royvanrijn/status/803902527360159744

On December 23, 2019 at 14:53, Mark Prins wrote:


On 21-12-19 21:02, Maarten Mulders wrote:

Maybe this can help you: 
https://github.com/portofrotterdam/versiondebt-plugin
As far as I can see, it doesn't allow you to configure "what is old". 
It does tell you how old dependencies are.


not really; it seems that it uses the "last modified" from a 
URLConnection to the artifact in a repository, so unlikely to provide a 
date related to the time of release. it will be unreliable in any 
situation that a maven proxy is used.


see:
https://github.com/portofrotterdam/versiondebt-plugin/blob/e500e2d2a1fce4eb350633c7515b04107dae42d6/versiondebt-maven-plugin/src/main/java/com/portofrotterdam/versiondebt/VersiondebtMojo.java#L218-L229

Important disclaimer at the end of the page: it isn't maintained on a 
regular basis.


Cheers,

Maarten

On December 21, 2019 at 18:50, Enrico Olivelli wrote:

Something like this:
https://www.mojohaus.org/versions-maven-plugin/display-dependency-updates-mojo.html 
Hope that helps

Enrico

Il sab 21 dic 2019, 18:31 mark  ha scritto:

On 2019-12-20 13:39, Marlow, Andrew wrote:
Hello everyone,

I am using the owasp maven dependency plugin to tell me when I am
using components that have CVEs. That's great. I was wondering if
there was something similar that would tell me when I am using very
old components (where the judgement about what is old is configurable,
e.g number of years, months etc).

never seen one, it would be hard without querying the source repository
for the release tag/branch for the moment the release was cut (which is
problematic in case a minimal release pom is in use. The current pom
does not have this/a timestamp for this and you cannot use the file 
date.


I guess you could look at the date of the (class) files inside the
artifact (jar) to determine build/release date, not sure how that would
work out with shaded dependencies or provided manifest files

-M

*Andrew Marlow*

Software Engineer Specialist, Apex

38^th Floor, 25 Canada Square,

Canary Wharf, London E14 5LQ

*T*:  020-8081-2367 / 07966-451-521
*E*: andrew.mar...@fisglobal.com 

*FIS | Advancing the way the world pays, banks and invests(tm) *

cid:image004.png@01D542DF.1DA72090
cid:image005.png@01D542DF.1DA72090
cid:image008.png@01D542DF.1DA72090


The information contained in this message is proprietary and/or
confidential jadajadajada...
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: is there a maven plugin to identify ancient pom dependencies

[Mark Prins]

On 21-12-19 21:02, Maarten Mulders wrote:
Maybe this can help you: 
https://github.com/portofrotterdam/versiondebt-plugin
As far as I can see, it doesn't allow you to configure "what is old". It 
does tell you how old dependencies are.


not really; it seems that it uses the "last modified" from a 
URLConnection to the artifact in a repository, so unlikely to provide a 
date related to the time of release. it will be unreliable in any 
situation that a maven proxy is used.


see:
https://github.com/portofrotterdam/versiondebt-plugin/blob/e500e2d2a1fce4eb350633c7515b04107dae42d6/versiondebt-maven-plugin/src/main/java/com/portofrotterdam/versiondebt/VersiondebtMojo.java#L218-L229


Important disclaimer at the end of the page: it isn't maintained on a 
regular basis.


Cheers,

Maarten

On December 21, 2019 at 18:50, Enrico Olivelli wrote:


Something like this:
https://www.mojohaus.org/versions-maven-plugin/display-dependency-updates-mojo.html 



Hope that helps
Enrico

Il sab 21 dic 2019, 18:31 mark  ha scritto:

On 2019-12-20 13:39, Marlow, Andrew wrote:
Hello everyone,

I am using the owasp maven dependency plugin to tell me when I am
using components that have CVEs. That's great. I was wondering if
there was something similar that would tell me when I am using very
old components (where the judgement about what is old is configurable,
e.g number of years, months etc).

never seen one, it would be hard without querying the source repository
for the release tag/branch for the moment the release was cut (which is
problematic in case a minimal release pom is in use. The current pom
does not have this/a timestamp for this and you cannot use the file date.

I guess you could look at the date of the (class) files inside the
artifact (jar) to determine build/release date, not sure how that would
work out with shaded dependencies or provided manifest files

-M

*Andrew Marlow*

Software Engineer Specialist, Apex

38^th Floor, 25 Canada Square,

Canary Wharf, London E14 5LQ

*T*:  020-8081-2367 / 07966-451-521
*E*: andrew.mar...@fisglobal.com 

*FIS | Advancing the way the world pays, banks and invests(tm) *

cid:image004.png@01D542DF.1DA72090
cid:image005.png@01D542DF.1DA72090
cid:image008.png@01D542DF.1DA72090


The information contained in this message is proprietary and/or
confidential jadajadajada...


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Publishing Maven site as an docker image

[Enrico Olivelli]

Hi
What's the purpose of this new image?
Can you explain better please?

There is a mojo, site:run to run the website, so it should be easy to do
what you want.

Anyway the site is static so you can copy it to any web server

You can also deploy automatically the site via sftp or any provider
supported by Maven Wagon

Enrico

Il lun 23 dic 2019, 10:00 Nick Stolwijk  ha
scritto:

> Hi folks,
>
> Has anyone tried to publish the site generated by Maven as a docker image?
> Are there examples of such a setup?
>
> With regards,
>
> Nick Stolwijk
>
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
>
> Lord Baden-Powell
>

Re: Configure default execution phase

[Thomas Broyer]

It's hardcoded in the plugin (and this is why you have things like
sources:jar and sources:jar-no-fork depending on how you need/want to
invoke it)

Le dim. 22 déc. 2019 à 18:04, Stanimir Stamenkov
 a écrit :

> I'm having a POM like:
>
>  
>  
>  
>  
>  org.liquibase
>  liquibase-maven-plugin
>  3.8.3
>  
>  ...
>  
>  
>  
>  
>  
>
> I don't want the plugin executed as part of the build but I want to be
> able to execute its goals [1] explicitly.  The goals get executed
> directly (no build phases get triggered), f.e.:
>
>  mvn liquibase:update
>
> but then it usually (while not necessarily, depending on project
> configuration) require "process-resources" to be completed, so I have to:
>
>  mvn process-resources liquibase:update
>
> Is it possible to trigger "process-resources" automatically via plugin
> configuration in POM (a`la Gradle's dependsOn [2]), or this is just
> hard-coded in the plugin itself?
>
> [1] https://www.liquibase.org/documentation/maven/index.html
> [2] https://docs.gradle.org/current/userguide/more_about_tasks.html
>
> --
> Stanimir
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Publishing Maven site as an docker image

[Nick Stolwijk]

Hi folks,

Has anyone tried to publish the site generated by Maven as a docker image?
Are there examples of such a setup?

With regards,

Nick Stolwijk

~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~

Lord Baden-Powell