Showing posts with label Maven. Show all posts
Showing posts with label Maven. Show all posts

Friday, May 10, 2013

Your portal with Entando


You are curious to see how you can create a portal with Entando, nothing more simple.
I urge you to read this Trumbitta guide "Entando: an unexpected journey. Or, my portal from scratch."

Good Entando to all

Rinaldo 

Friday, December 23, 2011

Install Entando on Netbeans


Hi to all,
yes again here speaking about  Entando, after installing it with maven (First step with Entando ), now we go to install Entando using NetBeans 7.01

prerequisites:
  java, postgresql, tomcat, NetBeans 7.01 are all present on the PC.
  a postgresql user agile with password agile is configured
  Step:
  1. Start Netbeans
  2. Create New Project
  3. Select Maven - Project From Archetype click Next
  4. Select Archetypes from Remote Repository
  5. Select Entando: Archetype For Generic Portal (the version number can be different)
  6. Click next and complete the form

yes we've just create a project based on Entando (whow very simple and fast).

Another few important steps
 1. create the db:
  1.1 in your project expand the build.xml file
  1.2 execute  PG-db-full-update this task create the db used by the project

 2. run the project
  2.1 click on run project select your webapp server I suggest tomcat 6.xx

  if all it's ok you'll see this page

  login as suggested in the web page and you see the administration console

Fine yes?
Simple poprtal with no plugin so next question is How can I insert a plugin in my project/portal?
 Answer:
first read the entando guide:
  How to add some Plugins to my own portal based on mavenized Entando  on GitHub

Read it?
Ok, go back to NetBeans
stop tomcat and open pom.xml file
insert the code you find in the entando guide and your pom.xml will look like this



pay attention to change the version (here we have 0.0.1-SNAPSHOT) to the last one, how? easy select 0.0.1-SNAPSHOT  and click ctrlspacebar and Netbeans will suggest you the last number version.
Save the pom.xml file, clean and build your project.

Now it's time to update the db to be compliant with the plugin inserted in the project, so expand the build.xml file and execute the task PG-db-restore-plugins

Run the projcet, login and you can see the plugin in the list.

et voilĂ , very simple and easy.

Now it's Christmas time so
Happy Christmas to all 

Rinaldo



Friday, December 16, 2011

First step with Entando


The new version of Entando is out and as reported in the following post "Enter Maven and GitHub"   mMven and GitHub are used.

mmm ... Maven?
question: how do I install / use the new version of Entando?
answer: ?????

So I started studying a bit of Maven, read the blog posts, wikis, tested,...

So the result is I can install and deploy a portal based on Entando in a few minutes
prerequisites:
  java, postgresql, tomcat are all present on the PC.
  a postgresql user agile with password agile is configured .
Steps:
1. Install maven
2. open a terminal
3. create a directory for the project you want to create
3. cd into the directory you just created
4. type mvn archetype: generate-Dfilter = entando
5. answer the following questions:
5.1 Choose archetype:
1: remote -> org.entando.entando: entando-archetype-plugin-generic (Generic Archetype Plugin for Entando: an agile, modern and user-centric open source portal platform.)
2: remote -> org.entando.entando: entando-generic-portal-archetype (Archetype for Entando Generic Portal: an agile, modern and user-centric open source portal platform.)
Choose a number or apply filter (format: [groupId:] artifactId, contains case sensitive):
choose 2

Choose org.entando.entando: entando-portal-archetype-generic version:
1: 2.4.0.1
2: 2.4.0
Choose a number: 2:
choose 1 [the list of version may differ we're now on version 4.0]
Define value for property 'groupId':: it.testentando
Define value for property 'artifactId':: testentando
Define value for property 'version': 1.0-SNAPSHOT: (accept default)
Define value for property 'package': it.testentando: (accept default)
displays the list of choices if you run press Y otherwise press N and repeat from step 5.1
That's all now we have a folder containing the created project (in this case testentando).
6.Populate the db
6.1 Configure the buildProperties.xml for your Operatin System
6.2 open a  terminal and type
cd testentando
ant  PG-db-full-update 
This step is not required , no postgres is require for the first run.

7. last step:
in the folder src/main/filters check the properties file to ensure that the configurations of Tomcat and the postgresql password is correct (in case you doesn't use agile/agile).

Now you're ready to start the portal.
  mvn clean jetty:run 

http://localhost:8080/testentando/

et voilĂ  Entando is running

Links:
            The Entando wiki on GitHub
            Entando download





Sunday, March 7, 2010

JasForge : the agility in the software development revealed !

Today I want to present a French product JasForge.
  • What is Jasforge?
Jasforge is a JASMINE CONSEIL initiative and like any forge solution Jasforge is a management system of collaborative development of software.
It allows sharing the source code of the projects, tracking bugs, storing and sharing documents, discussions and communications in a common area.
Moreover, Jasforge is a framework of collaborative development which can be installed and used in various contexts.
 Jasforge originality come from the fact that the project is based on standard Open Source tools which collaborate together to form a unified solution which follow the development practice of a Continuous Integration process.
Jasforge solution will help to organize software project processes, improve schedule management, increase software delivery quality and facilitate collaboration between project teams.
In order to carry out these objectives, Jasforge aims
     -   To integrate several tools of the open source world to carry out all the considered features.
     -   To implement a module that manages user’s profile in all the system.
     -   To Develop a GUI for administration and users that has to be friendly and ergonomic.
To summarize Jasforge must provide a common access point and unify all the tools necessary for the establishment of a platform for collaborative work using the techniques of continues integration.

  • What distinguish Jasforge?
Jasforge uses new concepts which made it very different compared to all existing forges.
First used concept:
Continuous Integration
Jasforge follows the development practice of a Continuous Integration process which will increasev the quality of the delivery by improving the use of software development best practices.
Second used concept: Plug-in based architecture 
The power of Jasforge is that it defines a Jasforge plug-in for each integrated tool. This will give it the capability to integrate easily new tools and versions and give the user the ability to define a customized Jasforge with his preferred set of tools. (The Jasforge architecture will be explained later).
Other Jasforge particularities
Jasforge is software that can be installed in any local or extended network or even in one single machine. Its installation will automatically setup a forge and by this way we avoid configuration time.
Other advantage is that Jasforge offer a friendly environment to interact with tools. That means that we can be a non-expert user and use the Jasforge solution.
Jasforge platform will offer a large range of tools and services needed daily by software development teams to supply high quality software.
The figure bellow illustrates features integrated in each module.


The particularity of Jasforge is it uses a continuous integration process. This assures the best practices of development and quality guaranty.
Hudson communicates with SVN to check a change in the project, if there any change, it launches a build, and we can also force a build manually.

Note That: the build can be an ANT build or a maven build. For Jasforge we use Maven build.
Hudson is a war file so it needs to deploy it in a server and to make a module to synchronize between Hudson and Jasforge.



Hudson contain different controller for each functionality like build or authenticate and we can call these controller from a URL. So we implement a process based on a HTTP communication and can call a function from Hudson and pass the different parameter in the URL.
For the authentication, Hudson use HTTP BASIC authentication to specify the user name and the password and can use the LDAP authentication because both Hudson and security Realms use the servlet J_Security_Check where we define the J_username and J_password.


If you need further information, contact:

  • Karim DJAAFAR  (kdjaafar[ at ] jasmineconseil.com) the chief leader of this open source projet, which can be pleased to respond to your questions ! 
  • me (Rinaldo Bonazzo rbonazzo[ at ]gmail.com).