[ALL] Maven plugins common configuration.

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[ALL] Maven plugins common configuration.

Artem Barger
Hi,

While working on creating multi module configuration for commons-rng
component I've extracted all configurations for maven plugins such as: pmd,
findbugs, checkstyle into separate module "commons-rng-build-tools". Such
that parent project can now refer to it within build plugins section and
will imply it for all modules reducing the need to repeat it for each
module again (or copy same files into new modules).

Now I think that it could be beneficial to have this "build-tools" common
component across all Apache Commons, so it will provide same configurations
for checkstyle, pmd and etc at once.

For example configuration of pmd could look something like:

<build>
<plugins>
<plugin>
  <artifactId>maven-pmd-plugin</artifactId>
  <version>${pmd.version}</version>
  <configuration>
    <targetJdk>${maven.compiler.target}</targetJdk>
    <skipEmptyReport>false</skipEmptyReport>
    <rulesets>
      <ruleset>pmd/pmd-ruleset.xml</ruleset>
    </rulesets>
  </configuration>
  <dependencies>
    <dependency>
      <groupId>org.apache.commons</groupId>
      <artifactId>commons-build-tools</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
  </dependencies>
</plugin>
</plugins>
</build>

And reporting section:

<reporting>
<plugins>
<plugin>
  <artifactId>maven-pmd-plugin</artifactId>
  <version>${pmd.version}</version>
  <configuration>
    <targetJdk>${maven.compiler.target}</targetJdk>
    <skipEmptyReport>false</skipEmptyReport>
    <rulesets>
      <ruleset>pmd/pmd-ruleset.xml</ruleset>
    </rulesets>
  </configuration>
  <reportSets>
    <reportSet>
      <reports>
        <report>pmd</report>
        <report>cpd</report>
      </reports>
    </reportSet>
  </reportSets>
</plugin>
</plugins>
</reporting>

At some sense this will be similar to "commons-parent", while keeping only
configuration resources for report generating plugins and for static
analysis tools.

WDYT?

PS. There is temporal example within "commons-rng" git repo inside
"multimodule" branch.

Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

sebb-2-2
On 26 October 2016 at 01:14, Artem Barger <[hidden email]> wrote:

> Hi,
>
> While working on creating multi module configuration for commons-rng
> component I've extracted all configurations for maven plugins such as: pmd,
> findbugs, checkstyle into separate module "commons-rng-build-tools". Such
> that parent project can now refer to it within build plugins section and
> will imply it for all modules reducing the need to repeat it for each
> module again (or copy same files into new modules).
>
> Now I think that it could be beneficial to have this "build-tools" common
> component across all Apache Commons, so it will provide same configurations
> for checkstyle, pmd and etc at once.
>
> For example configuration of pmd could look something like:
>
> <build>
> <plugins>
> <plugin>
>   <artifactId>maven-pmd-plugin</artifactId>
>   <version>${pmd.version}</version>
>   <configuration>
>     <targetJdk>${maven.compiler.target}</targetJdk>
>     <skipEmptyReport>false</skipEmptyReport>
>     <rulesets>
>       <ruleset>pmd/pmd-ruleset.xml</ruleset>
>     </rulesets>
>   </configuration>
>   <dependencies>
>     <dependency>
>       <groupId>org.apache.commons</groupId>
>       <artifactId>commons-build-tools</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>   </dependencies>
> </plugin>
> </plugins>
> </build>
>
> And reporting section:
>
> <reporting>
> <plugins>
> <plugin>
>   <artifactId>maven-pmd-plugin</artifactId>
>   <version>${pmd.version}</version>
>   <configuration>
>     <targetJdk>${maven.compiler.target}</targetJdk>
>     <skipEmptyReport>false</skipEmptyReport>
>     <rulesets>
>       <ruleset>pmd/pmd-ruleset.xml</ruleset>
>     </rulesets>
>   </configuration>
>   <reportSets>
>     <reportSet>
>       <reports>
>         <report>pmd</report>
>         <report>cpd</report>
>       </reports>
>     </reportSet>
>   </reportSets>
> </plugin>
> </plugins>
> </reporting>
>
> At some sense this will be similar to "commons-parent", while keeping only
> configuration resources for report generating plugins and for static
> analysis tools.
>
> WDYT?

Why not include it in commons parent?

> PS. There is temporal example within "commons-rng" git repo inside
> "multimodule" branch.
>
> Best regards,
>                       Artem Barger.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Jörg Schaible-5
In reply to this post by Artem Barger
Artem Barger wrote:

> Hi,
>
> While working on creating multi module configuration for commons-rng
> component I've extracted all configurations for maven plugins such as:
> pmd, findbugs, checkstyle into separate module "commons-rng-build-tools".
> Such that parent project can now refer to it within build plugins section
> and will imply it for all modules reducing the need to repeat it for each
> module again (or copy same files into new modules).
>
> Now I think that it could be beneficial to have this "build-tools" common
> component across all Apache Commons, so it will provide same
> configurations for checkstyle, pmd and etc at once.
>
> For example configuration of pmd could look something like:
>
> <build>
> <plugins>
> <plugin>
>   <artifactId>maven-pmd-plugin</artifactId>
>   <version>${pmd.version}</version>
>   <configuration>
>     <targetJdk>${maven.compiler.target}</targetJdk>
>     <skipEmptyReport>false</skipEmptyReport>
>     <rulesets>
>       <ruleset>pmd/pmd-ruleset.xml</ruleset>
>     </rulesets>
>   </configuration>
>   <dependencies>
>     <dependency>
>       <groupId>org.apache.commons</groupId>
>       <artifactId>commons-build-tools</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>   </dependencies>
> </plugin>
> </plugins>
> </build>
>
> And reporting section:
>
> <reporting>
> <plugins>
> <plugin>
>   <artifactId>maven-pmd-plugin</artifactId>
>   <version>${pmd.version}</version>
>   <configuration>
>     <targetJdk>${maven.compiler.target}</targetJdk>
>     <skipEmptyReport>false</skipEmptyReport>
>     <rulesets>
>       <ruleset>pmd/pmd-ruleset.xml</ruleset>
>     </rulesets>
>   </configuration>
>   <reportSets>
>     <reportSet>
>       <reports>
>         <report>pmd</report>
>         <report>cpd</report>
>       </reports>
>     </reportSet>
>   </reportSets>
> </plugin>
> </plugins>
> </reporting>
>
> At some sense this will be similar to "commons-parent", while keeping only
> configuration resources for report generating plugins and for static
> analysis tools.
>
> WDYT?


You may put both parts into an own profile that is activated automatically
at the extistence of pmd/pmd-ruleset.xml. Each component has then a chance
to use it or not simply by providing that file.


> PS. There is temporal example within "commons-rng" git repo inside
> "multimodule" branch.


Cheers,
Jörg



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
In reply to this post by sebb-2-2
On Wed, Oct 26, 2016 at 3:20 AM, sebb <[hidden email]> wrote:

> Why not include it in commons parent?
>

Because than it will introduce cyclic dependencies I guess. You will
declare "commons-parent"
is parent module and later add it as dependency for maven plugin config.​


Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
In reply to this post by Jörg Schaible-5
On Wed, Oct 26, 2016 at 10:08 AM, Jörg Schaible <
[hidden email]> wrote:

> You may put both parts into an own profile that is activated automatically
> at the extistence of pmd/pmd-ruleset.xml. Each component has then a chance
> to use it or not simply by providing that file.
>

​Not sure I follow you in the given context. I mean why one would create a
profile for
pmd plugin activated on presence of​ rule set xml?

I just wanted to put all these configurations for build plugins which
executed during
"mvn site" into some common place and reuse them later.


Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Jörg Schaible-5
Hi Artem,

Artem Barger wrote:

> On Wed, Oct 26, 2016 at 10:08 AM, Jörg Schaible <
> [hidden email]> wrote:
>
>> You may put both parts into an own profile that is activated
>> automatically at the extistence of pmd/pmd-ruleset.xml. Each component
>> has then a chance to use it or not simply by providing that file.
>>
>
> ​Not sure I follow you in the given context. I mean why one would create a
> profile for
> pmd plugin activated on presence of​ rule set xml?

Because you must have a mechanism to trigger the e.g. the PMD plugin
individually, if you put the declarationsof it into the commons parent
(pluginManagement as well as report).
 
> I just wanted to put all these configurations for build plugins which
> executed during
> "mvn site" into some common place and reuse them later.

So you've put all those configuration *files* into this new artifact? Can
those plugins access their configuration files when provided as resource?

Cheers,
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
On Wed, Oct 26, 2016 at 10:36 AM, Jörg Schaible <
[hidden email]> wrote:

> Because you must have a mechanism to trigger the e.g. the PMD plugin
> individually, if you put the declarationsof it into the commons parent
> (pluginManagement as well as report).
>
>
​Ok, I see, I didn't mean to put these into commons parent though.​



> > I just wanted to put all these configurations for build plugins which
> > executed during
> > "mvn site" into some common place and reuse them later.
>
> So you've put all those configuration *files* into this new artifact? Can
> those plugins access their configuration files when provided as resource?
>

​Yes, and yes, you can see how it works in "commons-rng", there is
a branch "multimodule" I have added my POC there.​



Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Gilles Sadowski
In reply to this post by Artem Barger
Hello.

On Wed, 26 Oct 2016 03:14:59 +0300, Artem Barger wrote:

> Hi,
>
> While working on creating multi module configuration for commons-rng
> component I've extracted all configurations for maven plugins such
> as: pmd,
> findbugs, checkstyle into separate module "commons-rng-build-tools".
> Such
> that parent project can now refer to it within build plugins section
> and
> will imply it for all modules reducing the need to repeat it for each
> module again (or copy same files into new modules).
>
> Now I think that it could be beneficial to have this "build-tools"
> common
> component across all Apache Commons, so it will provide same
> configurations
> for checkstyle, pmd and etc at once.
>
> For example configuration of pmd could look something like:
>
> <build>
> <plugins>
> <plugin>
>   <artifactId>maven-pmd-plugin</artifactId>
>   <version>${pmd.version}</version>
>   <configuration>
>     <targetJdk>${maven.compiler.target}</targetJdk>
>     <skipEmptyReport>false</skipEmptyReport>
>     <rulesets>
>       <ruleset>pmd/pmd-ruleset.xml</ruleset>
>     </rulesets>
>   </configuration>
>   <dependencies>
>     <dependency>
>       <groupId>org.apache.commons</groupId>
>       <artifactId>commons-build-tools</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>   </dependencies>
> </plugin>
> </plugins>
> </build>
>
> And reporting section:
>
> <reporting>
> <plugins>
> <plugin>
>   <artifactId>maven-pmd-plugin</artifactId>
>   <version>${pmd.version}</version>
>   <configuration>
>     <targetJdk>${maven.compiler.target}</targetJdk>
>     <skipEmptyReport>false</skipEmptyReport>
>     <rulesets>
>       <ruleset>pmd/pmd-ruleset.xml</ruleset>
>     </rulesets>
>   </configuration>
>   <reportSets>
>     <reportSet>
>       <reports>
>         <report>pmd</report>
>         <report>cpd</report>
>       </reports>
>     </reportSet>
>   </reportSets>
> </plugin>
> </plugins>
> </reporting>
>
> At some sense this will be similar to "commons-parent", while keeping
> only
> configuration resources for report generating plugins and for static
> analysis tools.
>
> WDYT?

What is the command to "build everything"?

I tried
  $ mvn site
and got an error:
... skipped ...
[INFO] Reactor Summary:
[INFO]
[INFO] Build Tools ........................................ SUCCESS [
17.979 s]
[INFO] Apache Commons Parent RNG .......................... FAILURE [  
4.274 s]
[INFO] Apache Commons RNG Core ............................ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 22.455 s
[INFO] Finished at: 2016-10-26T16:37:27+02:00
[INFO] Final Memory: 43M/451M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project commons-rng: failed to get report for
org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (validate)
on project commons-rng: Execution validate of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed:
Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17 or one of
its dependencies could not be resolved: Could not find artifact
org.apache.commons:commons-rng-build-tools:jar:1.0-SNAPSHOT in
apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]

Apart from that, the setup looks nice although I have no idea if
it can fit the "Commons" way of handling each of its sub-project.

Please let me know whether this can be sorted out so that a
release of "Commons RNG" will not be invalidated because of an
"unusual" project build layout or other incompatibility with the
release policy.

When this is settled, we must review the
   doc/release/release.howto.txt
document and update according to the new layout.

Thanks,
Gilles


>
> PS. There is temporal example within "commons-rng" git repo inside
> "multimodule" branch.
>
> Best regards,
>                       Artem Barger.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
​Hi,



On Wed, Oct 26, 2016 at 5:53 PM, Gilles <[hidden email]>
wrote:

> What is the command to "build everything"?
>
>

> I tried
>  $ mvn site
>

​Try "mvn install site"
​ instead.  For some reason dependencies between is not sorted out and
maven
could not find "commons-rng-build-tools" (posted a question in maven ML
list).




> Apart from that, the setup looks nice although I have no idea if
> it can fit the "Commons" way of handling each of its sub-project.
>
>
​Well, IMO this is fits into "Commons" pretty good, since it
provide common basic set of configs for maven plugins which
used by almost every common component.​



> Please let me know whether this can be sorted out so that a
> release of "Commons RNG" will not be invalidated because of an
> "unusual" project build layout or other incompatibility with the
> release policy.
>
>
​Working on it.



> When this is settled, we must review the
>   doc/release/release.howto.txt
> document and update according to the new layout.
>

​Sure thing.​



Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Jörg Schaible-5
Hi Artem,

Artem Barger wrote:

> ​Hi,
>
> On Wed, Oct 26, 2016 at 5:53 PM, Gilles <[hidden email]>
> wrote:
>
>> What is the command to "build everything"?
>>
>>
>
>> I tried
>>  $ mvn site
>>
>
> ​Try "mvn install site"
> ​ instead.  For some reason dependencies between is not sorted out and
> maven
> could not find "commons-rng-build-tools" (posted a question in maven ML
> list).

The reactor of Maven does not consider plugins itself or dependencies to
plugins for its build order (by design). To support something like this, you
will have to produce a released artifact first.

- Jörg



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
On Wed, Oct 26, 2016 at 6:30 PM, Jörg Schaible <
[hidden email]> wrote:

>
> The reactor of Maven does not consider plugins itself or dependencies to
> plugins for its build order (by design). To support something like this,
> you
> will have to produce a released artifact first.


​In that case I guess following tutorial has a bug:
https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html



Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Gilles Sadowski
In reply to this post by Jörg Schaible-5
On Wed, 26 Oct 2016 17:30:45 +0200, Jörg Schaible wrote:

> Hi Artem,
>
> Artem Barger wrote:
>
>> ​Hi,
>>
>> On Wed, Oct 26, 2016 at 5:53 PM, Gilles
>> <[hidden email]>
>> wrote:
>>
>>> What is the command to "build everything"?
>>>
>>>
>>
>>> I tried
>>>  $ mvn site
>>>
>>
>> ​Try "mvn install site"

That works but does not build the complete site, for which I'd
invoke

$ mvn site:stage

But this then fail with:
... skipped ...
[INFO] Build Tools ........................................ FAILURE [  
0.610 s]
[INFO] Apache Commons Parent RNG .......................... SKIPPED
[INFO] Apache Commons RNG Core ............................ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 0.972 s
[INFO] Finished at: 2016-10-26T18:09:23+02:00
[INFO] Final Memory: 14M/221M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project commons-rng-build-tools: Missing distribution management in
project Build Tools
(org.apache.commons:commons-rng-build-tools:1.0-SNAPSHOT) -> [Help 1]


>> ​ instead.  For some reason dependencies between is not sorted out
>> and
>> maven
>> could not find "commons-rng-build-tools" (posted a question in maven
>> ML
>> list).
>
> The reactor of Maven does not consider plugins itself or dependencies
> to
> plugins for its build order (by design). To support something like
> this, you
> will have to produce a released artifact first.

As maven-ignoramus, I do not follow.
Does it mean that Artem's proposal is not feasible (according to
Commons policy)?

Gilles

>
> - Jörg
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
On Wed, Oct 26, 2016 at 7:14 PM, Gilles <[hidden email]>
wrote:

> could not find "commons-rng-build-tools" (posted a question in maven ML
>>> list).
>>>
>>
>> The reactor of Maven does not consider plugins itself or dependencies to
>> plugins for its build order (by design). To support something like this,
>> you
>> will have to produce a released artifact first.
>>
>
> As maven-ignoramus, I do not follow.
> Does it mean that Artem's proposal is not feasible (according to
> Commons policy)?


​If only we could have build-tools as stand-alone component, that might
solve
all the problems.​ :/


Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
In reply to this post by Gilles Sadowski
On Wed, Oct 26, 2016 at 7:14 PM, Gilles <[hidden email]>
wrote:

> ​Try "mvn install site"
>>>
>>
> That works but does not build the complete site, for which I'd
> invoke
>
> $ mvn site:stage


​Can you try now? I've pushed some changes.​


Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Gilles Sadowski
On Wed, 26 Oct 2016 19:31:18 +0300, Artem Barger wrote:

> On Wed, Oct 26, 2016 at 7:14 PM, Gilles
> <[hidden email]>
> wrote:
>
>> ​Try "mvn install site"
>>>>
>>>
>> That works but does not build the complete site, for which I'd
>> invoke
>>
>> $ mvn site:stage
>
>
> ​Can you try now? I've pushed some changes.​

$ mvn clean install site site:stage

succeeds. :-)

But the modules link are still dead.
[E.g. there is no "apidocs".]

Best,
Gilles

>
> Best regards,
>                       Artem Barger.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Jörg Schaible
In reply to this post by Artem Barger
Artem Barger wrote:

> On Wed, Oct 26, 2016 at 6:30 PM, Jörg Schaible <
> [hidden email]> wrote:
>
>>
>> The reactor of Maven does not consider plugins itself or dependencies to
>> plugins for its build order (by design). To support something like this,
>> you
>> will have to produce a released artifact first.
>
>
> ​In that case I guess following tutorial has a bug:
> https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html


No, it uses a released version as dependency. You're currently using a
SNAPSHOT version that is part of the same reactor and should be build first
(apart from the fact that the dependencies of a plugin are resolved at a
completely different stage).

When you've built the subproject once (i.e. you have such a SNAPSHOT version
in your local repo), the situation is slightly different, but you will
probably not using the correct SNAPSHOT version.

Cheers,
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Jörg Schaible
In reply to this post by Artem Barger
Artem Barger wrote:

> On Wed, Oct 26, 2016 at 7:14 PM, Gilles <[hidden email]>
> wrote:
>
>> could not find "commons-rng-build-tools" (posted a question in maven ML
>>>> list).
>>>>
>>>
>>> The reactor of Maven does not consider plugins itself or dependencies to
>>> plugins for its build order (by design). To support something like this,
>>> you
>>> will have to produce a released artifact first.
>>>
>>
>> As maven-ignoramus, I do not follow.
>> Does it mean that Artem's proposal is not feasible (according to
>> Commons policy)?
>
>
> ​If only we could have build-tools as stand-alone component, that might
> solve
> all the problems.​ :/

We have commons-build in proper. Don't know what it is used for, but it
looks like an old Maven 1 project ;-)

Cheers,
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Artem Barger
In reply to this post by Gilles Sadowski
On Wed, Oct 26, 2016 at 7:42 PM, Gilles <[hidden email]>
wrote:

>
> But the modules link are still dead.
> [E.g. there is no "apidocs".]


​Added aggregation of javadocs for parent project.​

Best regards,
                      Artem Barger.
Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

sebb-2-2
In reply to this post by Jörg Schaible
On 26 October 2016 at 17:50, Jörg Schaible <[hidden email]> wrote:

> Artem Barger wrote:
>
>> On Wed, Oct 26, 2016 at 7:14 PM, Gilles <[hidden email]>
>> wrote:
>>
>>> could not find "commons-rng-build-tools" (posted a question in maven ML
>>>>> list).
>>>>>
>>>>
>>>> The reactor of Maven does not consider plugins itself or dependencies to
>>>> plugins for its build order (by design). To support something like this,
>>>> you
>>>> will have to produce a released artifact first.
>>>>
>>>
>>> As maven-ignoramus, I do not follow.
>>> Does it mean that Artem's proposal is not feasible (according to
>>> Commons policy)?
>>
>>
>> If only we could have build-tools as stand-alone component, that might
>> solve
>> all the problems. :/
>
> We have commons-build in proper. Don't know what it is used for, but it
> looks like an old Maven 1 project ;-)

Commons-build is current.
It is even documented. See:

http://commons.apache.org/proper/commons-build-plugin/index.html

> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [ALL] Maven plugins common configuration.

Jörg Schaible
Hi Sebb,

sebb wrote:

> On 26 October 2016 at 17:50, Jörg Schaible <[hidden email]> wrote:

[snip]

>> We have commons-build in proper. Don't know what it is used for, but it
>> looks like an old Maven 1 project ;-)
>
> Commons-build is current.
> It is even documented. See:
>
> http://commons.apache.org/proper/commons-build-plugin/index.html

you should have a look at subversion. What you desribe is commons-build-
plugin.

Cheers,
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12