Posted by Saba Ansari on July 6, 2010
Currently, I’m running an ant target (unzip) to explode and then copy the EAR+WAR to JBoss. the jboss-maven-plugin is insufficient b/c the unpack does not explode the WAR in the EAR.
Is this explode goal/plugin included as a feature in Maven 3? thx.
Posted by Saba Ansari on July 6, 2010
Hi All,
I am a new user to maven. And i have the following queries.
In my concern we use CVS as repository & ant for build. Whenever a new build is created we have a procedure like first updating CVS and then creating build using ant and then taking the new build and copying it in a new folder etc.,
now using maven i need automate the below tasks, by calling maven
1. CVS update
2. Build using ant
3. Copy the newly created build to some folder
4. Upload and deploy in remote server
5. Test cases to check whether site is working fine
6. Sending a mail to a group stating the deployment status
please help on this…
Thanks Paulwintech
Posted by Saba Ansari on July 2, 2010
So I actually had already downloaded and extracted the zip file for mavensh:
C:javamvnsh-0.10bin
In that directory there is a mvn.bat and mvnsh.bat for Windows.
How do I use this CLI tool? The readme.txt points to the website and no specific instructions. thx.
Posted by Saba Ansari on July 2, 2010
I am using the Confluence plugin for site pages with some success, but I can’t get the {toc} to work in a .confluence file. I just get the literal “{toc}” rendered in the HTML.
I am following the guidance here:
http://confluence.atlassian.com/renderer/notationhelp.action?section=confluence
Has anyone out there managed to make “{toc}” work in a .confluence file?
Thanks
Nathan
Posted by Saba Ansari on July 2, 2010
Using Maven 3 beta 1…
I have the following XML snippet in my pom.xml:
env-dev
true
maven-antrun-plugin
echodir
run
verify false
Build Dir: ${project.build.directory}
….
Note that the version tag is commented out. The version that was downloaded by Maven was from this URL: https://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-antrun-plugin/
and specifically it used version 1.3:
Downloading: https://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-antrun-plugin/1.3/maven-antrun-plugin-1.3.jar
How does Maven know which version to download when the version is not specified? thx.
BTW, I have the following in my settings.xml:
jboss-public-repository
jboss-public-repository-group JBoss Public Maven Repository Group https://repository.jboss.org/nexus/content/groups/public/ default
true never
true never
jboss-public-repository-group JBoss Public Maven Repository Group https://repository.jboss.org/nexus/content/groups/public/ default
true never
true never
jboss-public-repository
Posted by Saba Ansari on July 1, 2010
Where is beta-7?
As a side note, the developers had better not release version 3 until the site plugins and other major elements are actually ready. They did this with Maven 2 and it was hell. I know because I went through it.
On a side note, I decided that Tycho wasn’t worth it for as simple a plugin as mine was. It was just more trouble. Again, this has to do with not really being ready more than anything else, and having rather incomplete documentation.
-K
On Jun 30, 2010, at 3:46 AM, Olivier Lamy wrote:
Posted by Saba Ansari on July 1, 2010
Thanks for the suggestion Brett but it appears that wasnt the right fix. I updated to jdk 1.6.0_20. Im getting the same error in the same place.
Caused by: java.net.UnknownHostException: repo1.maven.org
Posted by Saba Ansari on July 1, 2010
Someone else posted similar a few weeks back with the same JDK version, which is pretty old: http://maven.40175.n5.nabble.com/Maven-in-5-minutes-doesn-t-work-tt510820.html#a510820
“Thanks for the support guys, it was not a proxy issue. I upgraded my JDK/JRE from 1.6.0_03 to 1.6.0_20 and it all came back on the track, a bit strange though. ”
I’d try updating to a current patch release of JDK 1.6.0 on you platform.
Best Brett
On Thu, Jul 1, 2010 at 11:13 AM, Andrew Bucknell wrote:
Posted by Saba Ansari on June 28, 2010
nothing happend so far
On 23.03.2009 06:54, Wayne Fay wrote:
Posted by Saba Ansari on June 28, 2010
The maven site to the maven signjar plugin does not seem to be completely up to date.
[MJARSIGNER-6] Allow batch signing of multiple JARs
This has not been covered by the documentation, and according to JIRA this was included in the 1.1 release, the current release is 1.2.
What should be trusted here? JIRA or the documentation?
Best regards