Re: build pblms on Macs
On 1/15/07, Adam Lally <[EMAIL PROTECTED]> wrote: I tried setting the Maven descriptors' setting to 644 (-rw-r--r--), but it did not seem to have any affect. It might be a Maven bug. Aha.. it is a known bug: http://jira.codehaus.org/browse/MASSEMBLY-173 The element of the descriptor is incorrectly treated as decimal rather than octal. When I specified a value of 422 (decimal equivalent of octal 644) I did get the correct permission rw-r--r--. Apparently, this bug also applied to the default permission - I will post that information to the Maven JIRA and vote for the issue. I'll commit the workarounds shortly and close our JIRA issue. -Adam
Re: build pblms on Macs
On 1/15/07, Marshall Schor <[EMAIL PROTECTED]> wrote: May be some kind of directory permissions issue. The Jars in the runtime plugin had permissions set as follows: The directory: drwxr-xr-x The jars in the directory: --w---r-T I think the T is a "sticky" bit - but I forgot what that means. Anyway, with these permissions settings, very strange errors are happening. I did a chmod to make the jars have -rw-r--r-- and then, the CDE actually started :-) Time to go to sleep, now... But I'll enter a Jira issue to fix the maven build on Unix and Mac platforms. I verified this same permissions problem on a Linux Intel machine. So far what I've found out is: If I change our Maven build scripts to build .tar.gz files for the plugins instead of .zip files, then the resulting unzipped files do not have the T bit set (yes it is the "sticky bit", based on information I found it is mostly obsolete). However, they still have the permission: --wr-- I didn't try this in Eclipse but I suspect it will still not work; it probably does not like having the owner read bit unset. I tried setting the Maven descriptors' setting to 644 (-rw-r--r--), but it did not seem to have any affect. It might be a Maven bug. That's all I know for now. -Adam
Re: build pblms on Macs
I tried changing the build scripts on the Mac, so the directory and outputDirectory entries are "./" instead of "/". That at least made the ep-plugins have all the files. I changed only the directory not the outputDirectroy.
Re: build pblms on Macs
I'll bring my mac tomorrow and look into that as well. Just to make sure it is not related to a distinct machine, because the rights are pretty weird though. btw.: http://en.wikipedia.org/wiki/Sticky_bit (not the best source, but good enough for a refresher) -- Mirko On 1/15/07, Marshall Schor <[EMAIL PROTECTED]> wrote: May be some kind of directory permissions issue. The Jars in the runtime plugin had permissions set as follows: The directory: drwxr-xr-x The jars in the directory: --w---r-T I think the T is a "sticky" bit - but I forgot what that means. Anyway, with these permissions settings, very strange errors are happening. I did a chmod to make the jars have -rw-r--r-- and then, the CDE actually started :-) Time to go to sleep, now... But I'll enter a Jira issue to fix the maven build on Unix and Mac platforms. -Marshall Marshall Schor wrote: > I tried changing the build scripts on the Mac, so the directory and > outputDirectory entries are "./" instead of "/". That at least made > the ep-plugins have all the files. > > However, the "jars" are not being built correctly - they're there, but > they're empty... > > Anyone have any ideas how to fix this? > > -Marshall > > Jörn Kottmann wrote: >> Hello, >> >> I have the same problem on my macbook. >> >> If you take a look at the assemble-plugin.xml you will see this: >> >> ... >> >> >> / >> >> plugin.xml >> META-INF/ >> >> / >> >> >> ... >> >> The problem is that "directory" must point to the current directory >> "./" and not to the root directory "/". >> Maven simply do not finds the files. I guess this fails on linux too. >> >> I think this should break the build or at least print a warning. >> >> Jörn > > >
Re: build pblms on Macs
May be some kind of directory permissions issue. The Jars in the runtime plugin had permissions set as follows: The directory: drwxr-xr-x The jars in the directory: --w---r-T I think the T is a "sticky" bit - but I forgot what that means. Anyway, with these permissions settings, very strange errors are happening. I did a chmod to make the jars have -rw-r--r-- and then, the CDE actually started :-) Time to go to sleep, now... But I'll enter a Jira issue to fix the maven build on Unix and Mac platforms. -Marshall Marshall Schor wrote: I tried changing the build scripts on the Mac, so the directory and outputDirectory entries are "./" instead of "/". That at least made the ep-plugins have all the files. However, the "jars" are not being built correctly - they're there, but they're empty... Anyone have any ideas how to fix this? -Marshall Jörn Kottmann wrote: Hello, I have the same problem on my macbook. If you take a look at the assemble-plugin.xml you will see this: ... / plugin.xml META-INF/ / ... The problem is that "directory" must point to the current directory "./" and not to the root directory "/". Maven simply do not finds the files. I guess this fails on linux too. I think this should break the build or at least print a warning. Jörn
Re: build pblms on Macs
I tried changing the build scripts on the Mac, so the directory and outputDirectory entries are "./" instead of "/". That at least made the ep-plugins have all the files. However, the "jars" are not being built correctly - they're there, but they're empty... Anyone have any ideas how to fix this? -Marshall Jörn Kottmann wrote: Hello, I have the same problem on my macbook. If you take a look at the assemble-plugin.xml you will see this: ... / plugin.xml META-INF/ / ... The problem is that "directory" must point to the current directory "./" and not to the root directory "/". Maven simply do not finds the files. I guess this fails on linux too. I think this should break the build or at least print a warning. Jörn
Re: build pblms on Macs
Hello, I have the same problem on my macbook. If you take a look at the assemble-plugin.xml you will see this: ... / plugin.xml META-INF/ / ... The problem is that "directory" must point to the current directory "./" and not to the root directory "/". Maven simply do not finds the files. I guess this fails on linux too. I think this should break the build or at least print a warning. Jörn
build pblms on Macs
I borrowed a Mac to do some testing. Setup Eclipse 3.2.1, with EMF and Subclipse SVN client. Checked out the code, installed maven 2 Did the maven setup for eclipse, etc. The build almost worked, but got one test failure. Building with the tests bypassed completed with no apparent error. However, *the plugins didn't build correctly*. The runtime plugin only has the "lib" directory - no "plugin.xml" or manifest. Can the maven expert give me some general hints where to look for this problem? It's probably some part of the setup I forgot to do -Marshall
