-
15. Re: Installation of JBoss Wiki
margotmedia Mar 11, 2009 9:43 AM (in response to margotmedia)I don't get any other projects from SVN because the SVN problem I told you so I can't try out my maven on other projects. Have you the normal download Link of any Project on JBoss.org then I can try it out.
-
16. Re: Installation of JBoss Wiki
peterj Mar 11, 2009 12:40 PM (in response to margotmedia)I also tried to download and build. Here is my checkout statement:
svn co https://anonsvn.jboss.org/repos/portletswap/contrib/wikiPortlet/tags/1.0 wiki_1.0
I then cd'ed into wiki_1.0/wiki-common and ran:
mvn install
I got errors about 12 missing dependencies. Here is the last one, along with the information about the repositories searched:12) jboss:portal-api-lib:jar:2.7.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=jboss -DartifactId=portal-api-lib -Dver sion=2.7.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=jboss -DartifactId=portal-api-lib -Dversi on=2.7.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) jboss:wiki-common:jar:1.0 2) jboss:portal-api-lib:jar:2.7.1 ---------- 12 required artifacts are missing. for artifact: jboss:wiki-common:jar:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2), repository.jboss.org (http://repository.jboss.org/maven2), snapshots.jboss.org (http://snapshots.jboss.org/maven2)
I have successfully build JBoss AS 5.0.1.GA from the SVN sources - it has Maven portion that successfully downloaded the JARs for thirdparty, so my repositories should be correctly set.
I hope this helps in resolving this issue.
margomedia, all of the SVN URLs can be found by starting at http://anonsvn.jboss.org/repos/. Of course, not all projects build with Maven at this time. -
17. Re: Installation of JBoss Wiki
piergiorgiolucidi Mar 11, 2009 4:38 PM (in response to margotmedia)You need to install manually all the jboss dependencies required by Maven.
JBoss Maven repository now don't have Portal dependencies exposed on web, so, as I advice on the header of poms, you need to install all of these in your local repository to build.
All the dependencies (jars) are in binaries directory, you need to go there and execute all mvn install logged by Maven.
I hope Maven guys add these dependencies soon on public repository.
Hope this helps. -
18. Re: Installation of JBoss Wiki
peterj Mar 11, 2009 6:14 PM (in response to margotmedia)Oh, so that is what "Maven manual install means". It just sort of ran into the licensing statement, so I did not even notice it. Would be nice if it was better differentiated (in its own paragraph) and with complete instructions on how to accomplish this task (an example for one of the jars would be sufficient).
Let me go off and see if I can get a build to work and I will report back. -
19. Re: Installation of JBoss Wiki
peterj Mar 11, 2009 6:33 PM (in response to margotmedia)Finally! Success!
Here is what I did:
1) Downloaded the source from subversion:
svn co https://anonsvn.jboss.org/repos/portletswap/contrib/wikiPortlet/tags/1.0 wiki_1.0
2) Manually installed several missing libraries:mvn install:install-file -DgroupId=jboss -DartifactId=portal-core-lib -Dversion=1.0 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\portal-core-lib.jar mvn install:install-file -DgroupId=jboss -DartifactId=portal-portlet-lib -Dversion=1.0 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\portal-portlet-lib.jar mvn install:install-file -DgroupId=jboss -DartifactId=portal-identity-lib -Dversion=1.0 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\portal-identity-lib.jar mvn install:install-file -DgroupId=jboss -DartifactId=portal-common-lib -Dversion=1.0 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\portal-common-lib.jar mvn install:install-file -DgroupId=jboss -DartifactId=jboss-portlet-api-lib -Dversion=1.0 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\jboss-portlet-api-lib.jar mvn install:install-file -DgroupId=jboss -DartifactId=jboss-ejb3x -Dversion=1.0 -Dpackaging=jar -Dfile=%JBOSS_HOME%\client\jboss-ejb3x.jar mvn install:install-file -DgroupId=jboss -DartifactId=jboss-mail -Dversion=1.0 -Dpackaging=jar -Dfile=%JBOSS_HOME%\server\default\lib\mail.jar mvn install:install-file -DgroupId=jboss -DartifactId=activation -Dversion=1.0 -Dpackaging=jar -Dfile=%JBOSS_HOME%\server\default\lib\activation.jar mvn install:install-file -DgroupId=jboss -DartifactId=portal-api-lib -Dversion=2.7.1 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\portal-api-lib.jar mvn install:install-file -DgroupId=jboss -DartifactId=jboss-jmx -Dversion=1.0 -Dpackaging=jar -Dfile=%JBOSS_HOME%\lib\jboss-jmx.jar mvn install:install-file -DgroupId=jboss -DartifactId=portlet-api -Dversion=2.4.0 -Dpackaging=jar -Dfile=%PORTAL_HOME%\jboss-portal.sar\lib\portlet-api.jar mvn install:install-file -DgroupId=jboss -DartifactId=jboss-j2ee -Dversion=1.0 -Dpackaging=jar -Dfile=%JBOSS_HOME%\server\default\lib\jboss-j2ee.jar mvn install:install-file -DgroupId=jboss -DartifactId=jboss-annotations-ejb3 -Dversion=1.0 -Dpackaging=jar -Dfile=%JBOSS_HOME%\client\jboss-annotations-ejb3.jar
(Looks like the forum is wrapping the lines - each 'mvn' command should be on a single line)
%JBOSS_HOME% is where the JBoss AS 4.2.3.GA binary zip file was installed.
%PORTAL_HOME% is where the Portal 2.7.1.GA binrary was unpacked. If using the Portal + AS bundle, PORTAL_HOME is %JBOSS_HOME%\server\default.
Linux readers can adjust the syntax accordingly.
3) Commented out the jboss-ejb3 dependency in all five pom.xml files. There is a story behind this - some of the names used for JAR files in the POMs don't match the names o JAR files in either AS or Portal. So when in doubt, I commented out the dependency. If the build failed, I looked up the JAR containing the missing class and manually installed it. There was never an error based on the missing jboss-ejb3 dependency.
By the way, why are the dependencies mentioned in the base pom.xml repeated in the pom.xml files in the subdirectories? Those subdirectory POMs reference the base POM as a parent and thus pick up the dependencies automatically.
4) I then cd'ed into the wiki-common, wiki-management, wiki-test and forge-wiki directories and ran:
mvn install
in each one. I had to run it twice for wiki-common, once with 'packaging' set to 'pom' and once with it set to 'jar'.
5) I then changed the version number of the dependency of portal-identify-lib in the base pom.xml to 1.0 (from 2.7.1) to match the version number in wiki-common/pom.xml.
By the way, it would be nice if the versions were correct! Hardly any of the JARs identified as being at version 1.0 are at that version. If the proper version and artifact names were used, they could be pulled from the JBoss Maven repository instead of
being manually installed.
6) Then from the base directory I ran:
mvn install
The build then completed successfully.
I recommend that someone on the Wiki team make the corrections to the pom.xml files that I mentioned above. And in the base pom.xml, change the header comment to this:<!-- * JBoss, Home of Professional Open Source * Copyright 2009, JBoss Inc., and individual contributors as indicated * by the @authors tag. See the copyright.txt in the distribution for a * full listing of individual contributors. * * This is free software; you can redistribute it and/or modify it * under the terms of the GNU Lesser General Public License as * published by the Free Software Foundation; either version 2.1 of * the License, or (at your option) any later version. * * This software is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this software; if not, write to the Free * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA * 02110-1301 USA, or see the FSF site: http://www.fsf.org. BUILD INSTRUCTIONS ================== 1) Manually install various artifacts Before you run the build, you must manully install a number of JAR files into your local Maven repository. The JARs you need to install are: From JBoss Portal: portal-core-lib.jar, version 1.0 portal-portlet-lib, version 1.0 portal-common-lib.jar, version 2.7.1 portal-identity-lib.jar, version 1.0 jboss-portlet-api-lib.jar, version 1.0 jboss-ejb3x.jar, version 1.0 jboss-mail.jar, version 1.0 activation.jar, version 1.0 portal-api-lib.jar, version 2.7.1 jboss-jmx.jar, version 1.0 portlet-api.jar, version 2.4.0 jboss-j2ee.jar, version jboss-annotations-ejb3 Here is an example for installing portal-core-lib.jar, install the other JAR files using similar command. (If you miss one, or mistype it, Maven will remind you of the syntax for installing a JAR file.) In the example, <portal-home> is the location where the Portal binary zip file was unpacked. mvn install:install-file -DgroupId=jboss -DartifactId=portal-core-lib -Dversion=1.0 -Dpackaging=jar -Dfile=<portal-home>/jboss-portal.sar/lib/portal-core-lib.jar Note that some of the dependencies are located in JBoss AS, not in Portal. 2) Build the prerequisite projects You must build the wiki-common, wiki-management and wiki-test artifacts first. To do this, open a command line the corresponding directory, for example: cd <wiki-src-dir>/wiki-common where <wiki-src-dir> is the base directory of the wiki source, and enter: mvn install 3) Build the wiki Open a command line at the directory containing this POM and enter: mvn install author: Piergiorgio Lucidi -->
By the way, the licensing text should really follow what is recommended for LGPL. -
20. Re: Installation of JBoss Wiki
peterj Mar 11, 2009 6:42 PM (in response to margotmedia)Well, while the build did not complain, I don't think that the end result is correct. In the target directory I end up with:
target/lib/wiki-common.jar
target/wiki-management.jar
target/wiki-test.war
The build apparently still needs some fixing before it works correctly. -
21. Re: Installation of JBoss Wiki
margotmedia Mar 12, 2009 7:01 AM (in response to margotmedia)On my machine I build it correctly to but deployment is not sucessful like PeterJ sayed.
My target directory looks like Peters on JBoss Portal I getERROR Cause: javax.portlet.PortletException: org.apache.jasper.JasperException: Failed to load or instantiate TagExtraInfo class: org.jboss.portal.portlet.impl.jsr286.taglib.GenerateURL286TagTEI Message: org.apache.jasper.JasperException: Failed to load or instantiate TagExtraInfo class: org.jboss.portal.portlet.impl.jsr286.taglib.GenerateURL286TagTEI StackTrace: javax.portlet.PortletException: org.apache.jasper.JasperException: Failed to load or instantiate TagExtraInfo class: org.jboss.portal.portlet.impl.jsr286.taglib.GenerateURL286TagTEI at org.jboss.portal.portlet.impl.jsr168.api.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:91) at org.jboss.wiki.WikiPortlet.doView(WikiPortlet.java:625) at org.jboss.portlet.JBossPortlet.doDispatch(JBossPortlet.java:257) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:244) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:390) ...
Eclipse shows missing superclass org.jboss.portal.core.servlet.jsp.PortalJsp in forge-wiki > src > web > WEB-INF > jsp > Edit.jsp, PageInfo.jsp and Wiki.jsp
Eventually it helps! -
22. Re: Installation of JBoss Wiki
piergiorgiolucidi Mar 12, 2009 7:19 AM (in response to margotmedia)The ouput of the build is based on ear package exploded:
target/lib/wiki-common.jar
target/wiki-test.war
target/wiki-management.jar
target/wiki.war
target/META-INF
target/license
So you must to create a temp directory called wiki.ear and then copy all the artifacts here.
In the next version (main trunk committed) you can find a new version of poms and create a target/wiki.ear package, so you will can deploy directly this directory.
To build you must install wiki-common in your repository as other dependencies and then you must call mvn package.
Hope this helps. -
23. Re: Installation of JBoss Wiki
piergiorgiolucidi Mar 12, 2009 7:34 AM (in response to margotmedia)Thank you PeterJ for all your contributions, I hope to correct poms soon.
You can take a look at newest poms that I committed on main trunk of the project.
About versioning of Jars, I prefered to commit this release now to allow users to deploy JBoss Wiki on Portal 2.7.
Before my contribution this project was based on Maven 1. I hope to refactor poms soon.
Now I can work on refactoring of these poms ;)
I work only on portlet projects so I have adviced JBoss Maven repos guys about exposing portal dependencies. They are working on, but I don't know when we will use it :-P
Thank you again. -
24. Re: Installation of JBoss Wiki
theute Mar 12, 2009 7:54 AM (in response to margotmedia)Piergiorgio,
there are some of the JBoss Portal 2.7 binaries on our Maven repo if it helps:
http://repository.jboss.com/maven2/org/jboss/portal -
25. Re: Installation of JBoss Wiki
margotmedia Mar 12, 2009 8:24 AM (in response to margotmedia)Whit the new trunk of the project Eclipse shows an error that the classes MBeanProxyExt and MBeanServerLocator of package org.jboss.mx.util not found. Therefore maven can not install it. What must I now install?
-
26. Re: Installation of JBoss Wiki
margotmedia Mar 12, 2009 10:25 AM (in response to margotmedia)Maven install of wiki-common is not successful. Maven says
cannot find symbol symbol : variable MBeanServerLocator location: class org.jboss.wiki.WikiCommon cannot find symbol symbol : variable MBeanProxyExt location: class org.jboss.wiki.WikiCommon
I have made a new checkout of trunk!
Please help me!
I just want a executable wiki on my jboss portal where I can save the files on a other place as /tmp and now I spend nearly 2 days to get a deployable wiki.ear file :-( -
27. Re: Installation of JBoss Wiki
peterj Mar 12, 2009 11:20 AM (in response to margotmedia)All this work just to change the location of the /tmp directory? Why didn't you say so in the first place! Unpack the wiki.war file, edit the the properties in the WEB-INF/classes/org/jboss/wiki/filedatasource.properties file and you are all set. Personally, I deploy as an exploded directory so that I have easy access to these settings.
-
28. Re: Installation of JBoss Wiki
peterj Mar 12, 2009 11:21 AM (in response to margotmedia)Oh, the wiki.war is within wiki.ear, so you have to unpack that first.
-
29. Re: Installation of JBoss Wiki
theute Mar 12, 2009 11:23 AM (in response to margotmedia)Piergiorgio if you can make this location easier to change (such as a portlet preference) you would be my hero :)
That's what I found the most frustrating thing when I tried that portlet :-/