Skip to content
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

Please review and add the new archetypes for RM #194

Closed
tunaaksoy opened this issue Jul 20, 2014 · 2 comments
Closed

Please review and add the new archetypes for RM #194

tunaaksoy opened this issue Jul 20, 2014 · 2 comments
Assignees
Milestone

Comments

@tunaaksoy
Copy link

Gab can you please review and add the new archetypes for RM? Thank you very much.

https://github.com/tunaaksoy/alfresco-rm-amp-archetype
https://github.com/tunaaksoy/share-rm-amp-archetype

UPDATE:

Gab can you please review the new all in one archetype for RM?

https://github.com/tunaaksoy/alfresco-allinone-rm-archetype

And also can we please add the following config to the parent pom so that not every user gets the error saying "Plugin execution not covered by lifecycle configuration" when the user imports the maven project until we fix it properly (after implementing a connector). Thanks.

   <build>
      <pluginManagement>
         <plugins>
            <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
            <plugin>
               <groupId>org.eclipse.m2e</groupId>
               <artifactId>lifecycle-mapping</artifactId>
               <version>1.0.0</version>
               <configuration>
                  <lifecycleMappingMetadata>
                     <pluginExecutions>
                        <pluginExecution>
                           <pluginExecutionFilter>
                              <groupId>
                                 org.alfresco.maven.plugin
                              </groupId>
                              <artifactId>
                                 alfresco-maven-plugin
                              </artifactId>
                              <versionRange>
                                 [2.0.0-SNAPSHOT,)
                              </versionRange>
                              <goals>
                                 <goal>set-version</goal>
                              </goals>
                           </pluginExecutionFilter>
                           <action>
                              <ignore></ignore>
                           </action>
                        </pluginExecution>
                     </pluginExecutions>
                  </lifecycleMappingMetadata>
               </configuration>
            </plugin>
         </plugins>
      </pluginManagement>
   </build>
@mindthegab
Copy link
Contributor

I think adding an “rm” profile should be fairly easy. We can chedule some time this week, we can go through it together and I can make the necessary changes to the SDK parent.

Ideally there would be no changes in the all-in-one, just an added profile -Prm to enable easy RM driven development. Interestingly enough you can also configure in your ~/.m2/settings.xml so rm devs can have the ‘rm’ profile active by default.

@mindthegab mindthegab added this to the 2.0.0-beta-3 milestone Aug 29, 2014
@mindthegab
Copy link
Contributor

This is now integrated in trunk.

Running the all-in-one with -Prun,rm includes the RM dependencies at runtime and for compilation.

mindthegab added a commit that referenced this issue Aug 29, 2014
@mindthegab mindthegab modified the milestones: 2.0.0-beta-4, 2.0.0 Dec 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants