You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dan Tran <da...@gmail.com> on 2016/05/20 05:16:04 UTC
maven-jar-plugin-3.0.0 compatiblity/regression?
Hi
My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
throws this error
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
(project-jar-for-docker) on project xxx: You have to use a classifier
to attach supplemental artifacts to the project instead of replacing
them. -> [Help 1]
This is a valid use case where I can have mutiple artifact extensions
without the need to use classifiers
The release notes of jar plugin 3.0.0 also not mentioned about this
I hope this is not intentional
My appology, i should have tested the during its voting period
Thanks
-Dan
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks a lot!
will wait for the updated version :)
not sure how plugin in eclipse can be updated with snapshot version :(
On Mon, May 23, 2016 at 11:44 AM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> Hi Maxim,
>
> I've already created an issue for m2e:
>
> https://github.com/tesla/m2eclipse-mavenarchiver/issues/8
>
> Kind regards
> Karl Heinz Marbaise
>
> On 5/23/16 5:54 AM, Maxim Solodovnik wrote:
>
>> Hello Karl,
>>
>> do I need to create JIRA issue? or maybe you can point me to the correct
>> tracker I can file issue against m2e?
>>
>> On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise <kh...@gmx.de>
>> wrote:
>>
>> Hi,
>>>
>>>
>>> On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
>>>
>>> I got following errors in eclipse:
>>>>
>>>>
>>>>
>>>> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
>>>> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
>>>> /openmeetings-core line 1 Maven Configuration Problem
>>>>
>>>> command line build works as expected
>>>>
>>>>
>>> This is a problem in M2E ...
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>>
>>>> On Fri, May 20, 2016 at 11:16 AM, Dan Tran <da...@gmail.com> wrote:
>>>>
>>>> Hi
>>>>
>>>>>
>>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>>>> throws this error
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>>>> to attach supplemental artifacts to the project instead of replacing
>>>>> them. -> [Help 1]
>>>>>
>>>>>
>>>>> This is a valid use case where I can have mutiple artifact extensions
>>>>> without the need to use classifiers
>>>>>
>>>>>
>>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>>
>>>>>
>>>>> I hope this is not intentional
>>>>>
>>>>>
>>>>> My appology, i should have tested the during its voting period
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> -Dan
>>>>>
>>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
WBR
Maxim aka solomax
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Maxim,
I've already created an issue for m2e:
https://github.com/tesla/m2eclipse-mavenarchiver/issues/8
Kind regards
Karl Heinz Marbaise
On 5/23/16 5:54 AM, Maxim Solodovnik wrote:
> Hello Karl,
>
> do I need to create JIRA issue? or maybe you can point me to the correct
> tracker I can file issue against m2e?
>
> On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise <kh...@gmx.de>
> wrote:
>
>> Hi,
>>
>>
>> On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
>>
>>> I got following errors in eclipse:
>>>
>>>
>>> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
>>> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
>>> /openmeetings-core line 1 Maven Configuration Problem
>>>
>>> command line build works as expected
>>>
>>
>> This is a problem in M2E ...
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>>>
>>> On Fri, May 20, 2016 at 11:16 AM, Dan Tran <da...@gmail.com> wrote:
>>>
>>> Hi
>>>>
>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>>> throws this error
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>>> to attach supplemental artifacts to the project instead of replacing
>>>> them. -> [Help 1]
>>>>
>>>>
>>>> This is a valid use case where I can have mutiple artifact extensions
>>>> without the need to use classifiers
>>>>
>>>>
>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>
>>>>
>>>> I hope this is not intentional
>>>>
>>>>
>>>> My appology, i should have tested the during its voting period
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>> -Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello Karl,
do I need to create JIRA issue? or maybe you can point me to the correct
tracker I can file issue against m2e?
On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> Hi,
>
>
> On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
>
>> I got following errors in eclipse:
>>
>>
>> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
>> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
>> /openmeetings-core line 1 Maven Configuration Problem
>>
>> command line build works as expected
>>
>
> This is a problem in M2E ...
>
> Kind regards
> Karl Heinz Marbaise
>
>>
>> On Fri, May 20, 2016 at 11:16 AM, Dan Tran <da...@gmail.com> wrote:
>>
>> Hi
>>>
>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>> throws this error
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>> to attach supplemental artifacts to the project instead of replacing
>>> them. -> [Help 1]
>>>
>>>
>>> This is a valid use case where I can have mutiple artifact extensions
>>> without the need to use classifiers
>>>
>>>
>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>
>>>
>>> I hope this is not intentional
>>>
>>>
>>> My appology, i should have tested the during its voting period
>>>
>>>
>>> Thanks
>>>
>>>
>>> -Dan
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
WBR
Maxim aka solomax
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
On 5/20/16 7:20 AM, Maxim Solodovnik wrote:
> I got following errors in eclipse:
>
> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
> /openmeetings-core line 1 Maven Configuration Problem
>
> command line build works as expected
This is a problem in M2E ...
Kind regards
Karl Heinz Marbaise
>
> On Fri, May 20, 2016 at 11:16 AM, Dan Tran <da...@gmail.com> wrote:
>
>> Hi
>>
>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>> throws this error
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>> (project-jar-for-docker) on project xxx: You have to use a classifier
>> to attach supplemental artifacts to the project instead of replacing
>> them. -> [Help 1]
>>
>>
>> This is a valid use case where I can have mutiple artifact extensions
>> without the need to use classifiers
>>
>>
>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>
>>
>> I hope this is not intentional
>>
>>
>> My appology, i should have tested the during its voting period
>>
>>
>> Thanks
>>
>>
>> -Dan
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Maxim Solodovnik <so...@gmail.com>.
I got following errors in eclipse:
org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject,
org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml
/openmeetings-core line 1 Maven Configuration Problem
command line build works as expected
On Fri, May 20, 2016 at 11:16 AM, Dan Tran <da...@gmail.com> wrote:
> Hi
>
> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
> (project-jar-for-docker) on project xxx: You have to use a classifier
> to attach supplemental artifacts to the project instead of replacing
> them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple artifact extensions
> without the need to use classifiers
>
>
> The release notes of jar plugin 3.0.0 also not mentioned about this
>
>
> I hope this is not intentional
>
>
> My appology, i should have tested the during its voting period
>
>
> Thanks
>
>
> -Dan
>
--
WBR
Maxim aka solomax
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by ec...@zusammenkunft.net.
Hello,
It might be a possible usecase to differentiate by extension, but if you want to follow the pure maven model just use an classifier which is used in the repo.
Gruss
Bernd
--
http://bernd.eckenfels.net
-----Original Message-----
From: Dan Tran <da...@gmail.com>
To: Maven Users List <us...@maven.apache.org>
Sent: Fr., 20 Mai 2016 22:05
Subject: Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Robert,
According to the jar plugin source outputDirectory is not read only. that
is why I can change the default value.
here is my use case
- Start out of jar module with a profile to create the RPM
- In the profile, use assembler-maven-plugin to create staging
distribution
- since the primary jar file is not in my staging, I need to invoke jar
plugin explicitly to create another jar. This makes jar plugin thinks it
has 2 primary artifacts and bails out
- Use RPM to package the staging
This is a valid use case right?
Thanks
-Dan
On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rf...@apache.org>
wrote:
> Dan,
>
> outputDirectory has become a readonly parameter.
> The reason is that you can set it with <project><build><directory>. Does
> that work for you?
>
> thanks,
> Robert
>
>
> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <kh...@gmx.de>
> wrote:
>
> Hi Dan,
>>
>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>
>>> Hi
>>>
>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>> throws this error
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>> to attach supplemental artifacts to the project instead of replacing
>>> them. -> [Help 1]
>>>
>>>
>>> This is a valid use case where I can have mutiple artifact extensions
>>> without the need to use classifiers
>>>
>>
>> Can you create an example project for this? So i can create an JIRA for
>> that or you can create the jira with that...sounds like an edge case which
>> i didn't thought of ?...
>>
>> So you are replacing the main artifact but with different extensions ?
>>
>> Hm.. ?
>>
>>
>>>
>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>
>>
>> https://issues.apache.org/jira/browse/MJAR-198
>>
>>
>>
>>>
>>> I hope this is not intentional
>>>
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> ---------------------------------------------------------------------
>> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Robert Scholte <rf...@apache.org>.
Awesome, case closed :)
On Sun, 22 May 2016 00:05:49 +0200, Dan Tran <da...@gmail.com> wrote:
> I just checked appassembler source, this plugin does populate project
> artifact if it is found. This mean i just need to configure the
> appassembler to run at package phase. It works
>
> -D
>
> On Sat, May 21, 2016 at 12:40 PM, Dan Tran <da...@gmail.com> wrote:
>
>> that would be awesome. appassembler-m-p should copy the primary jar to
>> its
>> lib directory. However, this also means it must run at package phase in
>> order to see the jar-plugin output
>>
>> -D
>>
>> On Sat, May 21, 2016 at 1:39 AM, Robert Scholte <rf...@apache.org>
>> wrote:
>>
>>> Hi Dan,
>>>
>>> So if I've correct the appassemble-maven-plugin assumes all jars are
>>> already put in the /lib directory by another plugin. I think it is more
>>> correct to let the plugin pull its libraries to this folder instead.
>>>
>>> WDYT?
>>> Robert
>>>
>>>
>>>
>>> On Fri, 20 May 2016 22:26:45 +0200, Dan Tran <da...@gmail.com> wrote:
>>>
>>> I meant appassemble-maven-plugin.
>>>>
>>>> very likely the error is from the fix of
>>>> https://issues.apache.org/jira/browse/MJAR-198
>>>>
>>>> For now, I will need to use antrun to copy the local primary jar to
>>>> the
>>>> place I need. Maybe, appassemble should do this for me
>>>>
>>>>
>>>> btw, if have RPM module but does invocation of 2 jar goals. Would that
>>>> cause an issue?
>>>>
>>>> -D
>>>>
>>>> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise
>>>> <kh...@gmx.de>
>>>> wrote:
>>>>
>>>> Hi Dan,
>>>>> On 5/20/16 10:04 PM, Dan Tran wrote:
>>>>>
>>>>> Hi Robert,
>>>>>>
>>>>>> According to the jar plugin source outputDirectory is not read
>>>>>> only.
>>>>>> that
>>>>>> is why I can change the default value.
>>>>>>
>>>>>> here is my use case
>>>>>>
>>>>>> - Start out of jar module with a profile to create the RPM
>>>>>> - In the profile, use assembler-maven-plugin to create staging
>>>>>> distribution
>>>>>>
>>>>>>
>>>>> assembly-maven-plugin? Do you mean maven-assembly-plugin ?
>>>>>
>>>>>
>>>>> - since the primary jar file is not in my staging, I need to invoke
>>>>> jar
>>>>>
>>>>>> plugin explicitly to create another jar. This makes jar plugin
>>>>>> thinks
>>>>>> it
>>>>>> has 2 primary artifacts and bails out
>>>>>> - Use RPM to package the staging
>>>>>>
>>>>>>
>>>>> As there has been already a call which sets the main artifact
>>>>> (primary
>>>>> artiact) of the project and maven-jar-plugin regrets to set the main
>>>>> artifact if it is already been set....
>>>>>
>>>>> That sounds like you build needs to be cleaned up...to prevent
>>>>> setting
>>>>> the
>>>>> main artifact twice ? Can we see that build somewhere ? Or can you
>>>>> send
>>>>> me
>>>>> a log file of it? (privately?)
>>>>>
>>>>>
>>>>>
>>>>> This is a valid use case right?
>>>>>>
>>>>>>
>>>>> Hm..we will see....
>>>>>
>>>>>
>>>>> Kind regards
>>>>> Karl Heinz
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> -Dan
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte
>>>>>> <rfscholte@apache.org
>>>>>> >
>>>>>> wrote:
>>>>>>
>>>>>> Dan,
>>>>>>
>>>>>>>
>>>>>>> outputDirectory has become a readonly parameter.
>>>>>>> The reason is that you can set it with <project><build><directory>.
>>>>>>> Does
>>>>>>> that work for you?
>>>>>>>
>>>>>>> thanks,
>>>>>>> Robert
>>>>>>>
>>>>>>>
>>>>>>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <
>>>>>>> khmarbaise@gmx.de>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Dan,
>>>>>>>
>>>>>>>
>>>>>>>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>>>
>>>>>>>>> My jar project can also create RPM via
>>>>>>>>> rpm-maven-plugin:attach-rpm
>>>>>>>>> now
>>>>>>>>> throws this error
>>>>>>>>>
>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>>>>>> (project-jar-for-docker) on project xxx: You have to use a
>>>>>>>>> classifier
>>>>>>>>> to attach supplemental artifacts to the project instead of
>>>>>>>>> replacing
>>>>>>>>> them. -> [Help 1]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> This is a valid use case where I can have mutiple artifact
>>>>>>>>> extensions
>>>>>>>>> without the need to use classifiers
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Can you create an example project for this? So i can create an
>>>>>>>>> JIRA
>>>>>>>> for
>>>>>>>> that or you can create the jira with that...sounds like an edge
>>>>>>>> case
>>>>>>>> which
>>>>>>>> i didn't thought of ?...
>>>>>>>>
>>>>>>>> So you are replacing the main artifact but with different
>>>>>>>> extensions
>>>>>>>> ?
>>>>>>>>
>>>>>>>> Hm.. ?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The release notes of jar plugin 3.0.0 also not mentioned about
>>>>>>>> this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/browse/MJAR-198
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I hope this is not intentional
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Kind regards
>>>>>>>> Karl Heinz Marbaise
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Dan Tran <da...@gmail.com>.
I just checked appassembler source, this plugin does populate project
artifact if it is found. This mean i just need to configure the
appassembler to run at package phase. It works
-D
On Sat, May 21, 2016 at 12:40 PM, Dan Tran <da...@gmail.com> wrote:
> that would be awesome. appassembler-m-p should copy the primary jar to its
> lib directory. However, this also means it must run at package phase in
> order to see the jar-plugin output
>
> -D
>
> On Sat, May 21, 2016 at 1:39 AM, Robert Scholte <rf...@apache.org>
> wrote:
>
>> Hi Dan,
>>
>> So if I've correct the appassemble-maven-plugin assumes all jars are
>> already put in the /lib directory by another plugin. I think it is more
>> correct to let the plugin pull its libraries to this folder instead.
>>
>> WDYT?
>> Robert
>>
>>
>>
>> On Fri, 20 May 2016 22:26:45 +0200, Dan Tran <da...@gmail.com> wrote:
>>
>> I meant appassemble-maven-plugin.
>>>
>>> very likely the error is from the fix of
>>> https://issues.apache.org/jira/browse/MJAR-198
>>>
>>> For now, I will need to use antrun to copy the local primary jar to the
>>> place I need. Maybe, appassemble should do this for me
>>>
>>>
>>> btw, if have RPM module but does invocation of 2 jar goals. Would that
>>> cause an issue?
>>>
>>> -D
>>>
>>> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise <kh...@gmx.de>
>>> wrote:
>>>
>>> Hi Dan,
>>>> On 5/20/16 10:04 PM, Dan Tran wrote:
>>>>
>>>> Hi Robert,
>>>>>
>>>>> According to the jar plugin source outputDirectory is not read only.
>>>>> that
>>>>> is why I can change the default value.
>>>>>
>>>>> here is my use case
>>>>>
>>>>> - Start out of jar module with a profile to create the RPM
>>>>> - In the profile, use assembler-maven-plugin to create staging
>>>>> distribution
>>>>>
>>>>>
>>>> assembly-maven-plugin? Do you mean maven-assembly-plugin ?
>>>>
>>>>
>>>> - since the primary jar file is not in my staging, I need to invoke
>>>> jar
>>>>
>>>>> plugin explicitly to create another jar. This makes jar plugin thinks
>>>>> it
>>>>> has 2 primary artifacts and bails out
>>>>> - Use RPM to package the staging
>>>>>
>>>>>
>>>> As there has been already a call which sets the main artifact (primary
>>>> artiact) of the project and maven-jar-plugin regrets to set the main
>>>> artifact if it is already been set....
>>>>
>>>> That sounds like you build needs to be cleaned up...to prevent setting
>>>> the
>>>> main artifact twice ? Can we see that build somewhere ? Or can you send
>>>> me
>>>> a log file of it? (privately?)
>>>>
>>>>
>>>>
>>>> This is a valid use case right?
>>>>>
>>>>>
>>>> Hm..we will see....
>>>>
>>>>
>>>> Kind regards
>>>> Karl Heinz
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Thanks
>>>>>
>>>>> -Dan
>>>>>
>>>>>
>>>>>
>>>>> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rfscholte@apache.org
>>>>> >
>>>>> wrote:
>>>>>
>>>>> Dan,
>>>>>
>>>>>>
>>>>>> outputDirectory has become a readonly parameter.
>>>>>> The reason is that you can set it with <project><build><directory>.
>>>>>> Does
>>>>>> that work for you?
>>>>>>
>>>>>> thanks,
>>>>>> Robert
>>>>>>
>>>>>>
>>>>>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <
>>>>>> khmarbaise@gmx.de>
>>>>>> wrote:
>>>>>>
>>>>>> Hi Dan,
>>>>>>
>>>>>>
>>>>>>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>>>
>>>>>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm
>>>>>>>> now
>>>>>>>> throws this error
>>>>>>>>
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>>>>> (project-jar-for-docker) on project xxx: You have to use a
>>>>>>>> classifier
>>>>>>>> to attach supplemental artifacts to the project instead of replacing
>>>>>>>> them. -> [Help 1]
>>>>>>>>
>>>>>>>>
>>>>>>>> This is a valid use case where I can have mutiple artifact
>>>>>>>> extensions
>>>>>>>> without the need to use classifiers
>>>>>>>>
>>>>>>>>
>>>>>>>> Can you create an example project for this? So i can create an JIRA
>>>>>>> for
>>>>>>> that or you can create the jira with that...sounds like an edge case
>>>>>>> which
>>>>>>> i didn't thought of ?...
>>>>>>>
>>>>>>> So you are replacing the main artifact but with different extensions
>>>>>>> ?
>>>>>>>
>>>>>>> Hm.. ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>>>>>
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/MJAR-198
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I hope this is not intentional
>>>>>>>>
>>>>>>>>
>>>>>>>> Kind regards
>>>>>>> Karl Heinz Marbaise
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Dan Tran <da...@gmail.com>.
that would be awesome. appassembler-m-p should copy the primary jar to its
lib directory. However, this also means it must run at package phase in
order to see the jar-plugin output
-D
On Sat, May 21, 2016 at 1:39 AM, Robert Scholte <rf...@apache.org>
wrote:
> Hi Dan,
>
> So if I've correct the appassemble-maven-plugin assumes all jars are
> already put in the /lib directory by another plugin. I think it is more
> correct to let the plugin pull its libraries to this folder instead.
>
> WDYT?
> Robert
>
>
>
> On Fri, 20 May 2016 22:26:45 +0200, Dan Tran <da...@gmail.com> wrote:
>
> I meant appassemble-maven-plugin.
>>
>> very likely the error is from the fix of
>> https://issues.apache.org/jira/browse/MJAR-198
>>
>> For now, I will need to use antrun to copy the local primary jar to the
>> place I need. Maybe, appassemble should do this for me
>>
>>
>> btw, if have RPM module but does invocation of 2 jar goals. Would that
>> cause an issue?
>>
>> -D
>>
>> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise <kh...@gmx.de>
>> wrote:
>>
>> Hi Dan,
>>> On 5/20/16 10:04 PM, Dan Tran wrote:
>>>
>>> Hi Robert,
>>>>
>>>> According to the jar plugin source outputDirectory is not read only.
>>>> that
>>>> is why I can change the default value.
>>>>
>>>> here is my use case
>>>>
>>>> - Start out of jar module with a profile to create the RPM
>>>> - In the profile, use assembler-maven-plugin to create staging
>>>> distribution
>>>>
>>>>
>>> assembly-maven-plugin? Do you mean maven-assembly-plugin ?
>>>
>>>
>>> - since the primary jar file is not in my staging, I need to invoke jar
>>>
>>>> plugin explicitly to create another jar. This makes jar plugin thinks
>>>> it
>>>> has 2 primary artifacts and bails out
>>>> - Use RPM to package the staging
>>>>
>>>>
>>> As there has been already a call which sets the main artifact (primary
>>> artiact) of the project and maven-jar-plugin regrets to set the main
>>> artifact if it is already been set....
>>>
>>> That sounds like you build needs to be cleaned up...to prevent setting
>>> the
>>> main artifact twice ? Can we see that build somewhere ? Or can you send
>>> me
>>> a log file of it? (privately?)
>>>
>>>
>>>
>>> This is a valid use case right?
>>>>
>>>>
>>> Hm..we will see....
>>>
>>>
>>> Kind regards
>>> Karl Heinz
>>>
>>>
>>>
>>>
>>>
>>>> Thanks
>>>>
>>>> -Dan
>>>>
>>>>
>>>>
>>>> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rf...@apache.org>
>>>> wrote:
>>>>
>>>> Dan,
>>>>
>>>>>
>>>>> outputDirectory has become a readonly parameter.
>>>>> The reason is that you can set it with <project><build><directory>.
>>>>> Does
>>>>> that work for you?
>>>>>
>>>>> thanks,
>>>>> Robert
>>>>>
>>>>>
>>>>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <
>>>>> khmarbaise@gmx.de>
>>>>> wrote:
>>>>>
>>>>> Hi Dan,
>>>>>
>>>>>
>>>>>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>>>
>>>>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm
>>>>>>> now
>>>>>>> throws this error
>>>>>>>
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>>>>>> to attach supplemental artifacts to the project instead of replacing
>>>>>>> them. -> [Help 1]
>>>>>>>
>>>>>>>
>>>>>>> This is a valid use case where I can have mutiple artifact extensions
>>>>>>> without the need to use classifiers
>>>>>>>
>>>>>>>
>>>>>>> Can you create an example project for this? So i can create an JIRA
>>>>>> for
>>>>>> that or you can create the jira with that...sounds like an edge case
>>>>>> which
>>>>>> i didn't thought of ?...
>>>>>>
>>>>>> So you are replacing the main artifact but with different extensions ?
>>>>>>
>>>>>> Hm.. ?
>>>>>>
>>>>>>
>>>>>>
>>>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>>>>
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/MJAR-198
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I hope this is not intentional
>>>>>>>
>>>>>>>
>>>>>>> Kind regards
>>>>>> Karl Heinz Marbaise
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Robert Scholte <rf...@apache.org>.
Hi Dan,
So if I've correct the appassemble-maven-plugin assumes all jars are
already put in the /lib directory by another plugin. I think it is more
correct to let the plugin pull its libraries to this folder instead.
WDYT?
Robert
On Fri, 20 May 2016 22:26:45 +0200, Dan Tran <da...@gmail.com> wrote:
> I meant appassemble-maven-plugin.
>
> very likely the error is from the fix of
> https://issues.apache.org/jira/browse/MJAR-198
>
> For now, I will need to use antrun to copy the local primary jar to the
> place I need. Maybe, appassemble should do this for me
>
>
> btw, if have RPM module but does invocation of 2 jar goals. Would that
> cause an issue?
>
> -D
>
> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise <kh...@gmx.de>
> wrote:
>
>> Hi Dan,
>> On 5/20/16 10:04 PM, Dan Tran wrote:
>>
>>> Hi Robert,
>>>
>>> According to the jar plugin source outputDirectory is not read only.
>>> that
>>> is why I can change the default value.
>>>
>>> here is my use case
>>>
>>> - Start out of jar module with a profile to create the RPM
>>> - In the profile, use assembler-maven-plugin to create staging
>>> distribution
>>>
>>
>> assembly-maven-plugin? Do you mean maven-assembly-plugin ?
>>
>>
>> - since the primary jar file is not in my staging, I need to invoke
>> jar
>>> plugin explicitly to create another jar. This makes jar plugin thinks
>>> it
>>> has 2 primary artifacts and bails out
>>> - Use RPM to package the staging
>>>
>>
>> As there has been already a call which sets the main artifact (primary
>> artiact) of the project and maven-jar-plugin regrets to set the main
>> artifact if it is already been set....
>>
>> That sounds like you build needs to be cleaned up...to prevent setting
>> the
>> main artifact twice ? Can we see that build somewhere ? Or can you send
>> me
>> a log file of it? (privately?)
>>
>>
>>
>>> This is a valid use case right?
>>>
>>
>> Hm..we will see....
>>
>>
>> Kind regards
>> Karl Heinz
>>
>>
>>
>>
>>>
>>> Thanks
>>>
>>> -Dan
>>>
>>>
>>>
>>> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rf...@apache.org>
>>> wrote:
>>>
>>> Dan,
>>>>
>>>> outputDirectory has become a readonly parameter.
>>>> The reason is that you can set it with <project><build><directory>.
>>>> Does
>>>> that work for you?
>>>>
>>>> thanks,
>>>> Robert
>>>>
>>>>
>>>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <
>>>> khmarbaise@gmx.de>
>>>> wrote:
>>>>
>>>> Hi Dan,
>>>>
>>>>>
>>>>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>>>>
>>>>> Hi
>>>>>>
>>>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm
>>>>>> now
>>>>>> throws this error
>>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>>> (project-jar-for-docker) on project xxx: You have to use a
>>>>>> classifier
>>>>>> to attach supplemental artifacts to the project instead of replacing
>>>>>> them. -> [Help 1]
>>>>>>
>>>>>>
>>>>>> This is a valid use case where I can have mutiple artifact
>>>>>> extensions
>>>>>> without the need to use classifiers
>>>>>>
>>>>>>
>>>>> Can you create an example project for this? So i can create an JIRA
>>>>> for
>>>>> that or you can create the jira with that...sounds like an edge case
>>>>> which
>>>>> i didn't thought of ?...
>>>>>
>>>>> So you are replacing the main artifact but with different extensions
>>>>> ?
>>>>>
>>>>> Hm.. ?
>>>>>
>>>>>
>>>>>
>>>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>>>
>>>>>>
>>>>> https://issues.apache.org/jira/browse/MJAR-198
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> I hope this is not intentional
>>>>>>
>>>>>>
>>>>> Kind regards
>>>>> Karl Heinz Marbaise
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>
>> ---------------------------------------------------------------------
>> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Dan,
On 5/20/16 10:26 PM, Dan Tran wrote:
> I meant appassemble-maven-plugin.
Ah sorry could have imagined that myself...
>
> very likely the error is from the fix of
> https://issues.apache.org/jira/browse/MJAR-198
>
> For now, I will need to use antrun to copy the local primary jar to the
> place I need. Maybe, appassemble should do this for me
>
>
> btw, if have RPM module but does invocation of 2 jar goals. Would that
> cause an issue?
If you run the jar goals without defining a classifier than yes...I
assume you used the jar goal ?
That's not a issue it prevents bad things which means simply replacing
primary artifact without knowing it...
>
> -D
>
> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise <khmarbaise@gmx.de
> <ma...@gmx.de>> wrote:
>
> Hi Dan,
> On 5/20/16 10:04 PM, Dan Tran wrote:
>
> Hi Robert,
>
> According to the jar plugin source outputDirectory is not read
> only. that
> is why I can change the default value.
>
> here is my use case
>
> - Start out of jar module with a profile to create the RPM
> - In the profile, use assembler-maven-plugin to create staging
> distribution
>
>
> assembly-maven-plugin? Do you mean maven-assembly-plugin ?
>
>
> - since the primary jar file is not in my staging, I need to
> invoke jar
> plugin explicitly to create another jar. This makes jar plugin
> thinks it
> has 2 primary artifacts and bails out
> - Use RPM to package the staging
>
>
> As there has been already a call which sets the main artifact
> (primary artiact) of the project and maven-jar-plugin regrets to set
> the main artifact if it is already been set....
>
> That sounds like you build needs to be cleaned up...to prevent
> setting the main artifact twice ? Can we see that build somewhere ?
> Or can you send me a log file of it? (privately?)
>
>
>
> This is a valid use case right?
>
>
> Hm..we will see....
>
>
> Kind regards
> Karl Heinz
>
>
>
>
>
> Thanks
>
> -Dan
>
>
>
> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte
> <rfscholte@apache.org <ma...@apache.org>>
> wrote:
>
> Dan,
>
> outputDirectory has become a readonly parameter.
> The reason is that you can set it with
> <project><build><directory>. Does
> that work for you?
>
> thanks,
> Robert
>
>
> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise
> <khmarbaise@gmx.de <ma...@gmx.de>>
> wrote:
>
> Hi Dan,
>
>
> On 5/20/16 7:16 AM, Dan Tran wrote:
>
> Hi
>
> My jar project can also create RPM via
> rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
> (project-jar-for-docker) on project xxx: You have to
> use a classifier
> to attach supplemental artifacts to the project
> instead of replacing
> them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple
> artifact extensions
> without the need to use classifiers
>
>
> Can you create an example project for this? So i can
> create an JIRA for
> that or you can create the jira with that...sounds like
> an edge case which
> i didn't thought of ?...
>
> So you are replacing the main artifact but with
> different extensions ?
>
> Hm.. ?
>
> >
> The release notes of jar plugin 3.0.0 also not
> mentioned about this
>
>
> https://issues.apache.org/jira/browse/MJAR-198
>
>
>
>
> I hope this is not intentional
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Dan Tran <da...@gmail.com>.
I meant appassemble-maven-plugin.
very likely the error is from the fix of
https://issues.apache.org/jira/browse/MJAR-198
For now, I will need to use antrun to copy the local primary jar to the
place I need. Maybe, appassemble should do this for me
btw, if have RPM module but does invocation of 2 jar goals. Would that
cause an issue?
-D
On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise <kh...@gmx.de>
wrote:
> Hi Dan,
> On 5/20/16 10:04 PM, Dan Tran wrote:
>
>> Hi Robert,
>>
>> According to the jar plugin source outputDirectory is not read only.
>> that
>> is why I can change the default value.
>>
>> here is my use case
>>
>> - Start out of jar module with a profile to create the RPM
>> - In the profile, use assembler-maven-plugin to create staging
>> distribution
>>
>
> assembly-maven-plugin? Do you mean maven-assembly-plugin ?
>
>
> - since the primary jar file is not in my staging, I need to invoke jar
>> plugin explicitly to create another jar. This makes jar plugin thinks it
>> has 2 primary artifacts and bails out
>> - Use RPM to package the staging
>>
>
> As there has been already a call which sets the main artifact (primary
> artiact) of the project and maven-jar-plugin regrets to set the main
> artifact if it is already been set....
>
> That sounds like you build needs to be cleaned up...to prevent setting the
> main artifact twice ? Can we see that build somewhere ? Or can you send me
> a log file of it? (privately?)
>
>
>
>> This is a valid use case right?
>>
>
> Hm..we will see....
>
>
> Kind regards
> Karl Heinz
>
>
>
>
>>
>> Thanks
>>
>> -Dan
>>
>>
>>
>> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rf...@apache.org>
>> wrote:
>>
>> Dan,
>>>
>>> outputDirectory has become a readonly parameter.
>>> The reason is that you can set it with <project><build><directory>. Does
>>> that work for you?
>>>
>>> thanks,
>>> Robert
>>>
>>>
>>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <
>>> khmarbaise@gmx.de>
>>> wrote:
>>>
>>> Hi Dan,
>>>
>>>>
>>>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>>>
>>>> Hi
>>>>>
>>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>>>> throws this error
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>>>> to attach supplemental artifacts to the project instead of replacing
>>>>> them. -> [Help 1]
>>>>>
>>>>>
>>>>> This is a valid use case where I can have mutiple artifact extensions
>>>>> without the need to use classifiers
>>>>>
>>>>>
>>>> Can you create an example project for this? So i can create an JIRA for
>>>> that or you can create the jira with that...sounds like an edge case
>>>> which
>>>> i didn't thought of ?...
>>>>
>>>> So you are replacing the main artifact but with different extensions ?
>>>>
>>>> Hm.. ?
>>>>
>>>>
>>>>
>>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>>
>>>>>
>>>> https://issues.apache.org/jira/browse/MJAR-198
>>>>
>>>>
>>>>
>>>>
>>>>> I hope this is not intentional
>>>>>
>>>>>
>>>> Kind regards
>>>> Karl Heinz Marbaise
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Dan,
On 5/20/16 10:04 PM, Dan Tran wrote:
> Hi Robert,
>
> According to the jar plugin source outputDirectory is not read only. that
> is why I can change the default value.
>
> here is my use case
>
> - Start out of jar module with a profile to create the RPM
> - In the profile, use assembler-maven-plugin to create staging
> distribution
assembly-maven-plugin? Do you mean maven-assembly-plugin ?
> - since the primary jar file is not in my staging, I need to invoke jar
> plugin explicitly to create another jar. This makes jar plugin thinks it
> has 2 primary artifacts and bails out
> - Use RPM to package the staging
As there has been already a call which sets the main artifact (primary
artiact) of the project and maven-jar-plugin regrets to set the main
artifact if it is already been set....
That sounds like you build needs to be cleaned up...to prevent setting
the main artifact twice ? Can we see that build somewhere ? Or can you
send me a log file of it? (privately?)
>
> This is a valid use case right?
Hm..we will see....
Kind regards
Karl Heinz
>
>
> Thanks
>
> -Dan
>
>
>
> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rf...@apache.org>
> wrote:
>
>> Dan,
>>
>> outputDirectory has become a readonly parameter.
>> The reason is that you can set it with <project><build><directory>. Does
>> that work for you?
>>
>> thanks,
>> Robert
>>
>>
>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <kh...@gmx.de>
>> wrote:
>>
>> Hi Dan,
>>>
>>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>>
>>>> Hi
>>>>
>>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>>> throws this error
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>>> to attach supplemental artifacts to the project instead of replacing
>>>> them. -> [Help 1]
>>>>
>>>>
>>>> This is a valid use case where I can have mutiple artifact extensions
>>>> without the need to use classifiers
>>>>
>>>
>>> Can you create an example project for this? So i can create an JIRA for
>>> that or you can create the jira with that...sounds like an edge case which
>>> i didn't thought of ?...
>>>
>>> So you are replacing the main artifact but with different extensions ?
>>>
>>> Hm.. ?
>>>
>>>
>>>>
>>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>>
>>>
>>> https://issues.apache.org/jira/browse/MJAR-198
>>>
>>>
>>>
>>>>
>>>> I hope this is not intentional
>>>>
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Dan Tran <da...@gmail.com>.
Hi Robert,
According to the jar plugin source outputDirectory is not read only. that
is why I can change the default value.
here is my use case
- Start out of jar module with a profile to create the RPM
- In the profile, use assembler-maven-plugin to create staging
distribution
- since the primary jar file is not in my staging, I need to invoke jar
plugin explicitly to create another jar. This makes jar plugin thinks it
has 2 primary artifacts and bails out
- Use RPM to package the staging
This is a valid use case right?
Thanks
-Dan
On Fri, May 20, 2016 at 12:15 PM, Robert Scholte <rf...@apache.org>
wrote:
> Dan,
>
> outputDirectory has become a readonly parameter.
> The reason is that you can set it with <project><build><directory>. Does
> that work for you?
>
> thanks,
> Robert
>
>
> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise <kh...@gmx.de>
> wrote:
>
> Hi Dan,
>>
>> On 5/20/16 7:16 AM, Dan Tran wrote:
>>
>>> Hi
>>>
>>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>>> throws this error
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>>> (project-jar-for-docker) on project xxx: You have to use a classifier
>>> to attach supplemental artifacts to the project instead of replacing
>>> them. -> [Help 1]
>>>
>>>
>>> This is a valid use case where I can have mutiple artifact extensions
>>> without the need to use classifiers
>>>
>>
>> Can you create an example project for this? So i can create an JIRA for
>> that or you can create the jira with that...sounds like an edge case which
>> i didn't thought of ?...
>>
>> So you are replacing the main artifact but with different extensions ?
>>
>> Hm.. ?
>>
>>
>>>
>>> The release notes of jar plugin 3.0.0 also not mentioned about this
>>>
>>
>> https://issues.apache.org/jira/browse/MJAR-198
>>
>>
>>
>>>
>>> I hope this is not intentional
>>>
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> ---------------------------------------------------------------------
>> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Robert Scholte <rf...@apache.org>.
Dan,
outputDirectory has become a readonly parameter.
The reason is that you can set it with <project><build><directory>. Does
that work for you?
thanks,
Robert
On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise
<kh...@gmx.de> wrote:
> Hi Dan,
>
> On 5/20/16 7:16 AM, Dan Tran wrote:
>> Hi
>>
>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
>> throws this error
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
>> (project-jar-for-docker) on project xxx: You have to use a classifier
>> to attach supplemental artifacts to the project instead of replacing
>> them. -> [Help 1]
>>
>>
>> This is a valid use case where I can have mutiple artifact extensions
>> without the need to use classifiers
>
> Can you create an example project for this? So i can create an JIRA for
> that or you can create the jira with that...sounds like an edge case
> which i didn't thought of ?...
>
> So you are replacing the main artifact but with different extensions ?
>
> Hm.. ?
>
>>
>>
>> The release notes of jar plugin 3.0.0 also not mentioned about this
>
> https://issues.apache.org/jira/browse/MJAR-198
>
>
>>
>>
>> I hope this is not intentional
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> 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: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Dan,
On 5/20/16 7:16 AM, Dan Tran wrote:
> Hi
>
> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar
> (project-jar-for-docker) on project xxx: You have to use a classifier
> to attach supplemental artifacts to the project instead of replacing
> them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple artifact extensions
> without the need to use classifiers
Can you create an example project for this? So i can create an JIRA for
that or you can create the jira with that...sounds like an edge case
which i didn't thought of ?...
So you are replacing the main artifact but with different extensions ?
Hm.. ?
>
>
> The release notes of jar plugin 3.0.0 also not mentioned about this
https://issues.apache.org/jira/browse/MJAR-198
>
>
> I hope this is not intentional
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Posted by Dan Tran <da...@gmail.com>.
sorry about the noise, my pom also calls
<!-- add main jar to staging -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>project-jar-for-rpm</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<outputDirectory>${rpm.staging.directory}/lib</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
to push the main jar to another directory consumed by rpm-m-p, that
triggers this issue
Looks like I have to use antrun instead. Ouch!!
-Dan
On Thu, May 19, 2016 at 10:16 PM, Dan Tran <da...@gmail.com> wrote:
> Hi
>
> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers
>
>
> The release notes of jar plugin 3.0.0 also not mentioned about this
>
>
> I hope this is not intentional
>
>
> My appology, i should have tested the during its voting period
>
>
> Thanks
>
>
> -Dan
>
>
>
>