rpm-maven-plugin should work under windows / cygwin

Did you found any solutions for this?

I have the same problem

This cannot work! The Java VM is still a Windows app and as such it does not understand the Cygwin path mappings.

I was thinking to install the maven and jdk in the cygwin. Do you think that this will cause the rpmbuild to work in case is executed from the cygwin terminal?

I installed maven and got till the point of some error when executing the ./j2ee_something, even if I set the execute permission on it and the file command recognized it as an linux 32 i3086 something. Is possible to install it right?

I think it is going to be pretty tricky to get this to work. Java knows nothing of cygwin.

All java knows is that the os is windows. This means that the absolute path to files typically have drive letters ("C:") at the beginning and that the File separator character is '\'. Both of these items cause problems for the plugin to generate valid spec files.

[1] - http://java.sun.com/j2se/1.5.0/docs/api/java/io/File.html#separatorChar

Hi folks,

I have the same problem too and I'm very happy that I'm not the only one whit it.

I also use Windows and cygwin.

To enable the "rpmbuild" command for the cmd. exe which is called by maven during the build process I did nearly the same dirty tricks like Jan. I copied the rpmb.exe and renamed the copy to rpmbuild.exe but left it all in the lib\rpm-Folder under the cygwin-download directory. Then I added this folder to the Windows PATH-Variable. This worked in that way that maven does not tell me anything about the unknown command rpmbuild anymore. That's nice but it does not work at all.

No I get the following error-message and I really have no idea what goes wrong here.

[INFO] RPM build execution returned: '-1073741515' executing 'cmd.exe /X /C "rpmbuild -bb --buildroot d:\Projekte\Maven_Demand\RPM\rpmParent\testProject\targetRpm\buildroot --define "_topdir d:\Projekte\Maven_Demand\RPM\rpmParent\testProject\targetRpm" --target noarch testProject.spec"'

When this message rises the plugin already did some work. There is a folder-structure created with some files in it. One of the files is the target-artefact (a simple jar-file) of the project. Others are the class-Files of my java-sources and a spec-file which contains describing information from the plugins configuration, like NAME, VERSION, LICENSE, GROUP, PACKAGER etc.

Maybe you guys have an idea that brings up the light in this tricky issue...

Andreas

Please attach the generated SPEC file.

This is the content of the SPEC-File. Hope you'll see something usefull there.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Name: testProject
Version: 1.0
Release: 1
Summary: testProject
License: GNU
Group: FG-software
Packager: Andreas Ermrich
BuildRoot: d:\Projekte\Maven_Demand\RPM\rpmParent\testProject\targetRpm\buildroot

%description
testproject for the maven rpm-plugin

%files

apps/myApp/classes
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Does anyone have an example of a SPEC file that uses absolute paths (for the buildroot) and works? I have manipulated a SPEC file and the command executed from the command line and have gotten to the point where all of my errors are File not found for absolute paths that ls resolves.

Given the lack of feedback since January, I am going to close the issue. It can be opened again if anyone has feedback.

I rewrote the SPEC file that was generated by the plugin. I've included that below. Running the rpmbuild command still fails, but with a new error: "/var/tmp/rpm-tmp.1234: line 32: syntax error: unexpected end of file". Removing all '^M' line endings allows the file to be executed successfully. Because the rpmbuild generates a tmp file each time, this doesn't help, but seems to be another issue to be resolved for this plugin to work on Windows.

Name: sample-ws
Group: Applications/Internet
autoprov: yes
autoreq: yes
BuildRoot: /home/lawreand/workspace/i7/sample-TRUNK/sample-ws/target/rpm/sample-ws/buildroot
%description
Sample UE application - for education and demo purposes
%install
if [ -e $RPM_BUILD_ROOT ];
mv /home/lawreand/workspace/i7/sample-TRUNK/sample-ws/target/rpm/sample-ws/tmp-buildroot/* $RPM_BUILD_ROOT
then
else
mv /home/lawreand/workspace/i7/sample-TRUNK/sample-ws/target/rpm/sample-ws/tmp-buildroot $RPM_BUILD_ROOT
fi
%files
%config %attr(,root,) /etc/httpd/conf.d
%attr(,root,) /ci/jetty-8080/webapps/
%post
service httpd graceful;
service jetty-8080 restart
%postun
service httpd graceful;
if test -e /etc/init.d/jetty-8080
then service jetty-8080 restart
fi

Can you include the plugin generated spec as well for comparison?

I created a batch-file which replaces all paths in the spec-file and arguments to rpmbuild to cygwin paths and then executes rpmbuild in a cygwin environment. To try it, install cygwin and include rpm, rpmbuild, libintl2 and sed. Add your cygwin\bin folder to PATH. Then place the following script somewhere in your PATH (E.g. c:\windows) and name it rpmbuild.bat so the rpm-plugin finds it.

This was tested using rpm-maven-plugin 2.1-alpha-1. Hope it works for you too!

Andreas- I can't get your bat file working. rpmbuild gets called with the proper paths now, but the paths for the 'mv' command in the spec file don't get replaced.

Brett- here's the generated SPEC file:

Name: sample-ws
Group: Applications/Internet
autoprov: yes
autoreq: yes
BuildRoot: C:\home\lawreand\workspace\poc\sample\sample-ws\target\rpm\sample-ws\buildroot

%description
Sample UE application - for education and demo purposes

%install
if [ -e $RPM_BUILD_ROOT ];
then
mv C:\home\lawreand\workspace\poc\sample\sample-ws\target\rpm\sample-ws\tmp-buildroot/* $RPM_BUILD_ROOT
else
mv C:\home\lawreand\workspace\poc\sample\sample-ws\target\rpm\sample-ws\tmp-buildroot $RPM_BUILD_ROOT
fi

%files

%config %attr(,root,) /etc/httpd/conf.d
%attr(,root,) /ci/jetty-8080/webapps/

%post
service httpd graceful;

service jetty-8080 restart

%postun
service httpd graceful;
if test -e /etc/init.d/jetty-8080

then service jetty-8080 restart
fi

Thanks Andreas!

FYI, on my side, i'm building RPMs on both Windows and Linux. My build scripts couldn't work with the .bat file because the RPM's file name on windows contained the token ".cygwin".
I had the rpmbuild line to get rid of it:

bash -c "rpmbuild %1 %2 %NEW_BUILDROOT% %4 ""_topdir %NEW_TOPDIR%"" %6 ""%7"" --define ""_build_name_fmt %%

.rpm"" %8"

(fixed rpmbuild.bat attached to this issue)

Ooops, I just figured that the command line I used was working only I was in 2.0-beta2. In later versions, have to use only 1 quote around %7:

bash -c "rpmbuild %1 %2 %NEW_BUILDROOT% %4 ""_topdir %NEW_TOPDIR%"" %6 "%7" --define ""_build_name_fmt %%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm"" %8"

_{fixed the attached rpmbuild.bat too}

This ticket is closed as "won't fix". If you want it to be reopened, please state so!