On 06/15/2011 04:19 AM, Marlon Pierce wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Permissions of the .tar.gz are screwy on my mac: the directory doesn't
have "read" permissions after I unpack it.
Ugh. I was afraid something like that might be an issue (assembly-plugin
filemode handling seems quite broken). Just didn't expect it to break on Mac :)
I'm actually have a MacBookPro but using Ubuntu natively :)
I guess I have to temporarily switch back to OSX now to try fix this...
Thanks,
Ate
Marlon
On 6/14/11 9:52 PM, Ate Douma (JIRA) wrote:
[
https://issues.apache.org/jira/browse/RAVE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049569#comment-13049569
]
Ate Douma commented on RAVE-59:
-------------------------------
I've committed a basic working automation for building a Rave demo/bin
distribution using maven-assembly-plugin and leveraging the cargo plugin to
setup and pre-deployed rave portal on Tomcat.
The distribution packages can be build from the rave-project folder using the
"dist" profile by running: $mvn -P dist
This will enforce a maven clean + install and thereafter build a
rave-<version>-bin.tar.gz and rave-<version>-bin.zip archive.
Note: these artifacts are build in the rave-portal/target directory!
Furthermore, I disabled the default enabled maven-assembly-plugin attaching of these
"artifacts" to the project, meaning these will *not* be deployed to the remote
maven repository (Nexus) during a release.
You would need to specify -P dist anyway to get it to work, so in practice this
is not really needed, but for sanity reasons I'd rather make sure it can't
happen anyway.
Can everyone please test drive this, including building the distributions on a
Windows environment and verify if these distributions thereafter still are
valid to be extracted and executed/run on a Linux environment?
Specifically, please verify if the execution bit for shell scripts is still
set, etc.
Furthermore, and IMO more importantly, what needs to be done is providing the
appropriate LICENSE and NOTICE files for the binary distributions (including
the rave-shindig.war and rave-portal.war).
I created a separate RAVE-63 issue for that.
Finally, I've provided basic/skeleton CHANGELOG file in the rave-project folder
and a demo/bin specific README file, both to be included in the demo
distributions.
These also need to be filled in, for which I created issue RAVE-64
Create automation for building of demo package
----------------------------------------------
Key: RAVE-59
URL: https://issues.apache.org/jira/browse/RAVE-59
Project: Rave
Issue Type: Sub-task
Reporter: Matt Franklin
Assignee: Ate Douma
Fix For: 0.1-INCUBATING
C
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN+BaVAAoJEOEgD2XReDo5pE4H/33R6afHEx47xorNG1V93Khm
SEu0V1cOJGk5FICVu35BV/7Z12o/PXwC7Iw0WXPFQB/3WHebCGC1v6EwIBgqM6Nn
JLOot1HrVh6mhiypa8Z9LALDzShNsQAdpuXOf7zZZyDQs7agPOi7ca/ePEB5Qrx9
kbq0kE4BWZFb/XOfiRvEtlpdi4NWZTJJapkdHoqWNHfijBicGEwzJ+QZXL7sYXHO
lz5aMj91llk8PPBExrLwV1PNe9MBbrBG1ZoaYlSal7R/E297rX+YFODc+Pil5646
+uiSwHjakzEz2DHJA8t053nOzcUIOSwn9rnKZQJKPcNV2kO0MJNYt8vV/Nbw0Eo=
=jM2S
-----END PGP SIGNATURE-----
