-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2 beta 4 share-amp archetype run.bat not provided (Windows) #271
Comments
Hi, Here are the steps that I use to work with a Share AMP:
|
Agree with @gravitonian. Just a clarification:
You can use a repo AMP archetype in another tab. In fact the SDK's purpose is no need for manual downloads. |
Some big advantages (and a few disadvantages of using the installer). Advantages:
Disadvantages:
If you are developing share and repo customizations, consider using the all in one archetype... I'm sure I've missed stuff, but figured I'd get this list started |
Thanks Bindu, this is something that may be useful for the documentation. |
run.bat is now provided as of 2.1.0 |
I am trying to create a development environment for a Community v5.0.d installation to work with Aikau. I first ran: mvn archetype:generate -Dfilter=org.alfresco.maven.archetype:share-amp-archetype which created the folder structure for the project. The instructions at https://artifacts.alfresco.com/nexus/content/groups/public/alfresco-sdk-aggregator/latest/archetypes/share-amp-archetype/index.html say to then execute run.sh. I am in a Windows environment and there is no run.bat in the folder. Is Windows supported?
I then tried to run "install mvn -Pamp-to-war" against the project and it fails and it never completes. I am not able to reach Share at http:localhost:8081/share afterwards.
Error messages:
Edited:
I manually executed the steps from the run.sh from the Windows command line and set the MAVEN_OPTS. The validate step run successfully and I can see springloaded in the maven repository, but the integration-test -Pamp-to-war step fails when it starts Tomcat.
SEVERE: The web application [/share] appears to have started a thread named [Fil
eSystemWatcher: files=#7 cl=WebappClassLoader
context: /share
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
ClassRealm[tomcat, parent: null]
] but has failed to stop it. This is very likely to create a memory leak.
Apr 01, 2015 7:28:02 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8081"]
The text was updated successfully, but these errors were encountered: