[
http://jira.amdatu.org/jira/browse/AMDATU-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11737#comment-11737
]
Bram de Kruijff commented on AMDATU-427:
----------------------------------------
Copy and paste from AMDATU-440:
{quote}
The following needs to be improved:
When I compile the demo release artifact, I get this build failure;
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
(create-release) on proj
ect org.amdatu.release.demo: Failed to create assembly: Error creating assembly
archive bin: Problem creating TAR: entry
closed at '149' before the '290' bytes specified in the header were written ->
[Help 1]
As a result the directory and tar.gz versions are generated, but the zip file
is not.
In the deploy directory there is an absolete META-INF directory
After startup the ' Amdatu Semantic Web - RDF 2 GO Sesame Bridge' bundle
remains in the 'Starting' state
There are two storage implementations deployed for user admin (filebased and
cassandra), which is probably the cause of issue
http://jira.amdatu.org/jira/browse/AMDATUAUTH-103. The filebased implementation
should be removed from the demo release.
The Amdatu dashboard shortcut points to an invalid URL (localhost:3337)
The NOTICE files does not contain a complete set of attributions (its almost
empty)
The default dashboard fails to render properly (JS errors 'gadgets is not
defined' and 'jQuery is not defined'). This is probably caused by the fact that
the Shindig config files define the port to be 3737 instead of 3337 used by
other config files.
{quote}
> Provide a demo release distribution
> -----------------------------------
>
> Key: AMDATU-427
> URL: http://jira.amdatu.org/jira/browse/AMDATU-427
> Project: Amdatu
> Issue Type: Task
> Components: Build & Release management
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
>
> As discussed on mail [0]. A popular request is a quickstart/demo distribution
> allowing people to quickly dl, install, run to get an idea of what amdatu can
> do. This is not unlike what we released before, obviously it only has one
> example deployment configuration (we should make that clear). We could
> probably implement this quick-and-dirty just like the amdatu-release-ams
> module while we wait for provisioning. I'd suggest making it as fat as
> possible thus including opensocial, cassandra, auth and semantic.
> [0] http://www.mail-archive.com/[email protected]/msg04883.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
