[OFFTOPIC] Games to Avoid
Maven Users, Avoid "Yoshi´s Woolly World" for Wii U. Due to this, I stopped pronouncing the POM acronym and started to use Yoshi's Pronunciation. https://www.youtube.com/watch?v=xLKeZOxhbZs#t=22 Cuter, but embarassing. Really, avoid this. -- -- Aldrin Leal, / http://about.me/aldrinleal
Re: [rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?
I think we may be able to remove the extra 'rpm' classifier
-D
On Tue, Dec 8, 2015 at 8:34 AM, Sverre Moe wrote:
> I have a similar problem with RPM archiving with our Nexus Maven
> Repository. I understand the reason for going the maven way for
> naming, but when we want to use Nexus as our Yum repository manager it
> should at least support naming the yum way.
>
> When I have several packages for one project, then maven rearranges
> the classifier to the end of the file and when there is no classifier
> it appends rpm to the end of the file name.
> ${project.artifactId}-${project-version}.noarch.rpm =>
> ${project.artifactId}-${project-version}.noarch-rpm.rpm
> ${project.artifactId}-devel-${project-version}.noarch.rpm =>
> ${project.artifactId}-${project-version}.noarch-devel.rpm
> ${project.artifactId}-jws-${project-version}.noarch.rpm =>
> ${project.artifactId}-${project-version}.noarch-jws.rpm
>
> I want to use Nexus as our RPM yum repository manager, but because of
> this renaming of the RPM artefacts I am reluctant. I would have gone
> for Artefactory if it didn't cost money for the RPM feature.
>
> 2015-12-07 22:05 GMT+01:00 Steve Cohen :
> > Aargh! Email formattting!
> >
> > org.apache.maven.plugins
> > maven-install-plugin
> > 2.5.2
> >
> >
> > install-rpm
> >
> > install-file
> >
> > install
> >
> >
> > ${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name
> }-${project.version}-${rpm.release}.noarch.rpm
> > ${project.groupId}
> > ${rpm.name}
> > ${project.version}-${rpm.release}
> > noarch
> > rpm
> >
> >
> >
> >
> >
> >
> >
> > On 12/07/2015 02:55 PM, Steve Cohen wrote:
> >>
> >> Actually, I found a way. If I am willing to let my "short name" become
> >> the archiveId, (and thus live with the rpms in a different location),
> >> the following is possible with the maven-install-plugin, after packaging
> >> with the rpm-maven-plugin:
> >>
> >>
> >>
> >> org.apache.maven.plugins
> >>
> >> maven-install-plugin
> >>
> >> 2.5.2
> >>
> >>
> >>
> >>
> >>
> >> install-rpm
> >>
> >>
> >>
> >> install-file
> >>
> >>
> >>
> >> install
> >>
> >>
> >>
> >>
> >> ${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name
> }-${project.version}-${rpm.release}.noarch.rpm
> >>
> >>
> >> ${project.groupId}
> >>
> >> ${rpm.name}
> >>
> >> ${project.version}-${rpm.release}
> >>
> >> noarch
> >>
> >> rpm
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 12/07/2015 01:54 PM, Karl Heinz Marbaise wrote:
> >>>
> >>> Hi Steve,
> >>>
> >>> simply answer to this: It is not possible...
> >>>
> >>> Long answer: Maven repositories dependending on an appropriate naming
> >>> schema to find artifacts / versions etc. If you change that the whole
> >>> system will not work at all..
> >>>
> >>> So the name which is stored within a maven repository can't be changed.
> >>>
> >>> Kind regards
> >>> Karl Heinz Marbaise
> >>>
> >>> On 12/7/15 7:44 PM, Steve Cohen wrote:
>
> Our organization has a convention for naming rpms. Typically, the rpm
> will have a shorter base name than the Maven project. There is also a
> convention around how releases are named. So we want a name
> like|${shortname}-${project.version}-${release}.noarch.rpm|.
>
> I want to build such rpms using the rpm-maven-plugin rather than older
> nmake technology.
>
> And this is easily accomplished using the plugin's parameters. The rpm
> generated in the target directory has the desired name.
>
> However, when|mvn install|installs this rpm into the maven repository,
> it insists on storing it the "maven
> way":|${project.artifactId}-${project.version}.rpm|
>
> I want the rpm stored in the standard maven repository directory using
> the name that is initially created on package.
>
> I also tried using the maven-install-plugin (install-file goal) and
> did
> not get the results I was after.
>
> How may I accomplish this?
>
> >>>
> >>> -
> >>> 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: [maven-scm-plugin] Why does scm:update fail on a branch?
The error message below should have been: [ERROR] fatal: ambiguous argument 'abc': unknown revision or path not in the working tree. - Original Message - Subject: [maven-scm-plugin] Why does scm:update fail on a branch? From: sco...@javactivity.org Date: 12/8/15 9:33 am To: users@maven.apache.org I am using the maven-scm-plugin with git. I find that the following succeeds: mvn -DscmVersion=abc -DscmVersionType=branch scm:bootstrap whereas the following, seemingly identical except for the command fails: mvn -X -DscmVersion=rpm -DscmVersionType=branch scm:update [ERROR] Provider message: [ERROR] The git-log command failed. [ERROR] Command output: [ERROR] fatal: ambiguous argument 'rpm': unknown revision or path not in the working tree. Use '--' to separate paths from revisions This looks like a bug in the plugin, but I don't really know. Why would the same specification fail for update but succeed for bootstrap? Other commands, such as scm:diff, scm:status, smc:checkout also work. Is this a bug and is there a workaround?
Episodic compilation
I'm about to get familiar with generating sources from XML-Schemas and fail with episodic compilation (whis is described at "https://github.com/highsource/maven-jaxb2-plugin/wiki/Using-Episodes";). But the description is for a different plugin, and I'm not sure whether the described syntax also fits to jaxb2-maven-plugin of the codehaus-distribution. I tried with a non existent but the plugin did not complain - so I think at lest this tag is not used. Is there somewhere out there a description of maven-plugin parameters, especially for , and ? I need to make sure, I only generate sources for the intended xsd not for the imported one. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?
I have a similar problem with RPM archiving with our Nexus Maven
Repository. I understand the reason for going the maven way for
naming, but when we want to use Nexus as our Yum repository manager it
should at least support naming the yum way.
When I have several packages for one project, then maven rearranges
the classifier to the end of the file and when there is no classifier
it appends rpm to the end of the file name.
${project.artifactId}-${project-version}.noarch.rpm =>
${project.artifactId}-${project-version}.noarch-rpm.rpm
${project.artifactId}-devel-${project-version}.noarch.rpm =>
${project.artifactId}-${project-version}.noarch-devel.rpm
${project.artifactId}-jws-${project-version}.noarch.rpm =>
${project.artifactId}-${project-version}.noarch-jws.rpm
I want to use Nexus as our RPM yum repository manager, but because of
this renaming of the RPM artefacts I am reluctant. I would have gone
for Artefactory if it didn't cost money for the RPM feature.
2015-12-07 22:05 GMT+01:00 Steve Cohen :
> Aargh! Email formattting!
>
> org.apache.maven.plugins
> maven-install-plugin
> 2.5.2
>
>
> install-rpm
>
> install-file
>
> install
>
>
> ${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name}-${project.version}-${rpm.release}.noarch.rpm
> ${project.groupId}
> ${rpm.name}
> ${project.version}-${rpm.release}
> noarch
> rpm
>
>
>
>
>
>
>
> On 12/07/2015 02:55 PM, Steve Cohen wrote:
>>
>> Actually, I found a way. If I am willing to let my "short name" become
>> the archiveId, (and thus live with the rpms in a different location),
>> the following is possible with the maven-install-plugin, after packaging
>> with the rpm-maven-plugin:
>>
>>
>>
>> org.apache.maven.plugins
>>
>> maven-install-plugin
>>
>> 2.5.2
>>
>>
>>
>>
>>
>> install-rpm
>>
>>
>>
>> install-file
>>
>>
>>
>> install
>>
>>
>>
>>
>> ${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name}-${project.version}-${rpm.release}.noarch.rpm
>>
>>
>> ${project.groupId}
>>
>> ${rpm.name}
>>
>> ${project.version}-${rpm.release}
>>
>> noarch
>>
>> rpm
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 12/07/2015 01:54 PM, Karl Heinz Marbaise wrote:
>>>
>>> Hi Steve,
>>>
>>> simply answer to this: It is not possible...
>>>
>>> Long answer: Maven repositories dependending on an appropriate naming
>>> schema to find artifacts / versions etc. If you change that the whole
>>> system will not work at all..
>>>
>>> So the name which is stored within a maven repository can't be changed.
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>> On 12/7/15 7:44 PM, Steve Cohen wrote:
Our organization has a convention for naming rpms. Typically, the rpm
will have a shorter base name than the Maven project. There is also a
convention around how releases are named. So we want a name
like|${shortname}-${project.version}-${release}.noarch.rpm|.
I want to build such rpms using the rpm-maven-plugin rather than older
nmake technology.
And this is easily accomplished using the plugin's parameters. The rpm
generated in the target directory has the desired name.
However, when|mvn install|installs this rpm into the maven repository,
it insists on storing it the "maven
way":|${project.artifactId}-${project.version}.rpm|
I want the rpm stored in the standard maven repository directory using
the name that is initially created on package.
I also tried using the maven-install-plugin (install-file goal) and did
not get the results I was after.
How may I accomplish this?
>>>
>>> -
>>> 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
[maven-scm-plugin] Why does scm:update fail on a branch?
I am using the maven-scm-plugin with git. I find that the following succeeds: mvn -DscmVersion=abc -DscmVersionType=branch scm:bootstrap whereas the following, seemingly identical except for the command fails: mvn -X -DscmVersion=rpm -DscmVersionType=branch scm:update [ERROR] Provider message: [ERROR] The git-log command failed. [ERROR] Command output: [ERROR] fatal: ambiguous argument 'rpm': unknown revision or path not in the working tree. Use '--' to separate paths from revisions This looks like a bug in the plugin, but I don't really know. Why would the same specification fail for update but succeed for bootstrap? Other commands, such as scm:diff, scm:status, smc:checkout also work. Is this a bug and is there a workaround?
